Hide Notes 

Slide 1: Achieving Interoperability: Microsoft .NET and J2EE Simon Guest Program Manager Architecture Strategy Microsoft Corporation Charles Liptaak Partner Solution Architect Enterprise Partner Group Microsoft Corporation
Slide 2: Agenda  Interoperability fundamentals    Comparing the stacks Why interoperate? Common scenarios for interoperability Sending data between tiers Enabling point to point interoperability with J2EE Standards and interoperability Resource tier interoperability   Dealing with complex data types  Products and technology     Conclusion, more info, and questions and answers
Slide 3: Agenda  Interoperability fundamentals    Comparing the stacks Why interoperate? Common scenarios for interoperability Sending data between tiers Enabling point to point interoperability with J2EE Standards and interoperability Resource tier interoperability   Dealing with complex data types  Products and technology     Conclusion, more info, and questions and answers
Slide 4: Comparing the stacks Enterprise solutions … … Third party extensions P&P blocks Extensions: Extensions: Phoenix, Tiles, Java Faces Eclipse Python Struts Visual Studio.net ASP.Net JSP Servlets Webshpere Studio Perl Java ADO.NET Base Class Library CLR JDBC J2EE Class Library Java runtime J2EE App Servers Websphere, Weblogic, Tomcat, etc. C++ C# Win32 MSMQ, COM+, IIS, WMI, AD, ADAM, Indexing, UDDI, etc. BEA Weblogic VB JMS Apache Win32, Unix, Linux
Slide 5: Why interoperate???  To re-use existing systems   Integration of legacy systems Extends life of current systems, and (more importantly) knowledge  Proof of concepts   Rip and replace is no longer an option Increases technical agility  Migration   Migration is not an ‘overnight’ process Allows for planned, correctly executed migrations  Lower project costs   Development time and resource cost savings Faster go-to-market (GTM) G A LI I Y T
Slide 6: Interoperability Scenarios Technology-Aligned Development Presentation Tier Business Tier Resource Tier J2EE JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker .NET
Slide 7: Interoperability Scenario #1 Creating a new user interface… Presentation Tier Business Tier Resource Tier JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker
Slide 8: Interoperability Scenario #1 …or standardizing on an existing one Presentation Tier Business Tier Resource Tier JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker
Slide 9: Interoperability Scenario #2 Interoperability at the Business Tier Presentation Tier Business Tier Resource Tier JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker
Slide 10: Interoperability Scenario #2 Interoperability at the Business Tier Presentation Tier Business Tier Resource Tier JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker
Slide 11: Interoperability Scenario #3 Sharing of common resources (data) Presentation Tier Business Tier Resource Tier JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker
Slide 12: Interoperability Scenarios In conclusion, 3 types of interoperability  Point to Point   Synchronous Between two points Asynchronous Handles more than two points Synchronous More complex  Resource Tier    Presentation Tier  
Slide 13: Agenda  Interoperability fundamentals   Why interoperate? Common scenarios for interoperability Sending data between tiers Enabling point to point interoperability Standards and interoperability Resource tier interoperability   Dealing with complex data types  Products and technology     Conclusion, more info, and questions and answers
Slide 14: Complex Data Types Beyond the ‘Hello World’ example Full Name Daniel Ingitaraj Tier Presentation Tier Business Company Name Address JSPs Servlets Resource Tier Microsoft Microsoft Corp (India) Pvt Ltd POJOs Database EJBs Prestige Takt 23 Kasturba Road Cross Bangalore – 560 001 Message “Hello World” Queue India +91-80-2121212 +91-80-2121800 Serviced Components danieli@microsoft.com Broker Client Work Tel Fax Email ASP.NET Last Updated 4 Jan 2003, 11:23.37am
Slide 15: Interoperability Is About Data Challenges      Data types exist on one platform, but not on the other java.sql.ResultSet in Java System.Data.DataSet in .NET Similar functionality, different data Also, does a String on one == a String on the other?  It’s all about serialization   Taking a data type on one platform and converting it such that it can be transported to, and understood by the other Two types of serialization   Binary XML
Slide 16: Interoperability Is About Data Common symptoms of data breakdown     Method or component cannot be exposed  Data type cannot be serialized Serialization seemed to work, but cannot be consumed You sent me what? Hang on, you didn’t send me anything Method or component can be exposed  I thought you were sending me the order?  Urgh… a NullPointerException  ASP.NET Order 789 Order 123 POJOs EJBs
Slide 17: Interoperability Is About Data Mitigating risks of data interoperability  Data first, then code     Avoid merging schemas Use a static canonical schema Keep to XSD types Build and maintain unit tests  Architect a central repository   Uniform naming convention Consider repository for data types within organization
Slide 18: Agenda  Interoperability fundamentals   Why interoperate? Common scenarios for interoperability Sending data between tiers Mitigating risk Enabling point to point interoperability Standards and interoperability Resource tier interoperability  Dealing with complex data types    Products and technology     Conclusion, more info, and questions and answers
Slide 19: Interoperability Technologies  Point to Point Interoperability   Direct, between two points, calls tend to be synchronous Three technology options for .NET and J2EE Interoperability    .NET Remoting RMI/IIOP CORBA Channel XML Web services
Slide 20: Point To Point Interoperability .Net Remoting  Microsoft specification (available to license)  Third-party implementations for Java 1.2+   Intrinsyc Ja.NET 1.5 (http://www.intrinsyc.com) JNBridge Pro 1.4 (http://www.jnbridge.com)  Competitor or complimentary to Web services? Binary communication over TCP (Performance) Inter-process communication (Simplicity) Pass by reference (Flexibility)  Interoperability benefits   
Slide 21: Point To Point Interoperability RMI/IIOP Channel to CORBA  OMG specification  .NET client proxy implementations    Borland Janeva (http://www.borland.com) Remoting.Corba (http://remoting-corba.sourceforge.net) IIOP.NET (http://iiop-net.sourceforge.net)  Interoperability benefits    Binary communication over TCP (Performance) No modifications required on the server (Simplicity) Suited for .NET client -> Java server applications
Slide 22: Point To Point Interoperability Web Services    Microsoft .NET Framework Support SOAP, XML and Web Services from day one Open source: Apache AXIS 1.1 Vendor value-add: IBM WSTK (ETTK) 1.1 J2EE vendor support: IBM WSAD 5.1, BEA Weblogic 8.1 ISV support: webMethods GLUE 4.1.2 Sun have reference implementation IBM have technical preview Firewall (and inter-organization) friendly (Transparency) SOAP based framework (Extensibility) Massive industry momentum (Standardization) Multiple Java Implementations (pre J2EE 1.4)      Post J2EE 1.4    Interoperability benefits   
Slide 23: Standards And Interoperability      WS-I (Web Services Interoperability Org.)  http://www.ws-i.org Broad and working-group participation 170+ ISVs, SIs and Enterprise Customers  Goal to deliver resources, samples and tools WS-I Basic Profile 1.0 – Aug 2003  SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0, XSD 1.0 WS-I Basic Profile Testing Tools    WS-I Monitor (trace tool) WS-I Analyzer (analyzer against BP 1.0) (C# and Java)
Slide 24: Standards And Interoperability  Looking Ahead   Interoperability Today = Connectivity Requirement for Application Interoperability      How about securing a Web Service? Can we use Web Services for routing? Are Web Service calls reliable? Transactional Web Services (ACID and long lived) Sending an attachment over a Web Service
Slide 25: Standards And Interoperability WS-* Specifications Timeline Trust Security Policy Secure Conversation Infoset Addendum to SOAP Messages w/ Attachments (MTOM) Federation Addressing Active Profile Passive Profile Eventing Routing Coordination Reliable Messaging MetaData Exchange Referral Security Transaction Oct Nov 2001 2001 WSInspection April 2002 June 2002 August 2002 December 2002 Policy Policy Attachment Policy Assertions March April 2003 2003 Reliable Messaging Addressing June 2003 Policy v1.1 July 2003 Sept Jan Feb Mar 2003 2004 2004 2004 Discovery Attachments Security Addendum Security Profile For Tokens Coordination Atomic Transactions Business Activity Policy Attachment v1.1 Policy Assertions v1.1 Security Roadmap Reliable Message Roadmap Federation of Identities in a WS World http://msdn.microsoft.com/webservices/understanding/specs
Slide 26: Standards And Interoperability   Snapshot of Today’s WS-* Implementations IBM    ETTK (Emerging Technologies Toolkit) 1.1 http://www.alphaworks.ibm.com/tech/ettk Alphaworks project. WSAD uses stable drops. GLUE 4.1.2 http://www.webmethods.com WS-* support in latest drops, inline with WSE WSE (Web Services Enhancements) 2.0 TP http://msdn.microsoft.com/webservices Short release cycle, leading into Indigo  webMethods     Microsoft   
Slide 27: Standards And Interoperability WS-* Specifications Timeline Trust Security Policy Secure Conversation Infoset Addendum to SOAP Messages w/ Attachments (MTOM) Federation Addressing Active Profile Passive Profile Routing Coordination Reliable Messaging Eventing MetaData Exchange Referral Security Transaction Oct Nov 2001 2001 WSInspection April June August 2002 2002 2002 Attachments Security Addendum Security Profile For Tokens December 2002 Policy Policy Attachment Policy Assertions March April June 2003 2003 2003 Reliable Messaging Addressing Policy v1.1 Policy Attachment v1.1 Policy Assertions v1.1 July Sept Jan Feb Mar 2003 2003 2004 2004 2004 Coordination Atomic Transactions Business Activity Discovery Security Roadmap Reliable Message Roadmap Federation of Identities in a WS World http://msdn.microsoft.com/webservices/understanding/specs
Slide 28: Standards And Interoperability WS-* Specifications Timeline - Releases WSE vNext WSE v1.0 March April June 2003 2003 2003 WSE v2.0 July Sept Jan Feb Mar 2003 2003 2004 2004 2004 2005 2006 Web Services Architecture (WSA) Longhorn
Slide 29: Standards And Interoperability  Demo: Web Services Scenario   Microsoft Outlook to J2EE CRM Application WS-Security using WSE 1.0 SP1 webMethods GLUE 4.1 X509 Certificate Web Services call WS-Security .NET Framework WSE 1.0 SP1 Microsoft Outlook XP Session and BMP EJBs J2EE CRM Service JBoss 3.07 SQL Server 2000 Database
Slide 30: WS-Security Interoperability
Slide 31: Demo Resources  MSDN References   Outlook XP with .NET Smart Client Add-In  http://msdn.microsoft.com/library/en-us/dnoxpta/html/odc_dnscof.asp WS-Security Authentication Interop using X.509 Certificate   IBM WSTK: http://msdn.microsoft.com/webservices/building/wse/default.aspx?pull =/library/en-us/dnwebsrv/html/wsejavainterop.asp   GLUE 4.0.1: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/ht  Feedback:  How could we extend this to make it better?
Slide 32: Interoperability at the Resource Tier of common resources (data) Sharing Presentation Tier Business Tier Resource Tier JSPs Servlets POJOs EJBs Database Client Message Queue ASP.NET .NET Assemblies Broker
Slide 33: Interoperability Technologies  Interoperability at the Resource Tier    Arbitrated, mostly asynchronous, between two or more points Can utilize point to point technology for connectivity For .NET and J2EE Interoperability    Shared Database Message Queue Broker
Slide 34: Interoperability Technologies Interoperability at the Resource Tier  Shared Database  Enabled by use of Open Access Database Drivers     Oracle OCI Driver for ADO.NET SQL Server 2000 Driver for JDBC 3rd Party managed drivers by Data Direct ADO.NET to OLEDB and ODBC Easiest way to achieve interoperability using resources Universally recognized way to store data Stored Procedures allow logic to be written once  Interoperability Benefits   
Slide 35: Interoperability Technologies Interoperability at the Resource Tier  Message Queue  MSMQ 3.0   HTTP SRMP endpoint COM endpoint – Java bridge .NET Adapter available via IBM CSD05    IBM WebSphere MQ (formerly MQ Series)  Fiorano, Silverstream, Sonic, Tibco Interoperability Benefits     Ideal for N-N Interoperability Scenarios Transaction Support Reliable Messaging Support Publish / Subscribe
Slide 36: Interoperability Technologies Interoperability at the Resource Tier  Broker   Microsoft BizTalk Server 2004 Interoperability Benefits      Ideal for N-N Interoperability Scenarios Transaction Support Rich Adapter Support (200+ adapters in BTS 2004)  Connection to legacy and disparate systems Excellent for Schema Interoperability between tiers Late binding allows for flexible interoperability Message Transformations  Orchestration 
Slide 37: Agenda  Interoperability fundamentals   What is interoperability? Why interoperate? Common scenarios for interoperability Sending data between tiers Standards that are helping promote interoperability Enabling point to point interoperability with J2EE Resource tier interoperability  Dealing with complex data types    Products and technology    Conclusion, more info, and questions and answers
Slide 38: Conclusion  What is Microsoft Doing?  Patterns and Practices Group   Enterprise Application Integration Guidance J2EE Interoperability Guidance Interoperability Workshops with other Vendors Content refresh around TechEd 2004 Continually learning from customer projects Architectural Interoperability Community Ensuring that partners (SIs / ISVs) are interoperable  Continuing Interoperability Tests    Customer Participation     Partner Participation  Interoperability is never ‘Microsoft-only’
Slide 39: Resources Available Today! Developer Focused: Fundamentals Point to Point Asynchronous Advanced Interoperability Amazon.com: http://www.amazon.com/exec/obidos/ASI N/0735619220/qid=1058741448
Slide 40: Resources Available Today! - Builds on concepts of the toolkit - Shows ‘XBikes’ reference application between .NET and IBM WebSphere URL: http://www.microsoft.com/practices
Slide 41: sguest@microsoft.com cliptaak@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.
Slide 42: Get what you need With an MSDN Universal Subscription Visit the MSDN Table Learn more & Enter a drawing!