1 / 101

Microsoft and Interoperability

Microsoft and Interoperability. Simon Guest Program Manager Architecture Strategy Microsoft Corporation. About This Informational. Microsoft and Interoperability What is Microsoft’s Interoperability story? Questions from individuals, customers and organizations

adolph
Download Presentation

Microsoft and Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft and Interoperability Simon Guest Program Manager Architecture Strategy Microsoft Corporation

  2. About This Informational • Microsoft and Interoperability • What is Microsoft’s Interoperability 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 Informational • Think about interoperability in a different way

  3. “Let’s start…” “How do you define Interoperability?”

  4. 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]

  5. Executive Email – Bill Gates http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp

  6. Executive Email – Bill Gates http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp …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)…

  7. Executive Email – Bill Gates http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp Designed for Interoperability Works with What You Have

  8. Executive Email – Bill Gates http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp Designed for Interoperability Works with What You Have

  9. Designed for Interoperability Works with What You Have The Areas of Interoperability Management Identity WS-* Process Web Services Programmatic XML Data Network

  10. The Areas of Interoperability Management Identity Process Programmatic Data Network

  11. NFS/NIS AppleTalk IPX/SPX The Areas of Interoperability Networking Protocols Management TCP/IP Identity DNS DHCP/BOOTP Process 802.1x Programmatic Data Network

  12. 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

  13. 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

  14. 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

  15. Network and Infrastructure • Interoperability with UNIX and Linux • Microsoft SFU (Services for UNIX) 3.5 NFS NIS V2 and v3 NFS / NIS support over TCP/IP UNIX or Linux Client or Server Windows Client, Server or Gateway

  16. 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

  17. Windows SFU 3.5 (Services For Unix) and Linux

  18. “Sounds good at the network layer…” “But what about Data and File Access?”

  19. The Areas of Interoperability Database Driver Access Management JDBC Identity OLEDB ODBC Process ADO Programmatic ADO.NET File Formats Data XML OfficeXML Network

  20. Data Access • Database Access • Interoperability Advantages • Ease of use, universal access, database driver availability ADO.NET Microsoft .NET JDBC Database Java

  21. 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 • DB2 UDB v6.1 for OS/390, v7.x for OS/390 and z/OS • DB2 UDB V4R5, V5R1, V5R2 for AS/400 • 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

  22. 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

  23. Data Access • XML Parsing and Serialization • Interoperability Advantages • Structured format • Industry support • Human readable XML Document XML Parser XML Parser Other Platform Microsoft .NET

  24. 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

  25. 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

  26. Office XML support on non-Microsoft Platforms

  27. “This covers how we access Data and Files…” “What about creating my own services?”

  28. The Areas of Interoperability Management Custom Channels HTTP GET Identity Binary Channels .NET Remoting Process COM Interop Programmatic Web Services WS-I Basic Profile Data WS-* Network UDDI

  29. Programmatic Interoperability • HTTP GET (REST) Call • Interoperability Advantages • Practical • Common extension to Java Servlets XML Payload over HTTP Java Servlet Microsoft .NET

  30. 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

  31. Programmatic Interoperability • Binary Communication • Interoperability Advantages • Performance • Stateful data • IPC applications Binary Data Formatter Formatter Other Platform Microsoft .NET

  32. 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)

  33. Programmatic Interoperability • COM Interoperability • Interoperability Advantages • Re-use of existing Microsoft Applications Marshaled COM call Formatter Formatter Microsoft .NET Assembly COM Component

  34. 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

  35. Programmatic Interoperability • Web Services • Interoperability Advantages • Extensible framework via SOAP • Industry support and momentum Web Service Request / Response Other Platform Microsoft .NET

  36. 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

  37. Location Description Message Schema Expression Transport Programmatic Interoperability WS-I Basic Profile 1.0

  38. UDDI v2 Location Description WSDL 1.1 SOAP 1.1 Message XSD 1.0 Schema Expression XML 1.0 Transport HTTP(S) Programmatic Interoperability WS-I Basic Profile 1.0

  39. WSDL Customer Datatypes CreateCustomerRequest CreateCustomerResponse Interfaces Doc/Literal Binding http://server1/custsvc.asmx Address WSDL Code Endpoint Programmatic Interoperability public class MyService { public Result CreateCustomer(Cust c) { // some code } } Web Service

  40. Download WSDL Proxy WSDL Code Code Endpoint Programmatic Interoperability Web Service Client

  41. Proxy WSDL Code Code Endpoint Programmatic Interoperability Web Service Client “Please create customer” SOAP Request SOAP, XSD, XML Using HTTP

  42. Proxy WSDL Code Code Endpoint Programmatic Interoperability Web Service Client “Created OK” SOAP Response SOAP, XSD, XML Using HTTP

  43. 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

  44. 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

  45. 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

  46. Web Services Interoperability

  47. “Services help me design for Interoperability” “…but how can these work together?”

  48. Message Queuing MSMQ IBM MQSeries The Areas of Interoperability Management Identity Mainframe/Midrange Integration Process BLI / SLI / Data Programmatic RPG Business Process Data Orchestration Network Adapters

  49. Message Payload Message Payload Service and Process Integration • Message Queuing • Interoperability Advantages • Asynchronous • Reliable • Transacted Calls Other Platform Message Queue Microsoft .NET

  50. 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 • Why don’t you support JMS? • 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

More Related