1. MDA for Web Services Applying Model Driven Architecture to Web Services Document webserv/2002-04-05

2. Copyright © 2000-2002, Data Access Technologies, Inc. Problem Space zIntegration Nightmare zInfrastructure, Version & Vendor lock-in zComplex, divergent and manual development and deployment processes

3. Copyright © 2000-2002, Data Access Technologies, Inc. Goals zA scalable and robust enterprise architecture zLoosely coupled enterprise components zEnable rapid provisioning of business solutions ySimple, reproducible processes supporting reuse zTechnology & vendor independence zEnable the integration and collaboration of multiple; yBusiness units (internal and external) yCustomers ySuppliers ySystems yTechnologies

4. Copyright © 2000-2002, Data Access Technologies, Inc. Model Driven Development Solution Triad Service Based Architecture Standards Tooling & Infrastructure Development Process Components Web Services Corba OMG ECA J2EE.NET

5. Copyright © 2000-2002, Data Access Technologies, Inc. The new center zThe strategic core of you systems must be the business itself zOnly technology independent business focused models will survive the transience of technology and lock-in zThese models can become part of your source code, driving enterprise applications zEnabler: Model Driven Architecture (MDA) with EDOC-ECA Extreme Modeling

6. Collaboration and Web Services Collaboration is the center of applying web services to core enterprise problems.

7. EDOC – Enterprise Collaboration Architecture Provides the standard UML “PIM” profile suitable for enterprise application of web services

8. Copyright © 2000-2002, Data Access Technologies, Inc. What is the Enterprise Collaboration Architecture? zECA is a “profile of UML”, a way to use UML for a specific purpose - it is an OMG standard yThat purpose is modeling enterprise systems. zYou can also think of this as a “modeling framework” for enterprise computing zECA is part of the “Model Driven Architecture” (MDA) initiative of the OMG yUsing precise modeling techniques as part of the development lifecycle to speed development and provide technology independence zECA has been adopted by the OMG as part of the EDOC RFP.

9. Copyright © 2000-2002, Data Access Technologies, Inc. WSDL&Soap Using MDA for WSDL Mapping “PIM” “PSM” Business Focused ECA Model

10. Copyright © 2000-2002, Data Access Technologies, Inc. Collaboration is Key zCollaboration is a key differentiation and key cost center (Healthcare Example) yCustomer Collaboration yClaim processing yDisputes yPhysician Collaboration yPayer Collaboration yHospital Collaboration yBroker Collaboration yGovernment Collaboration yEmployee Collaboration yOthers... The system integrates multiple collaborations

11. Copyright © 2000-2002, Data Access Technologies, Inc. Automated Model Driven Architecture Profile (E.G. EDOC) Framework & Infrastructure (E.G. Web Services) InfrastructureMapping (E.G. Web Services) Mapping is tuned to the infrastructure Tools Produce & Integrate EnterpriseComponents Business Focused Model (UML) Minimize and structure manual implementation

12. Copyright © 2000-2002, Data Access Technologies, Inc. Loose Coupling zLoose coupling is the ability for independent parts of systems to be built and evolve independently zTightly coupled systems yPrevent change (the next legacy system) yCause lock-in yBecome unmanageable yPrevent reuse zQuality architecture is essential for loose coupling

13. Copyright © 2000-2002, Data Access Technologies, Inc. Enterprise Components zEnterprise Components must be independent zWhile being able to interoperate with each other zMaking the information system a lattice of cooperating components Open Standards Open Standards Open Standards

14. Copyright © 2000-2002, Data Access Technologies, Inc. Poor Monolithic Architecture Traditional data sources SQL DBMS & Client/Server Bad Thing All business rules, data rules, application logic, technology and user interface code are contained here The data goes here Monolithic Applications Monolithic Applications HTTP Web Browser Making a monolithic web application doesn’t help!

15. Copyright © 2000-2002, Data Access Technologies, Inc. HTTP Web Server Applications Enterprise Architecture SQL DBMS, Client/Server & Legacy Applications Client Applications Business and data rules go here User interface and application logic go here The data goes here EAI Applications & B2B E-Commerce Web Browser Standard Middleware connects applications to components & components to components XML Corba EJB DCOM MQ Supply Chain Enterprise Components

16. Copyright © 2000-2002, Data Access Technologies, Inc. What the infrastructure vendors would have you do Technology Independence Business Logic Component ebXml Business Logic Component.NET Business Logic Component RosetaNet Business Logic Component Ejb Adapters EJB Business Logic Component ebXml BizTalk Rosetanet Adapters CICS EJB MQ Corba

17. Copyright © 2000-2002, Data Access Technologies, Inc. Typical Requirement B2B Buyer Web Service Seller Buyer Web Page HTML Seller Redundant Work!

18. Copyright © 2000-2002, Data Access Technologies, Inc. B2B Buyer Multi-tier implementation Buyer Web Page HTML Buyer Proxy Web Service Seller Could have multiple implementations using different technologies Could have multiple implementations using different technologies

19. Copyright © 2000-2002, Data Access Technologies, Inc. Legacy Seller Applications Event Cloud B2B Buyer Multi-tier implementation Buyer Web Page HTML Buyer Proxy Web Service Seller Event Implementing seller using events

20. Understanding Collaborations

21. Copyright © 2000-2002, Data Access Technologies, Inc. The Connected Enterprise Content and Communication Aerial Photos Digital Map Census Data House Drawings Police Records Police Dispatcher Role

