OAGIS Implementation Using eb XML Specification v 1

OAGIS Implementation Using eb. XML Specification v 1. 0 Jean-Jacques Dubray, Chief Architect e. Xcelon Corp.

Outline Background B 2 B Collaborations - modeling - Protocol profile and agreement A 2 A Integration Scenarios

Background

OAGIS and eb. XML Like Hand Glove Define Content Business Documents Business Transactions <PO> … </PO> Business Collaborations Implement Discover Party A Collaboration Protocol Profile Party B Collaboration Protocol Profile eb. XML Registry Collaboration Protocol Agreement Design Time Run Time Transact Party A Messaging Service Party B

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

Correspondence Between eb. XML and OAGIS Eb. XML Specification Element OAGI Specification Element Process specification Scenario Diagrams Binary Collaboration No corresponding elements, Multi-party Collaboration No corresponding elements, Business Transaction Business Action Collaboration Protocol Profile Sub-Scenarios Business Object Document (BOD) No corresponding element Collaboration Protocol Agreement Registries No corresponding element Messaging service No corresponding element

eb. XML Business Collaboration Definitions

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

A Collaboration is Composed of Business Transactions

Business Signals and Responses Response required Parameter Name Meaning of timeout Receipt acknowledgement time. To. Acknowledge. Rec eipt The time a responding role has to acknowledge receipt of a business document. Acceptance Acknowledgement (Non -substantive) time. To. Acknowledge. Acce ptance The time a responding role has to non-substantively acknowledge business acceptance of a business document. Substantive Response Time. To. Perform The time a responding role has to substantively acknowledge business acceptance of a business document.

Exchange of Signals Without Errors

Scenario 55: RFQ / Quote

get. List RFQ Business Transaction

Business Transaction Activity Definitions

Choreography Specification

Binary Collaboration Specification <Binary. Collaboration name="oagi: 55. 0 INTERMEDIARY AND SUPPLIER RFQ QUOTE SCENARIO " time. To. Perform="P 30 D"> <Documentation>time. To. Perform = Period: 30 days from start of transaction</Documentation> <Initiating. Role name="supplier"/> <Responding. Role name="intermediary"/> <Business. Transaction. Activity name="Get RFQ List" business. Transaction="BT: Get RFQ List" from. Authorized. Role="supplier" to. Authorized. Role="intermediary"/> <Business. Transaction. Activity name="Get RFQ" business. Transaction="BT: Get RFQ" from. Authorized. Role="supplier " to. Authorized. Role="intermediary "/> <Start to. Business. State="Get RFQ List"/> <Transition from. Business. State="Get RFQ List" to. Business. State="Get RFQ"/>. . . </Binary. Collaboration>

BOD Specification <Business. Document name="Get. List RFQ" specification. Element=”/148_getlist_rfq_003” specification. Location= ”www. openapplications. org/OAGIS/v 7. 1/148_getlist_rfq_00 3. xsd” /> <Requesting. Business. Activity name="Request RFQ List"> <Document. Envelope business. Document="Getlist RFQ"/> </Requesting. Business. Activity>

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

Multi-Party Collaboration <Multi. Party. Collaboration name="OAGI: RFQ / Quote With Intermediary"> <Business. Partner. Role name="Buyer"> <Performs initiating. Role="Buyer"/> <Transition from. Business. State="Cancel RFQ Buyer" to. Business. State="Cancel RFQ Intermediary"/> </Business. Partner. Role> …

Using eb. XML Collaboration Definitions for Application-to. Application Integration Scenarios

A 2 A Metamodel

A 2 A Collaboration Specification Schema

OAGI eb. XML Specifications OAGI Industry Vertical Party E 2 E Integration Scenarios CPP Elements More CPP Elements CPP CPA Elements CPA A 2 A Integration Scenarios Other A 2 A Integration Scenarios

Using eb. XML Messaging Service (Preliminary)

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

eb. XML Message Structure

eb. XML Message Header · · · · · From To CPAId Conversation. Id Service Action Message. Data Quality. Of. Service. Info Sequence. Number Description N/A Integration Scenario BOD

Conclusion

eb. XML and OAGIS are truly in a win-win situation • Enables us to Formalize OAGI Integration Scenarios n B 2 B, A 2 A, E 2 E • The re-work is important to create eb. XML collaboration Definitions from current OAGIS documents n n Plug and play commerce Scenarios are not tied directly to BODs anymore