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
Define Content
Business
Documents
Business
Transactions
<PO>
…
</PO>
Business
Collaborations
Implement
Discover
Party
A
Collaboration
Protocol
Profile
Party
B
Collaboration
Protocol
Profile
ebXML
Registry
Collaboration
Protocol
Agreement
Design Time
Run Time
Transact
Party
A
Messaging
Service
Party
B
ebXML (Published) Specifications
Define Content
OAGI
Business
Object
Documents
(BODs)
OAGI
STAR
Scenarios
Scenarios
&
&
Subscenarios
Subscenarios
RosettaNet
Partner
Interface
Process
PIPs
Implement
Discover
ebXML Business Process Specification
ebXML Collaboration Protocol Profile
ebXML Collaboration Protocol Agreement
Transact
ebXML Messaging Service
(Transport Routing and Packaging)
ebXML
Registry
Service
Correspondence Between
ebXML and OAGIS
EbXML 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
No corresponding element
ebXML
Business Collaboration
Definitions
ebXML Process Specification
• Business transaction specifications
• Document specifications
• Binary collaboration specifications
All OAGIS Integration Scenarios
• Multi-party collaboration specifications
Can Be Formally Expressed With
an ebXML Process Specification
A Collaboration is Composed of
Business Transactions
Business Signals and Responses
Response required
Parameter Name
Meaning 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 Response
TimeToPerform
The time a responding
role has to substantively
acknowledge business
acceptance of a
business document.
Exchange of Signals Without Errors
OAG Adapter:
Initiator
ebXML
Infrastructure:
Initiator
ebXML
Infrastructure:
Responder
OAG Adapter:
Responder
2:ebXML wrapped BOD
1:BOD
3: acknowledgment of Receipt
4: BOD
5: confirmBOD
6: acknowledgment of Acceptance
8: confirmBOD
7: acknowledgment of Receipt
Scenario 55: RFQ / Quote
Buyer
Organization
Supplier
Organization
Intermediary
Add RFQ
Getlist RFQ
List RFQ
Sync RFQ
Get RFQ
Respond RFQ
Change RFQ
Show RFQ
Cancel RFQ
Cancel RFQ
Respond RFQ
Procurement /
Purchasing
Sales Order
Management
Respond Quote
Add Quote
Getlist Quote
Sync Quote
List Quote
Get Quote
Show Quote
Cancel Quote
Respond Quote
Change Quote
Cancel Quote
getList RFQ Business Transaction
Intermediary
Responding
Activity
GetList RFQ
Supplier
List RFQ
Requesting
Activity
//ItemNumber > 0
//ItemNumber = 0
Success
Failure
Business Transaction Activity
Definitions
Intermediary
getList RFQ
list RFQ
get RFQ
show RFQ
respond RFQ
respond RFQ
cancel RFQ
add Quote
sync Quote
change Quote
delete Quote
Supplier
Choreography Specification
getList
RFQ
get
RFQ
review RFQ
cancel
Quote
add
Quote
Business
Failure
review Quote
Business
Failure
Success
sync
Quote
change
Quote
respond
Quote
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>
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>
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
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>
…
Using ebXML
Collaboration Definitions
for Application-toApplication Integration
Scenarios
A2A Metamodel
AuthorizedRole
Performs
from
isInitiator
name
to
n
CommponentRole
name
BinaryCollaboration
beginsWhen
endsWhen
name
postCondition
preCondition
timeToPerform
State
n
Activity
name
Transaction
TransactionActivity
beginsWhen
endsWhen
isGuaranteedDeliveryRequired
name
postCondition
preCondition
isConcurrent
timeToPerform
Action
name
RequestingActivity
timeToAcknow ledgeAcceptance
RespondingActivity
Collaboration
Activity
A2A Collaboration Specification
Schema
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
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

Securely

Guaranteed delivery

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

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