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

Web services for Enterprise Collaboration

Applying MDA to web services for enterprise collaboration

Doc Mars/2002-04-10

Doc webserv/2002-04-06

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

Quick Overview

WSDL provides the mechanism for specifying web services and endpoints

The Enterprise Collaboration Architecture adopted in EDOC provides a modeling framework for collaboration

Providing an ECA<>WSDL mapping in the RFP enhances both technologies using MDA


WSDLWSDL&&

SoapSoap

Using MDA for WS

Mapping

“PIM”

“PSM”

Business FocusedBusiness FocusedECA ModelECA Model


Collaboration is Key

Collaboration & integration is a key differentiation and key cost center for the enterprise (Healthcare Example) Customer Collaboration Claim processing Disputes Physician Collaboration Payer Collaboration Hospital Collaboration Broker Collaboration Government Collaboration Employee Collaboration Others...

The system integrates multiple

collaborations

EDOC – Enterprise Collaboration Architecture

Provides a standard UML “PIM” profile suitable for enterprise application of web services


ECA Community Process

The “community process”, the roles and interactions in a collaboration

Buyer Seller

BuySell CommunityProcess

Buy Sell

Shipper

ShipDelivery

ShipDelivery

Protocol

WSDL


Protocol OrderBT

OrderDenied

OrderConfirmationOrder

responderRoleSeller

initiatorRoleBuyer

ECA Protocols

<<initiates>> Order

<<responds>> OrderDenied <<responds>> OrderConfirmation

Failure Success

WSDLPort Type


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

MDAMappings

The RFP

Web Services for Enterprise Collaboration


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.


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.

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.


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.


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.


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.


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


Points

Scope This is a small and very focused RFP It maps between two existing specifications Easy - there are no known “large issues” Proprietary implementations already exist

High value Provides real user advantage

How the enterprise can utilize web services How UML based tools can facilitate web services

Realizes MDA for a hot technology Establishes OMG in the “Enterprise” web services space


What next

Assess acceptance of issuing such an RFP

Identify key players to refine and sponsor the RFP

Issue in Orlando?


Issues

Schema type system extension limitts

Abstract vs bound bindingMore specific schema [email protected] comments for added

semantics be normative?

mailto:[email protected]

Does ECA map well to WSDL?

An approach to the mapping


ECA/WSDL mapping

ECA works well as a modeling framework for WSDL

How major concepts could map WSDL Port <-> ECA Port WSDL Operation <-> ECA Flow port (one way)

or Operation (Two way) WSDL Service <-> ECA Component WSDL Port type <-> ECA Protocol WSDL Message <-> ECA Document type


WSDL/ECA Differences

WSDL Adds Technology binding and endpoints

ECA adds Choreography, nested conversations,

two-way protocols, nested components.

Documents

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