1. Web services for Enterprise Collaboration Applying MDA to web services for enterprise collaboration Doc Mars/2002-04-10 Doc webserv/2002-04-06

2. Copyright © 2000-2002, Data Access Technologies, Inc. Quick Overview zWSDL provides the mechanism for specifying web services and endpoints zThe Enterprise Collaboration Architecture adopted in EDOC provides a modeling framework for collaboration zProviding an ECA<>WSDL mapping in the RFP enhances both technologies using MDA

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

4. Copyright © 2000-2002, Data Access Technologies, Inc. Collaboration is Key zCollaboration & integration is a key differentiation and key cost center for the enterprise (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

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

6. Copyright © 2000-2002, Data Access Technologies, Inc. ECA Community Process zThe “community process”, the roles and interactions in a collaboration Protocol WSDL

7. Copyright © 2000-2002, Data Access Technologies, Inc. ECA Protocols WSDL Port Type

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

9. The RFP Web Services for Enterprise Collaboration

10. Copyright © 2000-2002, Data Access Technologies, Inc. Solicits proposals for  A Mapping from EDOC-Enterprise Collaboration Architecture to WSDL 1.1 with attachments and a SOAP binding.  A Mapping from WSDL 1.1 with a Soap binding to the EDOC-Enterprise Collaboration Architecture.  Any required extensions to the EDOC-Enterprise Collaboration Architecture to represent WSDL semantics.

11. Copyright © 2000-2002, Data Access Technologies, Inc. Requirements  Submissions shall specify complete mapping rules enabling translation of the applicable features of an ECA specification to a valid set of WSDL service definitions. z Submissions shall specify which version(s) WSDL, Schema and EDOC they support.  Submissions shall specify complete and isomorphic mapping rules enabling translation of all of the features of a valid WSDL specification to an ECA specification.  Submissions shall specify all extensions to ECA required to fully represent WSDL semantics.

12. Copyright © 2000-2002, Data Access Technologies, Inc. Optional Requirements  As this is the first ECA mapping RFP, Submissions may require and provide enhanced mechanisms or methodologies for augmenting ECA specifications with mapping parameters and technology specific semantics.

13. Copyright © 2000-2002, Data Access Technologies, Inc. Issues to be discussed  Proposals shall include information relative to future support for evolving WSDL “flow” languages.  Proposals may discuss how their solution may augment or be integrated with other standards activities such as ebXML or JCP-159.

14. Copyright © 2000-2002, Data Access Technologies, Inc. Evaluation Criteria  Independence  Ability for a WSDL domain to inter-work without each having prior knowledge of the other's implementation.  Completeness  Preservation of content and semantics between transformations.  Ease of use  The solution should, to the greatest extent possible, be easy to use and understand.

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

16. Copyright © 2000-2002, Data Access Technologies, Inc. Points zScope yThis is a small and very focused RFP yIt maps between two existing specifications yEasy - there are no known “large issues” yProprietary implementations already exist zHigh value yProvides real user advantage xHow the enterprise can utilize web services xHow UML based tools can facilitate web services yRealizes MDA for a hot technology yEstablishes OMG in the “Enterprise” web services space

17. Copyright © 2000-2002, Data Access Technologies, Inc. What next zAssess acceptance of issuing such an RFP zIdentify key players to refine and sponsor the RFP zIssue in Orlando?

18. Copyright © 2000-2002, Data Access Technologies, Inc. Issues zSchema type system extension limitts zAbstract vs bound binding zMore specific schema reference zCory-c@enterprise-component.comCory-c@enterprise-component.com zShould comments for added semantics be normative?

19. Does ECA map well to WSDL? An approach to the mapping

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

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