1. ebXML Technical Overview How all the pieces fit together Duane Nickull CTO – XML Global Technologies Chair – UN/CEFACT eBusiness Architecture duane@xmlglobal.com

2. 2 Agenda:  Examine some business and technical needs for ebXML.  Look at the overall architecture of ebXML. Followed by:  ( Technical Track | Business Track )

3. ebXML Introduction Understanding Mission and Architecture

4. 4 Business Needs  Link traditional data exchanges (EDI or new XML) to business applications.  Lower costs to configure new e-Business relationships.  Create “Smart” Business Processes.  Provide a reusable set of core information components.  Low cost server and client based solutions.  Protect investments in existing systems.

5. 5 The need for XML  It is desirable to transport data around networks (including the internet).  XML is the format of choice for marking up that data.  SGML was too complex, HTML not robust enough.

6. 6 What is Self Describing??? ST*323*712990413 V1*7039610*NEW ZEALAND QUEEN*D*104N*SCAC***L LS*0100 R4*D*D*JAX*JACKSONVILLE FL**** V9*EAD**920819**JACKSONVILLE FL***A26 R4*D*D*ORF*NORFOLK, VA**NORFOLK INTL TERMIN** V9*EAD**920817**NORFOLK, VA***A26 R4*L*K*MEB*MELBOURNE, AUST**** V9*EDD**920712**MELBOURNE, AUST***A40 R4*L*K*SYD*SYDNEY, AUST**** V9*EDD**920715**SYDNEY, AUST***A40 R4*L*K*WLG*WELLINGTON, NEW ZEALAND**** V9*EDD**920721**WELLINGTON, NEW ZEA***A40 LE*0100 SE*25*712990413

7. 7 XML is Self Describing Rod 12.00 1 Reel 15.00 1 Bait 24.00 3

8. 8 XML is not enough.  XML is for marking up data.  XML, by itself, does not solve interoperability problems yet it is an important tool for doing so.  XML does not provide semantics.  XML does not solve business problems.  XML Schemas do not provide semantics or solve business problems.

9. 9 Thoughts  XML by itself is not the magic bullet.  What we really need is a dynamic cross-walk mechanism for XML based vocabularies.

10. 10 Mission: ebXML enables anyone, anywhere to do business with anyone else over the Internet Thus the need for ebXML

11. 11 ebXML Technical Architecture

12. 12 1. Business Processes and associated Core Components (in XML) 2. A mechanism for registering and storing them (Registry) 3.A mechanism for declaring a Trading Partners capabilities and they can do/support (CPP) Architecture Concepts…

13. 13 5. A mechanism for describing a Trading Partners capabilities (CPP). 4. A mechanism for describing a Trading Partner Agreement (CPA). 6. A standardized messaging service (ebXML MS) 7. A standardized methodology/process for modeling the real world business and translating it into XML. Architecture Concepts…

14. 14 BUSINESSTRANSACTIONSBUSINESSTRANSACTIONS BUSINESSTRANSACTIONSBUSINESSTRANSACTIONS Viewed as Information technology aspects of business transactions Information technology aspects of business transactions Business Operational View Functional Service View Business aspects of business transactions Comply with Covered by BOV related standards* Comply with Covered by FSV related standards * UML Models

15. 15 Modeling ….

16. 16 BDV And more modelling…. BRVBTVBSV Business Experts Analysts Designers Facilitors & Modelers

17. 17 And yet more modelling…. Business Process And Information Models

18. 18 FSV Architecture Interface CPA CPP

19. 19  At the heart of ebXML is a powerful system of Registries and Distributed Repositories.  The Registry provides the interfaces.  Registries contain pointers and meta information in the Registry Information Model (RIM).  ebXML v 1.0 Registries have two main interfaces – ObjectManager() and ObjectQueryManager().  The methods exposed by the interfaces have set metadata for expressing queries and returns. Repository Registry Synchronization API I / O RIM

20. 20 ebXML Registry Architecture Transport Layer Registry SideClient Side ebXML MSH RSS Messaging Transport Layer RSS Messaging ObjectManager()ObjectQuery Manager() RIM Managed Objects API Applications GUI’s Passed by URI Reference Referenced By URI

21. 21 Registry Item Examples  Registry systems can give you information about many types of ebXML and even non-ebXML documents. - CPP and CPA templates - Business Process Documents - Core Components and CC Aggregates -DTD’s and Schemas (Assembly documents) -Programming artifacts

22. 22 XML Elements  XML elements can reference items from a Registry.  Examples:  All are the same item!!!

23. 23 Registry Item Examples  XML elements in business messages can reference items in a registry.  Examples:  All are the same item!!!

24. 24  XML Elements in document instances contain pointers to Repository Item’s.  Most Registry Items are metadata – not instances of data. Registry API Duane API 12345 姓 LastName Managed object Managed object Managed object

25. 25 ebXML Messaging Service

26. 26 ebXML – CPP and CPA  Trading Partner Profiles and Agreements.  Tells you Business Service Interfaces, bindings etc.  Provide a list of Business Processes or Web Services.  NOT designed to be a legal agreement. example

27. 27 ebXML Business Process Specification Schema BPSS are Runtime and Design Time artifacts.  Captures particulars of BP in an XML schema controlled instance.  References Business Information used in each step of process.  Should Identify Assembly Docs at Design time. example

28. 28 Core Components:  A Core Component captures information about a real world (business) concept.  A Core Component can be atomic or aggregate.  It is ‘ Core ’ because it occurs in many different areas of industry/business information exchange.

29. 29 Core Component Realization

30. 30 ebXML Business information Collaborat ion Protocol Profile (CPP) 1.. Supported Business Process > DTD’s Schemas? DTD’s Schemas? DTD’s Schemas? > 1.. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp Business Information Entities > XML Representations Bridge to Legacy Data

31. 31 Methodologies Final Business Payload Payload Metadata Core Components Information Components UMM Modeling Legacy Data TOP DOWN APPROACH BOTTOM UP APPROACH

32. 32 Information Harmonization EDI xCBL HL7 OTA RosettaNet OAG SAPXBRL UN/CEFACT Core Components 2002 2003 2004 2005 Existing eBusiness Standards UBL

33. 33 Runtime Stack (first look). O/S App Server ebXML MHS URL Port Security BPEE BP Rules BPSS CPP/A I/O

34. 34 ebXML Use Case Management Production Sales and Marketing CRM PR / IR ShippingProcurement

35. 35 ebXML Business Service Interfaces Management Production Sales and Marketing CRM PR / IR ShippingProcurement OUTSOURCE

36. 36 Some Final Thoughts..  ebXML ideal foundation for Web Services.  Build an open architecture, not a “Standard”  Truly interoperable and Extensible (Global)  Includes everyone from SME’s to Fortune 1000.  Facilitates global eBusiness. Q & A Duane Nickull

37. 37 Q & A