The ebxml Technical Architecture

Transcription

1 The ebxml Technical Architecture Presented by: Duane Nickull CTO, XML Global Technologies May 2

2 Before we begin Caveats ebxml is a work in progress and the work you see today could be subject to change. Copyright, January 2, see final slide.

3 Presenter Duane Nickull Co-lead/Chief Editor - ebxml Technical Architecture, ebxml Steering Committee Founder and CTO of XML Global Technologies ( Co-engineered / invented GoXML First Context based XML Search Engine. First XML e-commerce Pro (launched Mar 999). Working with OAG, OASIS, UDDI, HRXML, WSDL Built a reference implementation of ebxml Technical Editor / Director of XSLT.com duane@xmlglobal.com Copyright, January 2, see final slide.

4 Initial Thoughts: Examine some business technical needs Look at the overall architecture of ebxml. Show working example of XML Global ebxml marketplace Discuss implementing ebxml today Followed by: ebxml Proof of Concept Demonstration Copyright, January 2, see final slide.

5 Business Technical Needs Link traditional data exchanges (EDI or new XML) to business applications. Create business processes based on smart documents. Provide means for trading partners to quickly and easily locate re-usable components. Provide means for trading partners to customize methods to their own internal systems. Low cost server and client based solutions. Copyright, January 2, see final slide.

6 The need for XML It is desirable to transport data around networks (including the internet). Ideally, that data should be self describing. SGML was too complex, HTML not robust enough. Copyright, January 2, see final slide.

7 What is Self Describing??? ST*323* V*7396*NEW ZEALAND QUEEN*D*4N*SCAC***L LS* R4*D*D*JAX*JACKSONVILLE FL**** V9*EAD**9289**JACKSONVILLE FL***A26 R4*D*D*ORF*NORFOLK, VA**NORFOLK INTL TERMIN** V9*EAD**9287**NORFOLK, VA***A26 R4*L*K*MEB*MELBOURNE, AUST**** V9*EDD**9272**MELBOURNE, AUST***A4 R4*L*K*SYD*SYDNEY, AUST**** V9*EDD**9275**SYDNEY, AUST***A4 R4*L*K*WLG*WELLINGTON, NEW ZEALAND**** V9*EDD**9272**WELLINGTON, NEW ZEA***A4 LE* SE*25* Copyright, January 2, see final slide.

8 XML is Self Describing <?xml version=.?> <Data> <Item ID= 2 > <Name>Rod</Name> <Price>2.</Price> <Units></Units> </Item> <Item ID= 4 > <Name>Reel</Name> <Price>5.</Price> <Units></Units> </Item> <Item ID= 2 > <Name>Bait</Name> <Price>24.</Price> <Units>3</Units> </Item> </Data> Copyright, January 2, see final slide.

9 XML issues XML is a markup language XML, by itself, does not solve interoperability problems yet it is an important tool for doing so. Using XML alone, does not provide semantics XML is a not programming language XML is not a fixed element language XML is not difficult to understand XML will not replace HTML XML does not solve business problems XML Schemas do not provide semantics or solve business problems. What we really need is a dynamic cross-walk mechanism for XML based vocabularies. Copyright, January 2, see final slide.

10 Thus the need for ebxml Through the Electronic Business XML (ebxml) Initiative OASIS and UN/CEFACT want to lower the barrier of entry to electronic business in order to facilitate trade, particularly with respect to small- and medium-sized enterprises (SMEs) and developing nations. Copyright, January 2, see final slide.

11 The ebxml Technical Architecture Copyright, January 2, see final slide.

12 Ebxml Architecture design B U S S I I N E S S S S T R A N S S A C T I I O N S S Viewed as Business Operational View Business aspects of business transactions Functional Service View Information Information technology technology aspects aspects of of business business transactions transactions Comply with Covered by Comply with Covered by Copyright, January 2, see final slide. BOV related standards* FSV related standards * UML Models

13 Business Operational View Based on ebxml Meta Model Business Context Core Library Business Library Core & Aggregate Components Business Processes Business Collaboration Knowledge Requirements Artifacts Use Case Diagrams Use Case Descriptions Analysis Artifacts Activity Diagrams Sequence Diagrams Conceptual Diagrams Design Artifacts Collaboration Diagrams State Diagrams Final Class Diagrams Business Process and Information Models (Compliant to the ebxml Meta Model) Copyright, January 2, see final slide.

14 Business Operational View (BOV) The BOV addresses the semantics of: ) The semantics of business data in transactions and associated data interchanges 2) The architecture for business transactions, including: i) operational conventions; ii) agreements; iii) mutual obligations and requirements. These specifically apply to the business needs of ebxml Trading Partners. Copyright, January 2, see final slide.

