Understanding eb XML Enabling the global use of

Understanding eb. XML Enabling the global use of electronic business Duane Nickull Chief Technology Officer [email protected] com www. xmlglobal. com

Topics § Introduction and Architecture § The eb. XML Technologies § Continuing work § Implementation and adoption 2

Introduction Understanding Mission and Architecture

eb. XML Mission eb. XML enables anyone, anywhere to do business with anyone else over the Internet 4

Support and Background § Custodians - UN/CEFACT and OASIS § 75+ vendors, open public work § Major industry groups – OAG, GCI, AIAG, Rosetta. Net, X 12 EDI… § Published first release of specifications in May, 2001. § Work continuing under UN/EWG § Alignment of diverse XML vocabularies 5

eb. XML model § SMALL - Simple consistent integration for day-today small business applications (accounting, taxes, catalogues, inventory…) § BROAD - Simple consistent integration across industry verticals (insurance, healthcare, transportation, food services…) § LARGE - And complex large system integration 6

What eb. XML does § “Who, What, When, How” § Trading Profile Management and Discovery. § Assembly of transaction content. § Establishing consistent data definitions § Business Process Collaboration. § Message Handling Services 7

eb. XML Technical Architecture 8

eb. XML Business information Collaborat ion Protocol Profile (CPP) Supported Business Process 1. . <> 1. . DTD’s Schemas? Decomposition to the most atomic level is the winning strategy for eb. XML. It allows for automated <> semantic recognition of business DTD’s Schemas? information by using Registry services. <> Business Information Entities <> Core Comp. Core Comp 9

eb. XML technologies § Message Handling Services § Business Processes § Registry § Core Components § Modelling Methodology 10

Continuing Work Version 2. 0 Features

UN/CEFACT eb. TWG Overview (Proposed) OASIS Components UN/CEFACT Contributions UMM CRM + CC = BIE May use Extends BCP Uses Applied to BCP + MC May Change Uses CC Discovery and analysis BOTL Builds BPAIM UML to XML BPS 1. . * References Creates Forms References ASDOC 1. . * Yields References Creates BIE Governs UML to XML CCR MSG CCP 1 Is carried by PAYLOAD CCR (CQ) Binds CPA Creates (RT) Context Creates CRM CCP 2 BP CAT Registry 12

eb. XML as a series of Web Services CPP Manager (1) Eb. XML Registry Controller System Manager CPA Generator (2) eb. XML Repository (Managed Object Manager) Core Component Engine (3) XML Transformation Processor (4) BPSS Processor eb. XML Messaging Interface eb. XML Registry Message Manager eb. XML Registry Message Translator eb. XML Listener Payment Processing API eb. XML Registry API via Web Services Infrastructure Components eb. XML Framework with Web Services Client Side Components 13

Implementation and Adoption The Five Steps from Zero to Go!

Five Steps 1. Use eb. XML MHS and add UID references to existing content structures (EDI / XML) 2. Store vocabulary and transaction components in Registry 3. Adopt eb. XML BPSS definitions 4. Migrate toward eb. XML core components 15

Planning § 1 year, 2 year and 5 years out. § Issues, implementation criteria, ROI, support, interoperability, XML. § Schema neutral content assembly. § Separation of business semantics from XML mechanics. 16

Thank you Your XML Future http: //www. eb. XML. org http: //www. eb. XMLbook. com Exit 17

Message Handling Services Transport, Routing and Packaging (TRP)

eb. XML Transport Components 19

Transport Structure DEMO 20

Interchange sequence detail § A complete interchange consists of successfully: passed authentication/access control sent the bits to the other end checked the packaging checked the header structure checked the header data checked the signature on a header (*) decrypted the payload (*) verified the signature on a payload (*) checked the structure of a payload (*) passed the translated payload to a backend system/application for processing § Backend application successfully processed the payload Note: Items denoted (*) are optional § § § § § 21

Business Processes Methodology, Design and Representation

XML driven service layer(s) Partners Systems Integration Business Systems Customers Information Services XML Layer Business Enterprise Process Integration Open Socket Interface XML Content XML Data XML Products XML Services 23

Goal: Single face Solution n atio por Need to derive core components and standard business processes to reduce interface complexity In t er fa ce Cor Si ng le ing d ra T ers rtn Pa Integration at point of use. 24

Enabling Business Processes § Classification structures § Registration of business domains § Detailing of process steps § Facilitation and Choreography details § Linkage to Core Components 25

Collaboration Choreography Start Guard Success Start Guard Failed Transaction Activity Success Start Guard Transaction Activity Failure Success Failure 26

