ebXML Overview Cory Casanave Data Access Technologies (305)

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

Copyright © , Data Access Technologies, Inc. Requirements for the “ICM” zContract of Collaboration yShared business semantics yMeta-Model (EDOC- ECA/BPSS) 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

Copyright © , Data Access Technologies, Inc. Two levels of interoperability Instance data interoperability Metadata (contract) interoperability Business Partner Business Partner BPSS ebXML Over Soap Collaboration Partner Profile Collaboration Partner Profile Collaboration Protocol Agreement Repository

Copyright © , Data Access Technologies, Inc. Parts of ebXML Specification zRequirements (RE) zTechnical Architecture (TA) zBusiness Process Specification Schema (BPSS) zCollaboration protocol profile & agreement (CCP) zMessage Service (MS) zRegistry Information Model (RI) zGlossasry (Gloss)

Copyright © , Data Access Technologies, Inc. ebXML Architecture BP Specification Business Process Core Data Blocks Business Transactions Context ForBuilt With Implement one Partner Role Implement other Partner Roles Register Design time CPP Transport Package Business Service Interface Internal Business App Business Service Interface Runtime CPA

Copyright © , Data Access Technologies, Inc. Summary of ebXML terms zBPSS yBusiness Process Schema Specification – Meta model in XML (A Choreographed set of business transactions between partners) yUMM xUN/CEFACT Methodology & UML profile for EDI specification zCore Components yCommon data structures for message interchange in a context zCPP yCollaboration Partner Profile – Lists partner processes & technologies zCPA yCollaboration Protocol Agreement – Runtime partner binding zReg-Rep yRegistry & Repository – Storage for metadata and partners zTRP yTransport Routing & Packaging – Wire protocol

Copyright © , Data Access Technologies, Inc. Political Split zOasis yCPP yCPA yReg-Rep yTRP zUN/CEFACT yBPSS yCore Components yUMM

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

Copyright © , Data Access Technologies, Inc. XML Standards zXML Schema & DTD yDescription and packaging of data zSoap yBasic messaging and packaging yExtensions for Soap-RPC with WSDL yMay be extended to support collaborative messaging

Copyright © , Data Access Technologies, Inc. ebXML Added Value zSpecification of business process and data for collaboration zLink between BPSS, Repository and Transport zChoreography of async services zTiming and security parameters zPackaging of complex MIME packages zLong lived process identity zWhen web services need to be more than a simple request/reply

Copyright © , Data Access Technologies, Inc. ebXML & EDOC Transport Distribution Repository Runtime Enterprise Integration Components Information Model MDA Collaboration Process Model ebXML EDOC

Copyright © , Data Access Technologies, Inc. Standards for collaboration EDOC-ECAebXML-BPSS Business CollaborationsYes – Community ProcessYes – Multi Party Collaboration Contract of InteractionYes – Protocol with Choreography & Object Interface Yes – Binary Collaboration with Choreography and Business Transactions Content ModelYes – Document ModelUses external forms, such as XML Schema Recursive CompositionYes – Recursive Composition into Enterprise No – Only “B2B” Detail sufficient to drive communications No – Requires technology mappingYes – As ebXML transport. BPSS includes timing and security parameters. Computing Models Supported Internet document exchange, entities, business processes, objects and events Internet document exchange

The model driven architecture for web services and collaborative internet computing

Copyright © , Data Access Technologies, Inc. EDOC Solution Triad Service Based Architecture Standards Tooling & Infrastructure Development Process Components Model Driven Architecture

Copyright © , 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

Copyright © , Data Access Technologies, Inc. EDOC as the normal form EDOC-UML Web Services (WSDL) ebXML (BPSS) J2EE (Java RMI) Corba (IDL/CDL) MOM (FCM) The standard way to model and tool for multiple technologies MDA Mappings

Copyright © , Data Access Technologies, Inc. EDOC and WSDL zBoth define document interactions across ports zAn async EDOC protocol requires a pair of WSDL ports zWSDL adds connection and endpoint detail zEDOC choreography specifies how multiple WSDL interactions will work together zEDOC provides a way to model the component behind a set of services zEDOC shows how service components can be composed of other service components zEDOC integrates with the information model, events and workflow zWSDL is appropriate as an EDOC technology mapping

