OAGIS Implementation Using ebXML Specification v1.0

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
Define Content
Business Transactions
ltPOgt lt/POgt
Business Documents
Business Collaborations
Design Time
Run Time
5
ebXML (Published) Specifications
Define Content
STAR Scenarios Subscenarios
OAGI Business Object Documents (BODs)
RosettaNet Partner Interface Process PIPs
OAGI Scenarios Subscenarios
Implement Discover
ebXML Registry Service
ebXML Collaboration Protocol Profile
ebXML Collaboration Protocol Agreement
Transact
ebXML Messaging Service (Transport Routing and
Packaging)
6
Correspondence Between ebXML and OAGIS
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
Business Signals and Responses
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
ltBinaryCollaboration name"oagi55.0 INTERMEDIARY
AND SUPPLIER RFQ - QUOTE SCENARIO "
timeToPerform"P30D"gt ltDocumentationgttimeToPerf
orm Period 30 days from start of
transactionlt/Documentationgt ltInitiatingRole
name"supplier"/gt ltRespondingRole
name"intermediary"/gt ltBusinessTransactionActiv
ity name"Get RFQ List"
businessTransaction"BTGet RFQ List"
fromAuthorizedRole"supplier"
toAuthorizedRole"intermediary"/gt
ltBusinessTransactionActivity name"Get RFQ"
businessTransaction"BTGet RFQ"
fromAuthorizedRole"supplier "
toAuthorizedRole"intermediary "/gt
ltStart toBusinessState"Get RFQ List"/gt
ltTransition fromBusinessState"Get RFQ List"
toBusinessState"Get
RFQ"/gt ... lt/BinaryCollaborationgt  
17
BOD Specification
ltBusinessDocument name"GetList RFQ"
specificationElement/148_getlist_rfq_003
specificationLocation
www.openapplications.org/OAGIS/v7.1/148_getlis
t_rfq_003.xsd /gt
ltRequestingBusinessActivity name"Request RFQ
List"gt ltDocumentEnvelope businessDocument"Getlis
t RFQ"/gt lt/RequestingBusinessActivitygt
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
ltMultiPartyCollaboration name"OAGIRFQ / Quote
With Intermediary"gt ltBusinessPartnerRole
name"Buyer"gt ltPerforms initiatingRole"Buyer"/gt
ltTransition fromBusinessState"Cancel RFQ
Buyer" toBusinessState"Cancel
RFQ Intermediary"/gt lt/BusinessPartnerRolegt

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