MDA for Web Services Applying Model Driven Architecture

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

Problem Space z. Integration Nightmare z. Infrastructure, Version & Vendor lock-in z. Complex, divergent and manual development and deployment processes Copyright © 2000 -2002, Data Access Technologies, Inc.

Goals z A scalable and robust enterprise architecture z Loosely coupled enterprise components z Enable rapid provisioning of business solutions y Simple, reproducible processes supporting reuse z Technology & vendor independence z Enable the integration and collaboration of multiple; y Business units (internal and external) y Customers y Suppliers y Systems y Technologies Copyright © 2000 -2002, Data Access Technologies, Inc.

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

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

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

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

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

Using MDA for WSDL Business Focused ECA Model “PIM” Mapping WSDL & Soap Copyright

Collaboration is Key z Collaboration is a key differentiation and key cost center (Healthcare Example) y Customer Collaboration y Claim processing y Disputes y Physician Collaboration y Payer Collaboration y Hospital Collaboration y Broker Collaboration y Government Collaboration y Employee Collaboration y Others. . . Copyright © 2000 -2002, Data Access Technologies, Inc. The system integrates multiple collaborations

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

Loose Coupling z Loose coupling is the ability for independent parts of systems to be built and evolve independently z Tightly coupled systems y. Prevent change (the next legacy system) y. Cause lock-in y. Become unmanageable y. Prevent reuse z Quality architecture is essential for loose coupling Copyright © 2000 -2002, Data Access Technologies, Inc.

z Enterprise Components must be independent z While being able to interoperate with each other Op Sta en nda rds z Making the information system a lattice of cooperating components Copyright © 2000 -2002, Data Access Technologies, Inc. n s pe ard O d n ta S Enterprise Components Open Standards

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

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

Technology Independence What the infrastructure Business vendors would Business Logic eb. Xml Business. NET have. Logicdo you Roseta. Net Logic Ejb Component Logic Component Adapters eb. Xml Biz. Talk Rosetanet EJB Copyright © 2000 -2002, Data Access Technologies, Inc. Adapters EJB Business Logic Component MQ Corba CICS

Typical Requirement Buyer Web Page HTML Seller Redundant Work! B 2 B Buyer Copyright

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

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

Understanding Collaborations

The Connected Enterprise Content and Communication Digital Map Census Data Police Records Police Dispatcher

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

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

The Internet Computing Model The technology model behind WSDL and eb. XML and others

The Internet Computing Model Portals Business Party z Collaboration of independent entities z Document exchange over internet technologies y Large grain interactions z No shared infrastructure required * z Long lived business processes z Business transactions Copyright © 2000 -2002, Data Access Technologies, Inc.

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

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

Drilling down – inside a role z The open domain should make no assumptions about the “inside” of a role. z Inside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used z Until you get to system inside a managed domain y Shared resources (DBMS) y Common Management y Frequently a legacy system Copyright © 2000 -2002, Data Access Technologies, Inc. Inner Role Legacy Inner Role Domain Cust Inner Role

Collaborative Business Semantics z Defined: The processes, information and contracts of interaction between collaborators within a community z Collaborative business semantics are a valuable longterm asset z Captures information and process z Requires ownership and support z Do not put this valuable asset in a (transient - one size fits all) technology specific form y Use technology independent models (MDA) y Map to the technology of the day (E. G. DTD) Copyright © 2000 -2002, Data Access Technologies, Inc.

Generic web services z. Generic web services is any set of technologies that can

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

XML Standards z XML Schema & DTD y. Description and packaging of data z WSDL y. Specification a services, operations and flows available via that service z Soap y. Basic messaging and packaging y. Extensions for Soap-RPC with WSDL y. May be extended to support collaborative messaging Copyright © 2000 -2002, Data Access Technologies, Inc.

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

EDOC Component Collaboration Architecture The model of collaborative work

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

The Seller’s Detail Order Conformation Order Processing Shipped Shipping Ship Req Shipped Delivered Copyright

The Community Process z Identify a “community process”, the roles and interactions in a

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

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

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

WSDL/ECA Differences z. WSDL Adds y. Technology binding and endpoints z. ECA adds y. Choreography, nested conversations, twoway protocols, nested components. Copyright © 2000 -2002, Data Access Technologies, Inc.

Next steps z. RFP Draft – “Web services for enterprise collaboration” y. Two way mapping between EDOC-ECA and WSDL/Soap y. Draft available – discussion in “MARS” z. Roadmap items to make web services more viable as enterprise infrastructure y. Security and reliability 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 Copyright © 2000 -2002, Data Access Technologies, Inc.