OAGIS Implementation Using ebXML Specification v1.0 Jean-Jacques Dubray, Chief Architect eXcelon Corp.

Outline Background B2B Collaborations - modeling - Protocol profile and agreement A2A Integration Scenarios

Background

OAGIS and ebXML Like Hand and Glove Transact Party A Party B Messaging Service Run Time Design Time Define Content … Business Transactions Business Collaborations Business Documents Implement Discover Party A Party B Collaboration Protocol Profile Collaboration Protocol Profile ebXML Registry Collaboration Protocol Agreement

ebXML (Published) Specifications Transact Define Content OAGI Business Object Documents (BODs) RosettaNet Partner Interface Process PIPs Implement Discover ebXML Collaboration Protocol Profile ebXML Collaboration Protocol Agreement ebXML Messaging Service (Transport Routing and Packaging) ebXML Registry Service ebXML Business Process Specification STAR Scenarios & Subscenarios OAGI Scenarios & Subscenarios

Correspondence Between ebXML and OAGIS EbXML Specification ElementOAGI Specification Element Process specificationScenario Diagrams Binary CollaborationNo corresponding elements, Multi-party CollaborationNo corresponding elements, Business Transaction Sub-Scenarios Business ActionBusiness Object Document (BOD) Collaboration Protocol ProfileNo corresponding element Collaboration Protocol Agreement No corresponding element RegistriesNo corresponding element Messaging serviceNo corresponding element

ebXML Business Collaboration Definitions

ebXML Process Specification Business transaction specifications Document specifications Binary collaboration specifications Multi-party collaboration specifications All OAGIS Integration Scenarios Can Be Formally Expressed With an ebXML Process Specification

A Collaboration is Composed of Business Transactions

Business Signals and Responses Response requiredParameter NameMeaning of timeout Receipt acknowledgement timeToAcknowledgeRece ipt The time a responding role has to acknowledge receipt of a business document. Acceptance Acknowledgement (Non-substantive) timeToAcknowledgeAcce ptance The time a responding role has to non-substantively acknowledge business acceptance of a business document. Substantive ResponseTimeToPerformThe time a responding role has to substantively acknowledge business acceptance of a business document.

Exchange of Signals Without Errors

Scenario 55: RFQ / Quote

getList RFQ Business Transaction

Business Transaction Activity Definitions

Choreography Specification

Binary Collaboration Specification timeToPerform = Period: 30 days from start of transaction <BusinessTransactionActivity name="Get RFQ List" businessTransaction=" BT: Get RFQ List" fromAuthorizedRole="supplier" toAuthorizedRole="intermediary"/> <BusinessTransactionActivity name="Get RFQ" businessTransaction="BT:Get RFQ" fromAuthorizedRole="supplier " toAuthorizedRole="intermediary "/> <Transition fromBusinessState="Get RFQ List" toBusinessState="Get RFQ"/>...

BOD Specification <BusinessDocument name="GetList RFQ" specificationElement=”/148_getlist_rfq_003” specificationLocation= ” />

Business Collaboration Failures Timeout Technical Failures Business Failures n Negative acknowledgement of receipt. The structure/schema of a message is invalid. n Negative acknowledgement of acceptance. The business rules are violated. n Performance exceptions. The requested business action cannot be performed. n Sequence exceptions. The order or type of a business document or business signal is incorrect. n Syntax exceptions. There is invalid punctuation, vocabulary or grammar in the business document or business signal. n Authorization exceptions. Roles are not authorized to participate in the business transaction. n Business process control exceptions. Business documents are not signed for non-repudiation when required

Multi-Party Collaboration <Transition fromBusinessState="Cancel RFQ Buyer" toBusinessState="Cancel RFQ Intermediary"/> …

Using ebXML Collaboration Definitions for Application-to- Application Integration Scenarios

A2A Metamodel

A2A Collaboration Specification Schema

OAGI ebXML Specifications OAGI E2E Integration Scenarios CPP Elements Industry VerticalParty A2A Integration Scenarios E2E Integration Scenarios More CPP Elements CPA Elements CPP CPA Other A2A Integration Scenarios E2E Integration Scenarios

Using ebXML Messaging Service (Preliminary)

How to exchange BODs with ebXML Messaging Service ebXML MS provides a framework to exchange business messages over a wide variety of transport n Securely n Guaranteed delivery n Quality of Service

ebXML Message Structure

ebXML Message Header  From  To  CPAId  ConversationId  Service  Action  MessageData  QualityOfServiceInfo  SequenceNumber Description N/A Integration Scenario BOD

Conclusion

ebXML and OAGIS are truly in a win-win situation Enables us to Formalize OAGI Integration Scenarios n B2B, A2A, E2E The re-work is important to create ebXML collaboration Definitions from current OAGIS documents n Plug and play commerce n Scenarios are not tied directly to BODs anymore