Copyright © , Data Access Technologies, Inc. EDOC and J2EE – JSR 159 zTitle: Java Process Component API (JPC). yThe goal of [JSR 159] is to provide J2EE developers with the ability to compose an application out of service level components (where service in this context means a loosely coupled, event based process). Today, J2EE developers build applications that implement a service; however, there is no formal way to describe the full semantics of a service to the J2EE container. There is no formal concept of a service as a J2EE component nor is there a formal concept of service composition. yFor some time, the computing industry has struggled to find a component abstraction that balanced the need for type safety with the need for loosely coupled, event based composition. The most recent and most promising solution to this problem is the EDOC Component Collaboration Architecture. In addition to standing alone as a service component architecture, CCA is closely related to the WSDL model for web services. Both are loosely coupled, port based models of service integration; however, the CCA goes much further to explicitly define a rich collaboration model. Their similarities make it practical to view WSDL as a web service adjunct to CCA rather than a different, competing technology.

From the enterprise to technology viewpoints EDOC collaborations as the basis of multiple viewpoints

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

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

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

Vision Building and adapting systems for collaboration, reuse and change

Copyright © , Data Access Technologies, Inc. Loosely coupled enterprise architecture Open Standards Open Standards Open Standards zIndependent enterprise components zRepresenting business concepts zLink via open standards

Copyright © , Data Access Technologies, Inc. OMG Model Driven Architecture (MDA) zHigh level – platform independent models zTechnology Models zMapping yCustom yStandard zStandard Models produce technology specific standards artifacts

Copyright © , Data Access Technologies, Inc. What some 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

Copyright © , Data Access Technologies, Inc. Automated MDA Profile (E.G. EDOC) Framework & Infrastructure (E.G. XML) InfrastructureMapping Mapping is tuned to the infrastructure Tools Produce & Integrate EnterpriseComponents UMLDesign

Copyright © , Data Access Technologies, Inc. High level tooling & infrastructure zMUST BE SIMPLE! yWe must be able to create better applications faster yWe must separate the technology and business concerns, enable the user zTooling + Infrastructure yExecutable models are source code yTooling must be technology aware yInfrastructure must support tooling, not manual techniques zModel based component architectures

Copyright © , Data Access Technologies, Inc. High level tooling & infrastructure zMUST BE SIMPLE! yWe must be able to create better applications faster yWe must separate the technology and business concerns, enable the user zTooling + Infrastructure yExecutable models are source code yaTooling must be technology aware yInfrastructure must support tooling zModel based component architectures Executable Models

Copyright © , Data Access Technologies, Inc. Iterative Development Build Release Build Deploy Business Model Design Infrastructure Development Automation

Copyright © , Data Access Technologies, Inc. Business Component Marketplace zThe business component marketplace is projected to be a 10b market in 5 years zConsider the value of XML components that wrap popular legacy zNew application functionality built from components zComponents for integration and transformation zXML and web services makes an excellent basis for such components zTechnology components, such as for repositories and DBMS zMarketplace my be inside the enterprise or commercial

Copyright © , Data Access Technologies, Inc. Net effect zUsing these open standards and automated techniques we can; yAchieve the strategic advantage of an open and flexible enterprise yProduce and/or integrate these systems FASTER and CHEAPER than could be done with legacy techniques yProvide a lasting asset that will outlive the technology of the day

Copyright © , Data Access Technologies, Inc. Role of the OMG zWhile web services have huge potential but the enterprise needs to see how to bring these technologies together to solve business problems zThe OMG can bring business focus and unification to web services by applying Model Driven Architecture (MDA); yBridging technologies yUnifying tools yAutomating the development process zWe have just adopted EDOC for this vary purpose

Copyright © , Data Access Technologies, Inc. Discussion

Copyright © , Data Access Technologies, Inc. Contact Cory Casanave Data Access Technologies (305)