Requesting Activity Unit of Work Responding Activity Request Document Receipt. Acknowledgment Signal Signed. Receipt Non. Repudi ation Acceptance. Acknowledgment Signal Response Document Non. Repudi ation Time-Outs Guards Success Failure Business Transaction Legally Binding 27

Registry Role and Services

Version 1. 0 Registry and Registry Client § § Loosely coupled Must support Registry Service Specification (RSS) Must support eb. XML Messaging Service Handler (MSH) Uses Security Model REGISTRY CLIENT API REGISTRY (RIM) § The RSS governs a DTD to set the syntax for queries, Object Management and Returns including confirmations and errors. 29

eb. XML v 1. 0 Registry Architecture Managed Objects Passed by URI Reference Applications GUI’s Referenced By URI RIM Object. Manager() Object. Query Manager() RSS Messaging Transport Layer Registry Side API RSS Messaging eb. XML MSH Transport Layer Client Side 30

Registry Server Deployment Applications INTERNE T Registry Server JAVA SERVER PAGES API Users REGISTRY (RIM) 31

Registry Queries § Governed by RSS v 1. 0 (www. ebxml. org) § Query. Manager() interface exposes several methods. § Queries can return most parts of the RIM. § Return types are metadata. 32

Registry Query Sequence Managed Objects Return Applications GET Managed Object RIM RSS Messaging Transport Layer Query Return XML Query RIM DTD RIM XML Registry Side 33

Summary § Need § § § § Provide semantic registry Human interface Machine interface Classification and Associations UID and content notation synchronization Registry of Registries (UDDI one option) Certification of Registry implementations DEMO 34

Core Components Approach, Use, and Determining

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. 36

XML Elements § XML elements in business messages can reference items from a Registry. § Examples: § § <姓> All are the same item!!! 37

Linking Core Components § XML elements in business messages can reference items in a registry. § Examples: § § <姓 UID=“myrep: 1236”> All are the same item!!! 38

§ XML Elements in document instances contain pointers to Repository Item’s. § Registry Items are metadata – not instances of data. 12345 姓 Last. Name < 姓 UID=“Foo. Rep: 12345”> Duane Registry API Managed object 39

Core Component Realization DEMO 40

UN/CEFACT eb. TWG Overview. Contributions (Proposed) UN/CEFACT OASIS Components UMM CRM + CC = BIE May use Extends BCP Uses Applied to BCP + MC May Change Uses CC Discovery and analysis BOTL Builds BPAIM UML to XML BPS 1. . * References Creates Forms References ASDOC 1. . * Yields References Creates BIE Governs UML to XML CCR MSG CCP 1 Is carried by PAYLOAD CCR (CQ) Binds CPA Creates (RT) Context Creates CRM CCP 2 BP CAT Registry 41

eb. XML Compliant Query/Response Interface eb. TWG – CCR bridge for legacy data Transformation Service Layer Filters Templates Transformation Services Control Templates Registry Content Domains DISA X 12 EDI OAG BOD's Accounting XBRL Core Components Element Definitions Transaction Assembly 42

Core Components Today § Grab from Legacy data and store in XML format. § Can use Contextual modifications so all trading partners can use. DEMO CC DEMO CRM 43

44

Business Integration Needs Crosswalks and Core Components

Modelling Methodology Approach, Tools, Techniques

Concepts § Business Process and associated Information Model. § An XML Representation of the Business Process (BPS) and the Business Information (BIE, CC). § A mechanism for registering and storing them (Registry) • A mechanism for declaring a Trading Partners’ capabilities and what Business Processes and Information they use/support (CPP) 47

More Concepts § Mechanism for describing a Trading Partner Agreement (CPA) § Standardized messaging service (MSH) § Methodology/process for modelling the real world business and translating it into XML. (UMM and UML to XML rules) 48

Methodology – Business Language Artifacts 4 Collaboration Partner Profiles 2 Partner 3 Rules Messages Nouns To/From Events 2 3 5 Collaboration Partner Agreements Messages Verbs 1 Transport Routing, Packaging Nouns 4 Process Verbs 1 Transport Routing, Packaging 2 Roles Groupings based on simple Input-Output model 49

eb. XML Model View B U S I N E S S T R A N S A C T I O N S Business Operational View Business aspects of business transactions Comply with Covered by Viewed as BOV related standards* Functional Service View Information technology aspects of business transactions Comply with Covered by FSV related standards * UML Models 50

Business Operational View 51

FSV Architecture CPA Interface 52

Thank you Your XML Future http: //www. eb. XML. org http: //www. eb. XMLbook. com 53