1 / 29

OAGIS Implementation Using ebXML Specification v1.0

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.

dashiell
Download Presentation

OAGIS Implementation Using ebXML Specification v1.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. Background

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

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

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

  7. ebXML Business Collaboration Definitions

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

  9. A Collaboration is Composed of Business Transactions

  10. Response required Parameter Name Meaning of timeout Business Signals and Responses Receipt acknowledgement timeToAcknowledgeReceipt The time a responding role has to acknowledge receipt of a business document. Acceptance Acknowledgement (Non-substantive) timeToAcknowledgeAcceptance The time a responding role has to non-substantively acknowledge business acceptance of a business document. Substantive Response TimeToPerform The time a responding role has to substantively acknowledge business acceptance of a business document.

  11. Exchange of Signals Without Errors

  12. Scenario 55: RFQ / Quote

  13. getList RFQ Business Transaction

  14. Business Transaction Activity Definitions

  15. Choreography Specification

  16. Binary Collaboration Specification <BinaryCollaboration name="oagi:55.0 INTERMEDIARY AND SUPPLIER RFQ - QUOTE SCENARIO " timeToPerform="P30D"> <Documentation>timeToPerform = Period: 30 days from start of transaction</Documentation> <InitiatingRole name="supplier"/> <RespondingRole name="intermediary"/> <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 "/> <Start toBusinessState="Get RFQ List"/> <Transition fromBusinessState="Get RFQ List" toBusinessState="Get RFQ"/> ... </BinaryCollaboration>

  17. BOD Specification <BusinessDocument name="GetList RFQ" specificationElement=”/148_getlist_rfq_003” specificationLocation= ”www.openapplications.org/OAGIS/v7.1/148_getlist_rfq_003.xsd” /> <RequestingBusinessActivity name="Request RFQ List"> <DocumentEnvelope businessDocument="Getlist RFQ"/> </RequestingBusinessActivity>

  18. Business Collaboration Failures • Timeout • Technical Failures • Business Failures • 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

  19. Multi-Party Collaboration <MultiPartyCollaboration name="OAGI:RFQ / Quote With Intermediary"> <BusinessPartnerRole name="Buyer"> <Performs initiatingRole="Buyer"/> <Transition fromBusinessState="Cancel RFQ Buyer" toBusinessState="Cancel RFQ Intermediary"/> </BusinessPartnerRole> …

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

  21. A2A Metamodel

  22. A2A Collaboration Specification Schema

  23. OAGI ebXML Specifications OAGI Industry Vertical Party E2E Integration Scenarios E2E Integration Scenarios E2E Integration Scenarios CPP Elements More CPP Elements CPP CPA Elements CPA A2A Integration Scenarios Other A2A Integration Scenarios

  24. Using ebXML Messaging Service (Preliminary)

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

  26. ebXML Message Structure

  27. ebXML Message Header • ·From • ·To • ·CPAId • ·ConversationId • ·Service • ·Action • ·MessageData • ·QualityOfServiceInfo • ·SequenceNumber • Description N/A Integration Scenario BOD

  28. Conclusion

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

More Related