Transcript Interoperability

Welcome to this TechNet Event
We would like to bring your attention to the key elements of the
TechNet programme; the central information and community
resource for IT professionals in the UK:
•
•
•
•
•
•
FREE bi-weekly technical newsletter
FREE regular technical events hosted across the UK
FREE weekly UK & US led technical webcasts
FREE comprehensive technical web site
Monthly CD / DVD subscription with the latest technical tools
& resources
FREE quarterly technical magazine
To subscribe to the newsletter or just to find out more, please visit
www.microsoft.com/uk/technet or speak to a Microsoft representative
during the break
Integration
Michael Platt
Architect
Microsoft
About This Session
• Microsoft and Integration
– Why integrate?
– What is Microsoft’s Integration story?
• Questions from individuals, customers and organizations
• Product specific pitches often don’t hit the mark
– We do have a good story!
• Many people don’t always realize this!
• “You can work with what I already have?”
• My Goal for this Session
– Think about integration in a different way
“Let’s start…”
“How do you define Interoperability?”
Definitions of Interoperability
• Some Definitions
– “The ability of a system to use the parts or equipment
of another system”
• [Merrium Webster]
– “The capability to communicate, execute programs, or
transfer data among various functional units in a
manner that requires the user to have little or no
knowledge of the unique characteristics of those units."
• [ISO/IEC 2382 Information Technology Vocabulary]
– “…the capability of different programs to read and write
the same file formats and utilize the same protocols.”
• [Wikipedia – http://wikipedia.org/wiki/Interopedia]
Executive Email – Bill Gates
http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp
Executive Email – Bill Gates
…I want to focus on two major thrusts of
Microsoft’s product interoperability strategy: First,
we continue to support customers’ needs for
software that works well with what they have
today. Second, we are working with the industry to
define a new generation of software and Web
services based on eXtensible Markup Language
(XML)…
http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp
Executive Email – Bill Gates
Works with
What You Have
Designed for
Interoperability
http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp
Executive Email – Bill Gates
Works with
What You Have
Designed for
Interoperability
http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp
The Areas of Interoperability
Management
Identity
WS-*
Process
Works with
What You Have
Programmatic
Data
Network
Designed for
Interoperability
Web Services
XML
http://msdn.microsoft.com/vstudio/java/interop
The Areas of Interoperability
Management
Networking
Protocols
TCP/IP
Identity
DNS
Process
Programmatic
DHCP/BOOTP
802.1x
AppleTalk
Data
Network
IPX/SPX
NFS/NIS
Network and Infrastructure
• Windows Server File and Print
– “Interoperability with existing Windows Clients”
• Assumed and understood
• Don’t need to repeat!
– Backward compatibility assumed
• “After all, they are your own products!”
– Heterogeneity Happens
• Very few organizations are Microsoft-only
• Infrastructure and networking history may include
AppleTalk, NetWare NDS, Unix, Linux
Network and Infrastructure
• Interoperability with Novell and Apple
– Microsoft Services for Netware 5.03
– Microsoft Services for Macintosh
Directory Synchronization
over IPX/SPX
Novell Netware NDS
Data, Printer, PPP sharing
over AppleTalk
Windows Client, Server
or Gateway
Apple System 7 through
OSX
Network and Infrastructure
• Interoperability with Novell and Apple
– Microsoft Services for Netware 5.03
• Free Web Download
• Directory Synchronization Services (MSDSS)
– Synchronization of AD and NDS, eDirectory
– Tactical, Novell specific IDM solution for NDS
– Microsoft Services for Macintosh
• Embedded Service within Windows Server 2003
• Interoperability with Data
– Existing folders and printers to Macs
• Interoperability with Apple Networking
– AppleTalk Routing between networks
– AppleTalk (PPP) Remote Access
Network and Infrastructure
• Interoperability with UNIX and Linux
– Microsoft SFU (Services for UNIX) 3.5
V2 and v3 NFS / NIS
support
over TCP/IP
Windows Client, Server
or Gateway
NFS
NIS
UNIX or Linux
Client or Server
Network and Infrastructure
• Interoperability with UNIX and Linux
– Microsoft SFU (Services for UNIX) 3.5
– Interoperability with UNIX Data and Directories
• NFS Support for v2 and v3 of NFS
– Windows NFS support as client, server or gateway
– Used widely in NAS environments
– ACL to mode bit mapping
• NIS Support
– Tactical, UNIX specific IDM solution for NIS deployments
– Password update support
– SDK contains 1,900+ UNIX APIs, 300+ UNIX Tools
– Tools to interoperate work same as the UNIX derivitives
– Include mount, umount, showmount for NFS
– Use chmod, chgrp, chown for remotely mounted directories
Network and Infrastructure
• SNA
– TN3270
– IBM Anynet
– Data Link Switching
– Distributed Link Services
– TCP/IP now surpassing SNA
• Customer Upgrading to New z900 Mainframes
– IBM Retiring SNA FEP and CC Hardware
• Customers balking at high-end DLSw Routers
– IP-DLC Link Service
– Based on IBM APPN HPR/IP (RFC 2535 IP-DLC)
Network and Infrastructure
• Mainframe Integration
– Interoperability Advantages
– ‘Unlocking’ of existing production applications
BLI (Business Logic Interface)
SLI (Screen Logic Interface)
Microsoft .NET
Mainframe
Integration with Mainframes
• Mainframe Integration
– Business Logic Interface (BLI)
• Majority of IMS and AS/400 programs
• Access via callable interfaces
– Screen Logic Interface (SLI)
• Majority of CICS programs (80%)
• Access via Screen Scraping
– TN3270, 3270 Bridge or FEPI
• Presentation Integration (3270 -> HTML)
• Programmatic Integration (3270 -> objects)
– BLI or SLI?
• Performance, but requires callable interfaces
• SLI well suited for no touch interoperability
Integration with Mainframes
• Screen Logic Interface (SLI)
– Mainframe Access via Screens, TN3270 and/or FEPI
– Advantages
• Non-Invasive approach to mainframe integration
• Techniques for dealing with “form changes”
– Products dominated by many 3rd party companies
• ClientSoft, NetManage, WRQ and many more
– ClientSoft – Great Customer Success Stories
– NetManage – Contractual Relationship
– WRQ – Updated Verastream Product
• Gartner’s Programmatic Integration Magic-Quadrant
– http://mediaproducts.gartner.com/reprints/wrq/119038.html
“Sounds good at the infrastructure layer…”
“But what about Data and File Access?”
The Areas of Interoperability
Management
Identity
Process
Database
Driver Access
JDBC
OLEDB
ODBC
Programmatic
Data
Network
ADO
ADO.NET
File Formats
XML
OfficeXML
Data Access
• Database Access
– Interoperability Advantages
– Ease of use, universal access, database driver availability
ADO.NET
Microsoft .NET
JDBC
Database
Java
Data Access
• Other Databases from the Microsoft Platform
• ADO.NET Managed Providers
– IBM DB2
– DB2 UDB v7.1, v7.2, v8.1 for Windows, UNIX, and Linux
– Oracle
– Oracle 8i R2, R3 (8.1.6, 8.1.7)
– Oracle 9i R1, R2 (9.0.1, 9.2)
– Oracle 10g R1 (10.1)
– Sybase
– Sybase Adaptive Server 11.5 and 11.9
– Sybase Adaptive Server Enterprise 12.0, 12.5, 12.5.1
– Any other database
– Any database accessible through OLEDB, ODBC
Mainframe data
• Database and File System Host Integration
– Broad DB2 Platform Support
•
•
•
•
OLE DB (ADO), ODBC, Managed
DB2 for MVS V5 through V8
DB2 for OS/400 V4 through V5R2
DB2 UDB V5 through V8
– OLE DB Provider for AS/400 and VSAM
• Faster than FTP for receive, slower for send
• Data conversion on the PC platform
– Data Tools
• DTS from VSAM into SQL
• New data access tool to manage connections
Data Access
• Microsoft SQL Server from Other Platforms
• SQL Server 2000 JDBC Driver SP2
– Use Case
• Application written for IBM WebSphere or BEA WebLogic
• Desire to use Microsoft SQL Server as JDBC store
– Type 4 Native SQL driver for Java/J2EE
• Supports Connection Pooling on J2EE application servers
• Drop JAR files into server and go
• Free download from MSDN
– Go to http://www.microsoft.com/sql/downloads
Data Access
• XML Parsing and Serialization
– Interoperability Advantages
– Structured format
– Industry support
– Human readable
XML Document
XML Parser
Microsoft .NET
XML Parser
Other Platform
Data Access
• XML File Interoperability
– Parsing and Serialization
– XML Parsing
• System.Xml.XMLDocument
• System.Xml.XmlReader and XmlWriter
• Interoperability with DOM and SAX in Java implementations
– XML Serialization
• XML Serializer in .NET for object to XML mapping
• Interoperable with:
– Sun JAXB (Java API for XML Binding)
– IBM WebSphere Java Beans for XML Schema
– BEA WebLogic Workshop Schema compiler
Data Access
• XML File Support in Microsoft Office 2003
– Documents can be saved as XML
• “File, Save As… XML”
• WordML (Microsoft Word)
• SpreadsheetML (Microsoft Excel)
– Creation of documents on other platforms
• New XML file using WordML or SpreadsheetML schema
• Populate data and save
• Open up in Microsoft Office
“This covers how we access Data and Files…”
“What about creating my own applications?”
The Areas of Interoperability
Custom Channels
Management
Identity
HTTP GET
Binary Channels
.NET Remoting
Process
Programmatic
Data
COM Interop
Web Services
WS-I Basic Profile
WS-*
Network
UDDI
Programmatic Interoperability
• HTTP GET (REST) Call
– Interoperability Advantages
– Practical
– Common extension to Java Servlets
XML Payload over HTTP
Microsoft .NET
Java Servlet
Programmatic Interoperability
• HTTP GET (REST) Call
– Simple, HTTP-based interoperability
– REST (Representational State Transfer)
• HTTP GET with list of parameters
– Very common when using Java Servlets
– http://site/OrderServlet?item=123&price=99&qty=1
– Response returned in XML document
• .NET calling HTTP-based Service
– Programmed via System.Net.WebRequest namespace
• SQLXML toolkit enables queries from HTTP GET
– For example, client Perl script running on Linux
Programmatic Interoperability
• Binary Communication
– Interoperability Advantages
– Performance
– Stateful data
– IPC applications
Binary Data
Formatter
Microsoft .NET
Formatter
Other Platform
Programmatic Interoperability
• Binary Communication
– .NET Remoting
• Microsoft specification
• 3rd Party implementations for Java 1.2+
– Intrinsyc Ja.NET 1.5 (http://www.intrinsyc.com)
– JNBridge Pro 1.5 (http://www.jnbridge.com)
– RMI/IIOP Channel to CORBA objects
• CORBA underlying interfaces to all EJBs
• .NET Client Implementations
– Borland Janeva (http://www.borland.com)
– Remoting.Corba (http://remoting-corba.sourceforge.net)
– IIOP.NET (http://iiop-net.sourceforge.net)
Programmatic Interoperability
• COM Interoperability
– Interoperability Advantages
– Re-use of existing Microsoft Applications
Marshaled COM call
Formatter
Microsoft .NET Assembly
Formatter
COM Component
Programmatic Interoperability
• COM Interoperability
– Many COM based (“Pre-.NET”) applications exist
• VB6, ATL, MFC, Delphi
• A need to continue support through Interoperability
– Interoperability support within Microsoft .NET
• Call an existing COM component from .NET
– Import registered component through Visual Studio .NET
– “Interop Wrapper” created
• Call a new .NET component from COM
– Export type library using TLBEXP utility
– Register the type library
– Call as if regular COM component
Mainframe Integration
• Microsoft Host Integration Server (HIS) 2004
• Transaction Integrator
– Wrap business rules with COM or .NET wrapper
• Import COBOL, parse declarations, create interface
• Publish type library to Component Services application
• VS.NET and MMC Experience
• Host Initiated Processing
– TI up to this release was WIP
– HIS looks like another CICS or IMS region
• Asynchronous solutions (without using MQSeries)
• Example: Batch process return to sender response
Programmatic Interoperability
• Web Services
– Interoperability Advantages
– Extensible framework via SOAP
– Industry support and momentum
Web Service Request /
Response
Microsoft .NET
Other Platform
Programmatic Interoperability
• WS-I : Web Services Interoperability Org.
– http://www.ws-i.org
– 170+ ISVs, SIs and Enterprise Customers
– Broad vendor support and working groups
• Profiles, Testing Tools and Sample Applications
– Profiles
• WS-I Basic Profile
• WS-I Basic Security Profile in Draft
• WS-I Attachments Profile in Draft
– Testing Tools
• Monitor and Analyzer for both C# and Java
• Vendor integration with other SOAP trace tools
Programmatic Interoperability
WS-I Basic Profile 1.0
Location
Description
Message
Schema
Expression
Transport
Programmatic Interoperability
WS-I Basic Profile 1.0
UDDI
Location
v2
Description
WSDL 1.1
SOAP
Message
1.1
XSD
Schema
1.0
Expression
XML 1.0
HTTP(S)
Transport
Programmatic Interoperability
• Web Services Support in Microsoft Products
– Microsoft .NET Framework
• Part of the Framework – no extra additions
• Compliant with the WS-I Basic Profile 1.0
• Create Web Services in any .NET Language
– C#, C++, Visual Basic .NET, J#... Even COBOL!
– Microsoft WSE (Web Services Enhancements)
• Enhances the current Web Services stack
• WS-Security, WS-SecureConversation, WS-Trust, WS-Policy
• Fully supported product
Programmatic Interoperability
• Web Services Support for Java
– Sun Microsystems
• Web Services support through JAX-RPC specification
• Java Web Services Developer Pack (JWSDP) 1.5
– IBM
• WebSphere Application Developer Studio (WSAD) 5.1.2
• WebSphere Web Services Development Kit (WSDK)
– BEA
• BEA WebLogic 8.1.4
– Open Source
• Apache Axis 1.2, Apache SOAP, GSoap
– ISV
• Systinet Server 5.0
• webMethods Glue 5.0.2
Programmatic Interoperability
• Web Services Support for Other Platforms
– C++
• Apache Axis 1.2
• Roguewave LEIF 1.2
• Systinet Server 5.0
– Perl
• Soap::Lite
– Mainframe and Midrange Integration
•
•
•
•
•
Microsoft Host Integration Server 2004
Microsoft BizTalk Server 2004
ClientSoft Service Builder 3.5
NetManage OnWeb 7.0
ASNA Datagate
“Services help me design for Interoperability”
“…but how can these work together?”
The Areas of Interoperability
Management
Message Queuing
MSMQ
Identity
IBM MQSeries
Process
Programmatic
Data
Business Process
Orchestration
Adapters
Network
Service and Process Integration
• Message Queuing
– Interoperability Advantages
– Asynchronous
– Reliable
– Transacted Calls
Message Payload
Message Payload
Other Platform
Message
Queue
Microsoft .NET
Service and Process Integration
• Accessing MSMQ from other Platforms
– HTTP SRMP in MSMQ 3.0
– JMS->COM from SpiritSoft
• Accessing other message queues from Microsoft .NET
– TIBCO and other vendors
• TIBCO RV .NET support via COM adapter
• Open source managed adapter
– IBM MQSeries (WebSphere MQ since 5.3)
•
•
•
•
MSMQ-MQSeries Bridge in HIS 2004
MQSeries Adapter for BizTalk 2004
JMS MDB listener for IBM MQSeries
WebSphereMQ 5.3 support for .NET in CSD05
Service and Process Integration
• Integration with BizTalk Server 2004
– Interoperability Advantages
– Multiple Adapter Support (250+)
CICS Adapter
Web Service
MQ Adapter
Microsoft BizTalk Server 2004
SAP Adapter
Service and Process Integration
• Process Orchestration
BizTalk Server
CICS Adapter
Orchestration
Web Service
MQ Adapter
SAP Adapter
Service and Process Integration
• Microsoft BizTalk Server 2004
– Interoperability through Adapter Layer
• Enables Web Service Fabric
– Legacy abstraction
– Overcome installations of Web services
• Minimal Code
• Schema transformations using the BizTalk Mapper
• Build Orchestrations in Visual Studio .NET 2003
Service and Process Integration
• BizTalk Server 2004 Adapter Framework
– Goals
• Consistent user experience
• Unified framework for shared services
• Ease of adapter development
– Microsoft built adapters
• Key adapters of each segment
• Reference adapters for quality and completeness
– Partner build adapters
• 250+ adapters for BTS2004 today
– Adapter certification program
• Ensuring quality and completeness of adapters
• Jointly with UNISYS to leverage lab infrastructure
“Process pulls it all together…”
“…but what about my users?
The Areas of Interoperability
Management
Authentication
Directory
Identity
Kerberos
Process
Programmatic
PKIX X509
TLS/SSL
Authorization
Data
Network
ACLs
RBAC
Identity
• Standards Compliant Authentication
– TLS/SSL, HTTP Basic, HTTP Digest, IPSec, 802.11b,
PKIX X509, EAP-TLS
• Kerberos Authentication
– Kerberos Cross Realm Trust in WSS 2003
• Tested with MIT v5 Kerberos implementation
– Products available for extending Kerberos into nonMicrosoft environments
• Vintela VAS (http://www.vintela.com)
• CyberSafe TrustBroker (http://www.cybersafe.com)
Identity
• Web SSO (Single Sign On)
– Third party solutions today
•
•
•
•
OpenNetwork Universal IdP (http://www.opennetwork.com)
Oblix COREId (http://www.oblix.com)
Netegrity SiteMinder (http://www.netegrity.com)
Entrust GetAccess (http://www.entrust.com)
– Custom development
• Moving forward with WS-Federation Passive
Client Profile
– Enables Federated Security
• Standards based approach using WS-Security
– Web SSO adapters for HttpModule and ISAPI
• Ability to extend for Apache, NSAPI etc.
Identity
• Mainframe
– Enterprise Single Sign on (ESSO)
• RACF / Topend / ACF2 AD integration
– Account Password Sync
• Windows -> Mainframe supported with HIS 2004
• 3rd party products for Mainframe -> Windows
– Proginet (http://www.proginet.com)
– Blockade Systems (http://www.blockade.com)
– M-Tech (http://www.mtechit.com)
Identity
• Identity Management
– Microsoft Identity Integration Server 2003
• Formerly MMS (Microsoft Meta-Directory Services)
– Comprehensive IDM Solution
• Synchronize identity information
• Provision and de-provision of accounts
• Self-service and helpdesk password management
Identity
• Directory Synchronization
Active Directory
–Active Directory
–Active Directory Application Mode
–Attribute value pair text files
–Delimited text files
Exchange 5.5
–Directory Services Markup Language
–Global Address Lists (Exchange)
–LDAP Directory Interchange Format
–Lotus Notes/Domino 4.6 & 5.0
–Microsoft NT 4 Domains
–Microsoft Exchange 5.5, 2000 & 2003
–Microsoft SQL 7 & 2000 databases
–Novell eDirectory v8.6.2 & v8.7
Lotus Notes
–Oracle 8i & 9i databases
–SunONE/iPlanet/Netscape Directory
–IBM Informix, DB2, dBase, Access, Excel
iPlanet
SQL
Oracle
WS-Security
• Security for Web Services
• You build a Web Service
• You want to secure it, providing:
– Integrity (This message has come from x, and hasn’t been
tampered with)
– Confidentiality (The data is this message can only be read by
the intended recipient)
Web Service Request /
Response
Microsoft .NET
Other Platform
WS-Security
• Can’t We Just Use SSL?
• SSL provides integrity and confidentiality, but at the
transport level
• Limitations with Web Services:
–
–
–
–
Point to point communication
No way of applying security to just part of the message
Really only good for HTTP based connections
Security is removed after the transport layer
Web Service Request /
Response
Microsoft .NET
Other Platform
WS-Security
• Introducing WS-Security
– Message Level Security
• SOAP Headers provide integrity and confidentiality
• OASIS Specification (WS-Security 1.0) – April 2004
• Applicable to other transports in addition to HTTP
Web Service Request /
Response
Microsoft .NET
Other Platform
WS-Security
• Introducing WS-Security
– Sure, but who is adopting it?
•
•
•
•
•
•
•
•
•
•
•
Microsoft (Web Services Enhancements) WSE 2.0
BEA WebLogic 8.1.3
IBM WebSphere 5.1.2 (OASIS compliant in 6.0)
Systinet Server 5.0
Sun Microsystems JWSDP 1.5
Oracle (through acquisition of Phaos)
webMethods Glue 5.0.2
Apache Projects (WS-FX and Axis-WSSE)
RSA BSAFE
Verisign TSIK Toolkit (xmldsig and xmlenc)
Entrust Authority Security Toolkit (xmldsig and xmlenc)
“Identity secures it all…”
“…but how do I manage all of this?”
The Areas of Interoperability
Management
Identity
Management
Process
Programmatic
WMI
WBEM
CIM
Data
Network
SNMP
Management
• Management and Interoperability
– Extending Microsoft Operations Manager (MOM)
• Management Packs (MP)
• MOM Connector Framework (MCF)
– Interoperability with other management systems
Product Connector
MOM 2004 Management Group
Other Mgt Framework
e.g. Tivoli, OpenView etc.
Management
• Management and Interoperability
– MOM Connector Framework (MCF)
• eXc (http://www.excsoftware.com)
– WMI event provider for MVS and AS/400
– Handles MVS highlighted messages and WTORs
• Skywire (http://www.skywiresoftware.com)
– Integration of MOM with help desks
– Forwards alerts to help desks through iWave adapters
• Aprisma (http://www.aprisma.com)
– Integration of SNMP management with MOM
• Integration of MOM alerts
– Support for Tivoli, CA today
– HP and Micromuse (to be announced)
Management
• Management and Interoperability
– MOM Extensions for Web Services
• Actional (http://www.actional.com)
– Actional Web Services Management Platform
• AmberPoint (http://www.amberpoint.com)
– Amberpoint Management Foundation
• CA (http://www.ca.com)
– Unicenter Web Services Distribution Management
(Unicenter WSDM)
Management
• Management and Interoperability
– Microsoft SMS 2003
• Vintela (http://www.vintela.com)
– UNIX and Linux inventory and software distribution
– VMX (Vintela Management Extensions) built around
OpenWBEM
• Xcellenet Afaria (http://www.excellenet.com)
– Management of PDAs from SMS
– PocketPC, Palm and RIM
“The coverage of the topics has been interesting…”
“…but how do I piece all this together?”
MSF – Microsoft Solutions Framework
Envisioning
Planning
Building
MOF – Microsoft Operational Framework
Deploying
Changing
Operating
Supporting
Optimizing
The Areas of Interoperability
Management
Identity
Process
Programmatic
Data
Network
• Piecing Together
– Whole greater than sum
of parts
• Realize advantages
• Create opportunities
– Aggregation Patterns
• Aggregated Service
• Aggregated View
Conclusion
• Microsoft and Interoperability
• Works with what you have; Interoperable by Design
• Layered model to represent the six areas
• Think of the whole problem
• Resources
• Back of this deck
• Interop Month
– http://www.interopmonth.com
• Web Services Interoperability Home Page
– http://msdn.microsoft.com/webservices/building/interop
• My Blog
– http://www.michael_platt.com
• My Email
– [email protected]
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
Services for UNIX (SFU)
•
•
Services for UNIX v. 3.5 provides the tools and environment that IT professionals and
developers need to:
Integrate Windows and UNIX/Linux
environments
• Partners:
Migrate UNIX applications to Windows
– X-Win32, Vintela, F-Secure, Interop
Systems
Interoperability
•
Full range of cross-platform services for blending
Windows and UNIX-based environments.
•
Single sign-on, seamless file and print accessibility,
and easy administration
Integration
•
IT professionals can use the UNIX-based tools and
utilities they are already familiar with on the Windows
platform.
•
Remotely monitor and administer Windows-based
systems in the same fashion as UNIX-based systems.
Extensibility
•
Run UNIX applications side by side with modern, bestof-breed Windows and .NET applications – all on a
single, easy to manage and familiar platform.
•
Wrap UNIX calls in COM wrappers and expose your
legacy UNIX applications as web services
Relevant standards supported
•
UNIX, POSIX, NFS, NIS, X11, BSD Sockets, …
•
Case studies
–
–
http://www.microsoft.com/windows/sfu
http://www.unixproresources.com
Services for Netware (SFN)
•
Feature description
– SFN includes a Directory
Synchronization service which
enables NDS, eDirectory object
migration to Active Directory; a
File Migration Utility which
migrates user files while also
preserving user ACLs after
migration.
•
Key interop scenarios
– Enables migration from
NDS/eDirectory to Active Directory
as well as user file migration
which preserves access control
information
•
Relevant standards supported
(and interoperability with 3rd party
products)
•
Technical resources
– http://www.microsoft.com/windows
server2003/sfn
.NET Remoting
•
Feature description
–
.NET Remoting is a binary protocol that
can be used to enable interoperability
between applications written for .NET
and J2EE.
•
Technical resources
–
–
•
Key interop value scenario
–
•
Until Web Services are able to support
binary and TCP communications (think:
Indigo), .NET Remoting can be used as
a tactical solution to achieve
interoperability and bridge the gap.
Good for accounts who have high
performance interop needs.
Relevant standards supported (and
interoperability with 3rd party products)
–
.NET Remoting is a Microsoft
specification, released with v1.0 of the
.NET Framework, but is open to license
by third parties.
–
http://www.amazon.com/exec/obidos/ASIN/07
35619220/qid%3D1058741448/102-87631239255368
Intrinsyc Ja.NET 1.5
(http://www.intrinsyc.com)
JNBridge Pro 1.5 (http://www.jnbridge.com)
RMI/IIOP and CORBA
•
Feature description
–
•
Key interop value scenario
–
•
CORBA is the underlying specification
of the majority of EJB application
servers. RMI/IIOP is the remoting
transport used to expose CORBA
objects. To date, Microsoft has not
support for the CORBA specification.
Finding a solution that interoperates
with CORBA is useful for Java
accounts that wish to maintain their
existing investment in CORBA and do
not wish to embrace Web Services or
.NET Remoting. Typically, CORBA is
found in Financial and Telecom
verticals.
Relevant standards supported (and
interoperability with 3rd party products)
–
CORBA is a specification of the OMG.
(http://www.corba.org)
•
Technical resources
–
–
–
Borland Janeva (Commercial)
(http://www.borland.com)
Remoting.Corba (Open Source)
(http://remoting-corba.sourceforge.net)
IIOP.NET (Open Source) (http://iiopnet.sourceforge.net)
XML Interoperability
• Feature description
– XML provides one of the most
structured ways of achieving
interoperability today. It is the
foundation of Web services
and many third party solutions.
• Key interop value scenario
– XML Parsing and Serialization
is available for almost every
platform and language.
• Relevant standards supported
(and interoperability with 3rd
party products)
– XML (http://www.xml.org)
• Technical resources
– webMethods (have an
implementation of XML
Serialization that offers good
interoperability with .NET)
– http://www.webmethods.com
– http://www.castor.org
– http://java.sun.com/xml/jaxb/
Web Services Interoperability
•
Feature description
–
•
Web services toolkits are now available
for typically all platforms and languages
Key interop value scenario
–
Web services provide an industry
recognized and supported way of
achieving interoperability regardless of
the platform and language.
•
Technical resources
– Apache AXIS 1.1
• http://ws.apache.org/axis/
– IBM WSAD 5.x
• http://www.ibm.com/websphere
– BEA Weblogic 8.1
• http://www.bea.com
– webMethods GLUE 4.1
• http://www.webmethods.com
•
Relevant standards supported (and
interoperability with 3rd party products)
–
WS-I Basic Profile 1.0 (http://www.wsi.org)
– Systinet WASP Server 4.6
• http://www.sysinet.com
– RogueWave LEIF 1.2
• http://www.roguewave.com
– SOAP::Lite
• http://www.soaplite.com
WSE Interoperability
•
•
•
Feature description
–
WSE (Web Services Enhancements)
is our implementation of the next
generation WS-* standards and
specifications. WSE 1.0 was
released in Dec 2002. WSE 2.0 is
currently in technical preview (as of
Feb 2004)
•
Case study
–
•
•
Key interop scenarios
–
For WSE interop scenarios, see
technical resources. Today, WSSecurity has the most proven set of
case studies due to the maturity of
the spec
Relevant standards supported (and
interoperability with 3rd party products)
–
We have two interoperability articles on
MSDN that demonstrate WSE 1.0 WSSecurity interop (authentication only)
• IBM WSTK:
•
•
http://msdn.microsoft.com/webservices/building/wse/
default.aspx?pull=/library/enus/dnwebsrv/html/wsejavainterop.asp
GLUE 4.0.1:
http://msdn.microsoft.com/library/default.asp?url=/libr
ary/en-us/dnwebsrv/html/wsejavainterop2.asp
Technical resources
–
–
WSE
(http://msdn.microsoft.com/webservices)
IBM ETTK – IBM’s implementation as an
Alphaworks project
•
http://alphaworks.ibm.com/tech/ettk
•
http://www.webmethods.com
–
WebMethods GLUE – ISV implementation
acquired from TME. Good alignment with
WSE.
–
.NET and J2EE Interoperability Toolkit
(shows WS-Security, WS-Routing and WSAttachments interop)
WS-*
•
http://www.amazon.com/exec/obidos/ASIN/0735
619220/qid%3D1058741448/102-87631239255368
MQ Series Interoperability
•
Key interop scenarios
•
Relevant standards supported
(and interoperability with 3rd party
products)
– MQS to .NET
– MA0C, a SupportPac from IBM
shows a technical preview of
exposing a SOAP endpoint from
an implementation of MQS.
•
Technical resources
– Host Integration Server 2000
(2004) – contains an MSMQ –
MQSeries bridge
• http://www.microsoft.com/hiser
ver
– IBM’s support for .NET in their
CSD05 release:
• http://publibb.boulder.ibm.com/Redbooks.n
sf/9445fa5b416f6e32852569ae00
6bb65f/371eaf26a479ef0385256
d250050f289?OpenDocument
– .NET and J2EE Interoperability
Toolkit (shows multiple options
for connecting with MQS
implementations)
• http://www.amazon.com/exec/obid
os/ASIN/0735619220/qid%3D105
8741448/102-8763123-9255368
HIS Transaction Integrator
•
Feature description
– Visual Studio Designer, COM or
Managed Runtime for integrating
and extending mainframe (CICS,
IMS) and midrange (AS/400)
programs using the Windows
Server System.
•
Key interop scenario
•
Relevant standards supported
– Enable enterprise developers to
move towards a services-oriented
architecture (SOA) using the .NET
Framework.
– VSIP-enabled TI Designer, CICS
Link over SNA or TCP/IP, IMS
Connect over TCP/IP, CICS
Enhanced TCP/IP, Reliable 2PC
Distributed Transactions across
SNA LU6.2.
• Case study
– http://www.microsoft.com/r
esources/casestudies
HIS Host Initiated Processing
•
Feature description
– Network listeners that allow a
Windows Server computer to
function as a peer to IBM
mainframe and AS/400
computers, enabling LOB
Windows applications to
participate in a distributed
enterprise solution.
•
Key interop value scenario
– HIP allows enterprises to more
effectively move portions of their
application logic or data onto the
more cost-effective Windows
Server and SQL Server platforms,
while ensuring logical and secure
bi-directional application
communication.
•
Relevant standards supported
– VSIP-enabled TI Designer, CICS
Link over SNA or TCP/IP, AS/400
DPC over TCP/IP.
HIS Data Providers
•
Feature description
–
•
Key interop value scenario
–
•
Set of reliable, scalable, high
performance Data Providers for
integrating legacy data using industrystandard data access architectures.
Publish vital data stored in IBM DB2
File Systems (mainframe VSAM and
midrange AS/400, AS/36) using
Microsoft Data Providers supporting
industry-standard architectures.
Relevant standards supported
–
–
–
–
–
ODBC, OLEDB, ADO, ADO.NET
DDM, DRDA
SQL Server 2000 (DTS, Replication,
OLAP)
Office 2003 (Excel, Access, InfoPath)
Visual Studio .NET
•
Case study
– http://www.microsoft.com/resource
s/casestudies
HIS Network Services
•
Feature description
– Industry-standard technologies
and services allowing network
administrators to move towards
pure TCP/IP WANs and
datacenters.
•
Key interop value scenario
•
Relevant standards supported
– No longer do enterprises have to
remotely administer branch cluster
controllers, utilize expensive data
link switching (DLSw) capable
routers, or maintain costly front
end processors (FEPs). With HIS
Network Services, enterprises can
continue to consolidate their
network infrastructure, while
supporting the same level of SNAcompatible applications and
services.
– SNA, DLC, LU0, LU1, LU2, LU3,
LU6.2
– IBM Enterprise Extender HPR/IP
•
Case study
– http://www.microsoft.com/resource
s/casestudies
HIS Enterprise Single Sign-On
•
•
•
Feature description
–
Secure access across your enterprise
by offering end users and application
developers single sign-on to host
sessions and programs.
Key interop value scenario
–
Provides end-to-end single sign-on
solution between Windows and IBM
Legacy Host systems by integrating
with TI (WIP and HIP), Data Providers
and SNA Services. By offering a
centralized secure credential database,
it makes it easy for users and
administrators to manage their
credentials in a secure manner. In
addition, password synchronization
keeps the user passwords in sync
between Windows Active Directory and
directory stores on IBM systems.
Relevant standards supported
–
–
–
RACF, ACF/2, TopSecret
AS/400
Windows Active Directory
•
Case study
–
http://www.microsoft.com/resources/ca
sestudies
HIS MSMQ-MQSeries Bridge
•
Feature description
– Integrate Windows applications
using industry-popular MQMQ
with heterogeneous systems
running IBM MQSeries
messaging.
•
Key interop value scenario
•
Relevant standards supported
– Move towards a Services Oriented
Architecture using flexible,
asynchronous messaging based
on MSMQ and Visual Studio .NET.
Integrate these solutions with
enterprise-wide messaging-based
applications using MSMQMQSeries Bridge, supporting high
throughput and reliable
transactions.
– TCP/IP and SNA LU6.2
– Reliable 2PC Distributed
Transactions
– MQSeries
– MSMQ
• Case study
– http://www.microsoft.com/reso
urces/casestudies