15 FSV Architecture Business Process and Information Models UML to XML conversion ebxml metamodel XML content Registration Registration Retrieval of Profiles & new or updated ebxml Models Registration TPP Registry Registry Service Interface Retrieval of ebxml Specifications & Models Retrieval of Profiles & new or updated ebxml Models Registration TPP Internal Business App Interface Business Service Interface Build Implementers TPA CPA Payload Build TPP Derives TPA Governs Shrink-wrapped Application Interface Business Service Interface Copyright, January 2, see final slide.

16 Functional Service View (FSV) The FSV addresses the supporting services meeting the mechanistic needs of ebxml. It focuses on the Information Technology aspects of: i) functional capabilities; ii) service interfaces; iii) protocols. Copyright, January 2, see final slide.

17 TA Philosophy Architect ebxml in Layers Start with the high level use cases The first layer has to recognize the Repository Items that constitute Core Components (ie address, tel). The second Layer has to recognize the Business Process (BPM) Third Layer is discovery of what partners require (CPP Collaborative Process Protocol) Use existing work the wheel is already round!!!! Write test code (informally) to test concepts!!! Copyright, January 2, see final slide.

18 ebxml High Level use case XML Business Scenarios Business Profiles Request Business Details COMPANY A 2 ebxml Registry 3 Register Implementation Details Register COMPANY A Profile Build Local System Implementation Download Scenarios and Profiles Query about COMPANY A profile 4 COMPANY B ebxml compliant system 5 Agree on Business Arrangement 6 DO BUSINESS TRANSACTIONS Copyright, January 2, see final slide.

19 Concepts The conceptual overview has therefore introduced the following concepts and architectural components:. A standard mechanism for describing a business process and its associated information model (BPSS) 2. A mechanism for registering and storing a business process and information model so that it can be shared/reused (Registry) 3. Discovery of information (from the CPP) about each participant including: What business processes they support. What service interfaces they offer in support of the business process. What business messages are to be exchanged between their respective service interfaces. Technical configuration of the supported transport, security and encoding protocols Copyright, January 2, see final slide.

20 Concepts (continued) 4. A mechanism for registering the aforementioned information so that it may be discovered and retrieved (Registry Client or Interface) 5. A mechanism for describing a Trading Partner Agreement (CPA) which can be derived from the information about each participant from their CPP. 6. A standardized messaging service which enables interoperable, secure and reliable exchange of messages between two parties (ebxml TRP) 7. Mechanism for configuration of the respective messaging services to engage in the agreed upon business process in accordance with the constraints defined in the CPA. Copyright, January 2, see final slide.

21 ebxml Architecture At the heart of ebxml is a powerful system of Registries and Distributed Repositories. The Registry is really the interface to the documents. Registries contain pointers and meta information about many different items - Core Components, DTD, Trading Partner Profiles and Business Process documents. It is important that we can reference items (CC) from Business Process Layer down to the most atomic Element Level. Repository Synchronization Registry API I / O Copyright, January 2, see final slide.

22 Repository Item Examples Registry systems can give you information about many types of ebxml documents - CPP and CPA templates - Business Process Documents - Core Components and CC Aggregates - DTD s and Schemas (Assembly documents) Copyright, January 2, see final slide.

23 Registry Item Examples XML elements in business messages can reference items callable from a Registry. Examples: <nameofperson> <nomdelapersonne> <name> <TheThingICallYou> All are the same item!!! Copyright, January 2, see final slide.

24 Registry Item Examples XML elements in business messages can reference items in a registry. Examples: <nameofperson UUID= myrep:236 > <nomdelapersonne UUID= myrep:236 > <name UUID= myrep:236 > <TheThingICallYou UUID= myrep:236 > All are the same item!!! Copyright, January 2, see final slide.

25 XML Elements in document instances contain pointers to RI s Registry Items are metadata not instances of data <?xml version=. > <name GUID= FooRep:2345 > Duane </name> <?xml version=. > <GUID>2345</GUID> <Element>name</Element> <EQ org= yourorg > PersonName </EQ> API Managed object Registry Managed object Managed object API Copyright, January 2, see final slide.

