530 likes | 543 Views
Learn about the mission, architecture, and technologies of ebXML, a framework that enables efficient and secure business transactions over the Internet.
E N D
Understanding ebXML Enabling the global use of electronic business Duane Nickull Chief Technology Officer duane@xmlglobal.com www.xmlglobal.com
Topics • Introduction and Architecture • The ebXML Technologies • Continuing work • Implementation and adoption
Introduction Understanding Mission and Architecture
ebXML Mission ebXML enables anyone, anywhere to do business with anyone else over the Internet
Support and Background • Custodians - UN/CEFACT and OASIS • 75+ vendors, open public work • Major industry groups – OAG, GCI, AIAG, RosettaNet, X12 EDI… • Published first release of specifications in May, 2001. • Work continuing under UN/EWG • Alignment of diverse XML vocabularies
ebXML model • SMALL - Simple consistent integration for day-to-day 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
What ebXML does • “Who, What, When, How” • Trading Profile Management and Discovery. • Assembly of transaction content. • Establishing consistent data definitions • Business Process Collaboration. • Message Handling Services
ebXML Business information 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. Collaboration Protocol Profile (CPP) Supported Business Process 1.. <<References>> 1.. <<Constructed From>> DTD’s Schemas? DTD’s Schemas? DTD’s Schemas? <<Constructed From>> Business Information Entities <<Constructed From>> Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp
ebXML technologies • Message Handling Services • Business Processes • Registry • Core Components • Modelling Methodology
Continuing Work Version 2.0 Features
BCP Uses BCP + MC Uses BOTL UN/CEFACT ebTWG Overview (Proposed) OASIS Components UN/CEFACT Contributions CRM + CC = BIE UMM May use May use Extends Applied to May Change CC Discovery and analysis Builds BPAIM Creates Forms UML to XML References Yields Creates BPS 1..* References ASDOC 1..* References BIE CC UML to XML Governs UML to XML CCR Is carried by MSG PAYLOAD CCR (CQ) CCP 1 Binds Binds CPA Creates (RT) Context Creates CRM CCP 2 BP CAT Registry Legend UMM = UN/CEFACT Modeling Methodology BCP = Business Collaboration Protocol BCP+MC = Business Collaboration Patterns and Monitored Commitments BIO = Business Information Object CC = Core Component (Tech neutral Business information unit) BPS = Business Process Schema (XML) BP CAT = Common Business Process Catalog CPP/A = OASIS ebXML CPP/A MSG = OASIS ebXML Messaging REG = OASIS ebXML Registry CRM = Context Rules Message from ebXML CCR = Core Component Realization (as an XBDL bus doc?) ASDOC = Assembly Doc (ebXML) BPAIM = Business Processes and Associated Information Models BIE = Business Information Entity PAYLOAD = a syntax specific electronic business message payload. BOTL = Business Object Type Library (BIO’s)
Controller System Manager CPP Manager (1) EbXML Registry CPA Generator (2) Core Component Engine (3) ebXML Repository (Managed Object Manager) XML Transformation Processor (4) BPSS Processor ebXML Messaging Interface ebXML Messaging Interface ebXML Registry Message Manager ebXML Registry Message Translator ebXML Listener Payment Processing API ebXML Framework with Web Services ebXML Registry API via Web Services Infrastructure Components Client Side Components ebXML as a series of Web Services RAWS
Implementation and Adoption The Five Steps from Zero to Go!
Five Steps • Use ebXML MHS and add UID references to existing content structures (EDI / XML) • Store vocabulary and transaction components in Registry • Adopt ebXML BPSS definitions • Migrate toward ebXML core components • Full compliance with ebXML infrastructure
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.
Thank you Your XML Future http://www.ebXML.org http://www.ebXMLbook.com Exit
Message Handling Services Transport, Routing and Packaging (TRP)
Transport Structure DEMO
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
Business Processes Methodology, Design and Representation
XML driven service layer(s) Partners Systems Integration Business Systems Customers Process Integration Open Socket Interface Information Services Layer XML XML XML XML XML XML XML XML XML Business Enterprise Services Content Products Data
Goal: Single face Solution Integration at point of use. Need to derive core components and standard business processes to reduce interface complexity Trading Partners Corporation Single Interface
Enabling Business Processes • Classification structures • Registration of business domains • Detailing of process steps • Facilitation and Choreography details • Linkage to Core Components
Collaboration Choreography Start Success Transaction Activity Guard Start Success Transaction Activity Failure Guard Failed Start Transaction Activity Success Guard Failure
Unit of Work Non-Repudiation Non-Repudiation Success Failure Business Transaction Requesting Activity Responding Activity Request Document ReceiptAcknowledgment Signal SignedReceipt AcceptanceAcknowledgment Signal Response Document Time-Outs Guards Legally Binding
Registry Role and Services
Version 1.0 Registry and Registry Client • Loosely coupled • Must support Registry Service Specification (RSS) • Must support ebXML 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.
Passed by URI Reference Applications GUI’s Referenced By URI ObjectManager() ObjectQuery Manager() ebXML MSH Transport Layer Transport Layer ebXML v 1.0 Registry Architecture Managed Objects RIM API RSS Messaging RSS Messaging Registry Side Client Side
Applications Registry Server Deployment INTERNET Registry Server JAVASERVERPAGES API REGISTRY (RIM) Users
Registry Queries • Governed by RSS v 1.0 (www.ebxml.org) • QueryManager() interface exposes several methods. • Queries can return most parts of the RIM. • Return types are metadata.
GET Managed Object Transport Layer Registry Query Sequence Managed Objects Applications Return RIM Query Return XML Query RSS Messaging RIM DTD RIM XML Registry Side
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
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.
XML Elements • XML elements in business messages can reference items from a Registry. • Examples: • <LastName> • <NomDeFamille> • <VorName> • <姓> All are the same item!!!
Linking Core Components • XML elements in business messages can reference items in a registry. • Examples: • <LastName UID=“myrep:1236”> • <NomDeFamille UID=“myrep:1236”> • <VorName UID=“myrep:1236”> • <姓 UID=“myrep:1236”> All are the same item!!!
XML Elements in document instances contain pointers to Repository Item’s. Registry Items are metadata – not instances of data. <?xml version=“1.0”> <UID>12345</UID> <Element> 姓 </Element> <Also org=“yourOrg”> LastName </Also> Repository Item <?xml version=“1.0”> < 姓UID=“FooRep:12345”> Duane </ 姓 > Document Instance Registry API API Managed object Managed object Managed object
UN/CEFACT ebTWG Overview (Proposed) OASIS Components UN/CEFACT Contributions CRM + CC = BIE UMM May use May use Extends Applied to May Change BCP Uses BCP + MC Uses BOTL CC Discovery and analysis Builds BPAIM Creates Forms UML to XML References Yields Creates BPS 1..* References ASDOC 1..* References BIE CC UML to XML Governs UML to XML CCR Is carried by MSG PAYLOAD CCR (CQ) CCP 1 Binds Binds CPA Creates (RT) Context Creates CRM CCP 2 BP CAT Registry Legend UMM = UN/CEFACT Modeling Methodology BCP = Business Collaboration Protocol BCP+MC = Business Collaboration Patterns and Monitored Commitments BIO = Business Information Object CC = Core Component (Tech neutral Business information unit) BPS = Business Process Schema (XML) BP CAT = Common Business Process Catalog CPP/A = OASIS ebXML CPP/A MSG = OASIS ebXML Messaging REG = OASIS ebXML Registry CRM = Context Rules Message from ebXML CCR = Core Component Realization (as an XBDL bus doc?) ASDOC = Assembly Doc (ebXML) BPAIM = Business Processes and Associated Information Models BIE = Business Information Entity PAYLOAD = a syntax specific electronic business message payload. BOTL = Business Object Type Library (BIO’s)
ebTWG – CCR - bridge for legacy data ebXML Compliant Query/Response Interface Filters Transformation Service Layer Templates Transformation Services Control Templates Registry Content Domains DISA X12 Accounting EDI OAG BOD's XBRL Core Core Element Definitions Components Components Core Transaction Assembly Components Element Definitions Element Definitions Transaction Assembly Transaction Assembly
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
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)
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)
Methodology – Business Language Artifacts Collaboration Partner Profiles 4 5 Collaboration Partner Agreements To/From Partner 2 Events 2 3 Rules 3 Messages Messages Verbs Verbs Nouns Nouns 1 4 1 Transport Routing, Packaging Process Transport Routing, Packaging 2 Roles Groupings based on simple Input-Output model
Business Operational View Comply with Business aspects of business transactions BOV related standards* Covered by Viewed as Functional Service View Information technology aspects of business transactions Comply with FSV related standards Covered by ebXML Model View B U S I N E S S T R A N S A C T I O N S * UML Models