Web Services Interoperability Architecture Symposium – Malaysia, March 2005

1. Web Services InteroperabilityArchitecture Symposium – Malaysia, March 2005 Simon Guest Program Manager Architecture Strategy Microsoft Corporation Part III

2. Agenda • Part I – Introduction (9:00 – 10:00) • Microsoft and Interoperability – where are we? • Web Services Interoperability • Understanding and using the WS-I Basic Profile • Part II – Strategies (10:15 – 11:15) • Top Ten Tips for Interoperability • Security • Attachments • Part III – Advanced (11:30 – 12:30) • Mainframes and Web Services • Piecing this all together • Understanding Indigo • Part IV – Q&A, Lunch (12:30 +)

3. Interoperability using Web Services We’ve seen .NET and Java – how about mainframes?

4. Web Services Interoperability • Exposing Web Services from Mainframes • Database (DB2) Access • Asynchronous (MQ Series) Access • Business Logic Interface (BLI) • Access via callable interfaces • Screen Logic Interface (SLI) • Access via Screen Scraping • TN3270, 3270 Bridge or FEPI • Presentation Integration (3270 -> HTML) • Programmatic Integration (3270 -> objects)

5. Web Services Interoperability • Mainframe Integration • Interoperability Advantages • ‘Unlocking’ of existing production applications • Performance, but requires callable interfaces BLI (Business Logic Interface) Microsoft .NET Mainframe

6. Web Services Interoperability • 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

7. Web Services Interoperability • 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

8. Web Services Interoperability • Network and Identity Integration with HIS 2004 • TCP/IP now surpassing SNA • Customer Upgrading to New z900 Mainframes • IBM Retiring SNA FEP and CC Hardware • High end DLSw Routers are expensive • HIS 2004 includes IP-DLC Link Service • Based on IBM APPN HPR/IP (RFC 2535 IP-DLC) • Identity Integration • Account Password Changes • 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)

9. Web Services Interoperability • Mainframe Integration • Interoperability Advantages • ‘Unlocking’ of existing production applications • Provides “non-invasive” integration with Mainframes SLI (Screen Logic Interface) Microsoft .NET Mainframe

10. Web Services Interoperability • 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

11. SLI (Screen Logic Interface) Integration

12. Service and Process Integration • NetManage OnWeb Object Builder • Microsoft Gold Certified Partner • Librados acquisition in 2004 • OnWeb 7.1 Evaluation CD • Pick-up after this presentation

13. Interoperability using Web Services You mentioned other transports – is this even possible?

14. Other Transports • Web Services over HTTP • Pervasive today, but doesn’t fit every problem: • Asynchronous Access • “I want to call a Web Service and get it to respond to me in 7 days” • Peer-to-Peer Web Service Communication • “How do I reach Jim’s Web Service? He’s behind a Firewall in another organization” • Offline Web Services • “I’m on an airplane at 30,000 ft – how does my Web Service application store sent messages?” • I’m Looking For Something Lighter Than IIS • How can application A talk to application B on the same machine?

15. Other Transports • Custom Transports • Microsoft WSE 2.0 solves this by defining a “Custom Transport” API • Provides ability to write new channel and URI scheme • You write how to access the channel, import as DLL • Works alongside WS-* specifications • No need to do anything else when applying WS-Security • Examples Today: • TCP and inproc – supplied with WSE 2.0 • MSMQ – http://codeproject.com/useritems/SoapMSMQ.asp • SMTP – http://hyperthink.net • UDP – http://dynamic-cast.com • SQL Server –http://mtaulty.com • IPC and Named Pipes –http://www.mug.org.ar • IBM MQ Series – http://workspaces.gotdotnet.com/wsemqs

16. Using an Alternative Transport to HTTP

17. Interoperability using Web Services How does Microsoft BizTalk Server work with Web Services?

18. Service and Process Integration • Integration with BizTalk Server 2004 • Interoperability Advantages • Multiple Adapter Support (250+) • Process Orchestration CICS Adapter Web Service MQ Adapter Microsoft BizTalk Server 2004 SAP Adapter

19. Service and Process Integration • Integration with BizTalk Server 2004 • Interoperability Advantages • Multiple Adapter Support (250+) • Process Orchestration CICS Adapter BizTalk Server Orchestration Web Service MQ Adapter SAP Adapter

20. 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 BizTalk Mapper • Build Orchestrations in Visual Studio .NET 2003 • WSE 2.0 Adapter now available

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

22. Interoperability using Web Services What is Indigo, and how will this affect me?

23. TransactedMethods Instance Manager Context Manager ServiceMethods TypeIntegration DeclarativeBehaviors ASP.NET .container .exe NT Service DllHost Indigo Architecture Messaging Services Service Model Queuing Routing Connector Eventing Channels (Datagram, Reliable, Peer, …) Policy Engine … Channel Security Transport Channels (IPC, HTTP, TCP…) Message Encoder System Services Transaction Communications Manager (Port) Federation Hosting Environments …

24. The “Indigo” Connector • The “Indigo” Connector is based on four simple concepts • Messages are in-memory SOAP envelopes • Services are targets for message delivery • Ports are a (named) location in network space • Channels allow message I/O through a port • All “Indigo” applications rely on these concepts directly or indirectly

25. Unified Programming Model ASMX and WSE .NET Remoting Enterprise Services System.Messaging Simple ConfigInteroperableService-Oriented Broad VisionExtensibility Object-Oriented AttributesTransactionsComponents QueuingReliable MsgDurable Msg Indigo Indigo is a superset of the capabilities of our existing stacks

26. Preparing For "Indigo" Today • Build using .NET Web Services • Use .NET Enterprise Services within your service… • If you need ES functionality • If you need fast/secure intra-farm • Use .NET Remoting within your service… • If you need lightweight CLR-CLR

27. Interoperability using Web Services How does this all piece together?

28. “Avalon Bill Payer”

29. Agenda • Part I – Introduction (9:00 – 10:00) • Microsoft and Interoperability – where are we? • Web Services Interoperability • Understanding and using the WS-I Basic Profile • Part II – Strategies (10:15 – 11:15) • Top Ten Tips for Interoperability • Security • Attachments • Part III – Advanced (11:30 – 12:30) • Mainframes and Web Services • Piecing this all together • Understanding Indigo • Part IV – Q&A, Lunch (12:30 +)

30. Interoperability using Web Services Where can I go for more information?

31. Conclusion • Resources • “Interoperability Month” • http://www.interopmonth.com • Web Services Interoperability Home Page • http://msdn.microsoft.com/webservices/building/interop • Java Interoperability Home Page • http://msdn.microsoft.com/vstudio/java/interop • My Blog (inc. these slides!) • http://www.simonguest.com • Other Blogs • Brian Keller (http://blogs.msdn.com/briankel/) • Ted Neward (http://www.neward.net/ted/weblog/) • Dino Chiesa (http://blogs.msdn.com/dotnetinterop/) • Interop Warriers (http://www.interopwarriers.com) • My Email • sguest *AT* microsoft.com

32. Conclusion • 14 Pre-Recorded Web Casts Available Now!

33. sguest@microsoft.com © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.