26 Registries deployment Both centralized and decentralized RegRep models shall be acceptable within the ebxml infrastructure. The ebxml registry architecture supports distribution. No single point of failure Copyright, January 2, see final slide.

27 Centralized System User User Registry (API) User Repository User User User Copyright, January 2, see final slide.

28 Decentralized Repository / Distributed Registry Repository Items Repository Items Registry (subscribes to decentralized Repository Items User User sync Repository Items User Registry (API) Searching and indexing only User Repository Items Repository Items User Repository Items User Copyright, January 2, see final slide.

29 ebxml CPP and CPA Tells you who, interfaces, tmodels etc. Provide a list of interfaces expressed as Business Processes (and binding s) Each Process has a Globally Unique Identifier (called UUID in UDDI, GUID in ebxml) Similar efforts IBM TPAML, UDDI, eco. CPP Preview Copyright, January 2, see final slide.

30 ebxml Business Process BP describe document choreography and overall process interfaces. Identify which business data needs to be present to ensure requirements of a party is being met. Examples can be Deliver a service or Purchase a product Identify DTD s by GUID BPM Preview Copyright, January 2, see final slide.

31 Core Components: A Core Component captures information about a real world (business) concept. A Core Component can be either an individual piece of business information (atomic data element), or a natural 'go-together' family of business information pieces (aggregate data element). It is Core because it occurs in many different areas of industry/business information exchange. CC Preview Copyright, January 2, see final slide.

32 ebxml CC and XML Vocabularies Vocabularies (eg. xcbl 2., Ariba cxml) contain elements that may be semantically identical to some of the common core components. Examples can be an <address> element on a xcbl invoice and the <partyaddress> on a Visa XML Invoice. Core Components MAY have contextual behaviour at run time i.e. PurchaseOrder.sendParty(name)!= PurchaseOrder.buyerParty(name) Copyright, January 2, see final slide.

33 ebxml Phases Phases of implementing and running ebxml.. Copyright, January 2, see final slide.

34 Implementation Phase ebxml Business Service Interface (application) Request / Send Receive ebxml Registry ebxml Specification Business Process and Information Models Lexicon (Core Component) Content Business Object Library RequestSpecification() ReceiveSpecification() RequestLexicon() ReceiveLexicon() RequestBusinessObjectLibrary() ReceiveBusinessObjectLibrary() RequestSomeOnesBusinessProcessInformationModel() ReceiveBusinessSomeOnesBusinessProcessInformationModel() SendOwnBusinessProcessInformationModel() ReceiveAcknowledgementForOwnBusinessProcessInformationModelAcceptance() SendOwnTradingPartnerProfile () ReceiveAcknowledgementForOwnTradingPartnerProfile () Copyright, January 2, see final slide.

35 Discovery Phase Request Receive Update ebxml Registry Lexicon (Core Component) Content Business Process and Information Models Business Object Library ebxml Business Service Interface (application) Query Retrieve (abstract) Send TPP Registry ebxml Service Interface (application) Security Constraints Messaging Constraints List of Scenarios RequestSomeOnesTradingPartnerProfile() ReceiveSomeOnesTradingPartnerProfile () RequestSomeOnesNew/UpdatedBusinessProcessInformationModel() ReceiveBusinessSomeOnesNew/UpdatedBusinessProcessInformationModel() SendTradingPartnerAgreement() ReceiveAcknowledgementForTradingPartnerAgreement() RequestLexiconUpdate() Some examples of possible access service methods ReceiveLexiconUpdate() RequestBusinessObjectLibraryUpdate() Copyright, January 2, see final slide. ReceiveBusinessObjectLibraryUpdate()

36 ebxml Run Time Phase ebxml Business Service Interface (application) Send Retrieve ebxml Business Service Interface (application) SendBusinessMessage() ReceiveBusinessMessageAcknowledgement() ReceiveBusinessMessage() SendBusinessMessageAcknowledgement() GenerateErrorMessage() ReceiveErrorMessage() Some examples of possible transport methods Copyright, January 2, see final slide.

37 Business Profile Document (XML) Business Process Document (XML) DTD s / Schemas Indexes XML instances based on rules and meta data in index.xml Trading Partner A Big Co. Trading Partner B Big Co. GUI Reg Business Profile Registry Business Process Registry DTD / Schema Registry Registry Abstract Layers. Core Component Library Core Component Library Registry Copyright, January 2, see final slide.

38 Special Considerations for SME s SME s will not likely have the expertise to start modeling business processes in UML. Address complexity issues part of the reason why EDI failed to scale/ SME s need a cost effective solution plug and play type components. ebxml is designed to allow lightweight packages and scaled integration. DEMO ALPHA (online) Copyright, January 2, see final slide.

39 How ebxml SME s interact SME s will likely use packages from ASP s which will present simple web forms for them to fill out. These will include many stock business processes, identifiable by a GUID (UUID). An SME may also identify and use BPM s (Business Processes) and DTD s / Schemas used by its partners. Trading Partner (ebxml Compliant) GUI Tool Trading Trading Partner Partner Profile Profile API Human Interface SECURITY LAYER Registry Repository system Copyright, January 2, see final slide.

40 ebxml Business information Collaborat ion Protocol Profile (CPP).. <<References>> DTD s Schemas?.. DTD s Schemas? Supported Business Process <<Constructed From>> DTD s Schemas? <<Constructed From>> Common Business Objects Decomposition to the most atomic level is the winning strategy for ebxml. It allows for automated semantic recognition of business information by using Registry services. <<Constructed From>> Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp Copyright, January 2, see final slide.

41 Business Message References Business Messages References to: Partner Discovery Layer Business Process Layer Business Info Layer Human Search Interface Registry Examples: eco.xml UDDI Examples: ebxml BP Syntax Examples: xcbl, cxml Visa Inv. Business Application Interface API Repository Items Human Actors Copyright, January 2, see final slide.

42 Building an ebxml Marketplace Caveat do not claim you have an ebxml compliant marketplace until the spec is done and conformancy tests are available. Start with slow transition. Adopting ebxml is not really complex but needs to be well though out. Some specific tools are needed. Copyright, January 2, see final slide.

43 ebxml Marketplace Architecture Registry/Repository is used as a central mechanism for Registration and subsequent discovery of XML meta data. XML Global uses XML Search Engine tightly coupled with Native XML Database. Facilitates ebxml TRP as messaging. Copyright, January 2, see final slide.

44 ebxml Marketplace Architecture Tools on front end allow companies to Register their CPP s. Copyright, January 2, see final slide.

45 Building an ebxml Markeplace Once a Skeleton CPP is built, the user may add one or more Business Processes Copyright, January 2, see final slide.

46 XML Global ebxml Marketplace Users CPP is now complete with BP s and other participants can query the Registry using published API. CPP Registry ebxml Users Copyright, January 2, see final slide.

47 XML Global ebxml Marketplace Another User can now retrieve and examine the CPP if they are wanting to do business with the first user. CPP Registry Copyright, January 2, see final slide.

48 Building an ebxml Marketplace As long as they know some basic information, they can compose a CPA and propose it to the first organization. Self(CPP) other(cpp) CPA Verify() TRP_Packaging Propose() Copyright, January 2, see final slide.

49 Building an ebxml Marketplace The recipient can then examine the CPA and check it. If it is acceptable, they may wish to sign it. A business Agreement is now in place. ReceiveProposedCPA() Validate() Recognize BP() Accept() Reject() CounterPropose() Copyright, January 2, see final slide.

50 ebxml Marketplace Once a CPA and BP have been recognized (by GUID or by query), business information can be transformed using a declarative transformation tool. Proprietary Data Format Data Exchange ebxml Backend System Compliant XML Syntax Copyright, January 2, see final slide.

51 Data Transformation is key DEMO.NET Transformation Copyright, January 2, see final slide.

52 Putting all the pieces together TP # TP #2 EbXML Application ebxml App. INTERCHANGE Business Interface Business modeling Human Interface API SECURITY LAYER Registry API XML Cache Local Cache QUERIES synchronizes Manual Search Repository Repository Repository Registry QUERIES Human Search Interface INDEX Repository Syntax Validation xcbl UDDI Copyright, January 2, see final slide. Interface Biztalk Schema s

53 Some Final Thoughts.. ebxml to build an open architecture, not a Standard Truly interoperable and Extensible (Global) Includes everyone from SME s to Fortune XML Global has begun implementing this year (2) Thank you! Duane Nickull Copyright, January 2, see final slide.

54 Copyright Notice / Credits You may use this presentation freely for your purposes! Copyright is owned by the Author however, you are hereby granted the right to reuse, distribute, translate and show this presentation, free of any royalty in the spirit of open sharing of information. There are no restrictions other than modification of this copyright notice or credits which must remain intact. Contact Duane Nickull, duane@xmlglobal.com Copyright, January 2, see final slide.