22. Copyright © 2000-2002, Data Access Technologies, Inc. Multiple roles in a collaboration

23. Copyright © 2000-2002, Data Access Technologies, Inc. Implementation Net Hardware Operating System Framework, Middleware & Container Roles to Systems Interaction Path Component in Role Interaction (With Information) Role Collaboration

24. The Internet Computing Model The technology model behind WSDL and ebXML and others

25. Copyright © 2000-2002, Data Access Technologies, Inc. The Internet Computing Model zCollaboration of independent entities zDocument exchange over internet technologies yLarge grain interactions zNo shared infrastructure required * zLong lived business processes zBusiness transactions Business Party Business Party Portals

26. Copyright © 2000-2002, Data Access Technologies, Inc. Requirements for the “ICM” zContract of Collaboration yShared business semantics yMeta-Model (EDOC-ECA) and representation (I.E. XMI, ebXML-BPSS) yShared Repository for Contracts (MOF, UDDI, ebXML) zConnectivity (middleware) which meets requirements of the contract zImplementation of each contract role providing connectivity (application server) Business Partner Business Partner Repository Contracts (Metadata) Contract of collaboration can be mapped to the format of various technologies. (ebXML, Soap,.NET) Instance Data

27. Copyright © 2000-2002, Data Access Technologies, Inc. Two levels of interoperability Instance data and interoperability Metadata (contract) interoperability Business Partner Business Partner Bridge Each can be transformed Purchasing Model.NET ebXML BPSS ebXML Biztalk Normal Form Over Soap

28. Copyright © 2000-2002, Data Access Technologies, Inc. Drilling down – inside a role zThe open domain should make no assumptions about the “inside” of a role. zInside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used zUntil you get to system inside a managed domain yShared resources (DBMS) yCommon Management yFrequently a legacy system Inner Role Legacy Inner Role Inner Role Domain Cust

29. Copyright © 2000-2002, Data Access Technologies, Inc. Collaborative Business Semantics zDefined: The processes, information and contracts of interaction between collaborators within a community zCollaborative business semantics are a valuable long- term asset zCaptures information and process zRequires ownership and support zDo not put this valuable asset in a (transient - one size fits all) technology specific form yUse technology independent models (MDA) yMap to the technology of the day (E.G. DTD)

30. Copyright © 2000-2002, Data Access Technologies, Inc. Generic web services zGeneric web services is any set of technologies that can implement the internet computing model. zWSDL, ebXML,.NET…

31. Standards for Global Internet Computing EDOCEDOC SOAP WSDL XML XML-Schema.NET BPML XLANG

32. Copyright © 2000-2002, Data Access Technologies, Inc. XML Standards zXML Schema & DTD yDescription and packaging of data zWSDL ySpecification a services, operations and flows available via that service zSoap yBasic messaging and packaging yExtensions for Soap-RPC with WSDL yMay be extended to support collaborative messaging

33. Copyright © 2000-2002, Data Access Technologies, Inc. ECA as the normal form EDOC-ECA Web Services (WSDL) ebXML (BPSS) J2EE (Java RMI).NET MOM (MQ-Series) The standard way to model and tool for multiple technologies MDA Mappings English

34. EDOC Component Collaboration Architecture The model of collaborative work

35. Copyright © 2000-2002, Data Access Technologies, Inc. The Marketplace Example Mechanics Are Us Buyer Acme Industries Seller GetItThere Freight Shipper Order Conformation Ship Req Shipped Physical Delivery Delivered Status Process Complete

36. Copyright © 2000-2002, Data Access Technologies, Inc. The Seller’s Detail Order Conformation Shipped Ship Req Shipped Delivered Order ProcessingShipping Receivables Event

37. Copyright © 2000-2002, Data Access Technologies, Inc. The Community Process zIdentify a “community process”, the roles and interactions in a collaboration Protocol

38. Copyright © 2000-2002, Data Access Technologies, Inc. Protocols

39. Copyright © 2000-2002, Data Access Technologies, Inc. Composition

40. Copyright © 2000-2002, Data Access Technologies, Inc. ECA/WSDL mapping zECA works well as a modeling framework for WSDL zHow major concepts could map yWSDL Port ECA Port yWSDL Operation ECA Flow port (one way) or Operation (Two way) yWSDL Service ECA Component yWSDL Port type ECA Protocol yWSDL Message ECA Document type

41. Copyright © 2000-2002, Data Access Technologies, Inc. WSDL/ECA Differences zWSDL Adds yTechnology binding and endpoints zECA adds yChoreography, nested conversations, two- way protocols, nested components.

42. Copyright © 2000-2002, Data Access Technologies, Inc. Next steps zRFP Draft – “Web services for enterprise collaboration” yTwo way mapping between EDOC-ECA and WSDL/Soap yDraft available – discussion in “MARS” zRoadmap items to make web services more viable as enterprise infrastructure ySecurity and reliability

43. Copyright © 2000-2002, Data Access Technologies, Inc. Business Case  ·High level support for understanding and documenting collaborative business processes.  ·Loose coupling between independent parties in a collaboration  ·Tighter coupling in the software development life-cycle between design and implementation processes and artifacts.  ·Consistency in the way WSDL is used to implement collaboration.  ·A standard way to use UML for web services.  ·Enhanced support for asynchronous interactions.  ·Automation of the development process from design to implementation.  ·A faster, more deterministic development processes.  ·Ability to adapt to changing business requirements.  ·Ability to adapt to multiple and changing infrastructure technologies.  ·Full life-cycle tool support