OAGIS Implementation Using ebXML

Specification v1.0

OAGIS Implementation Using ebXML

Specification v1.0

Jean-Jacques Dubray, Chief Architect

eXcelon Corp.

OutlineOutline

Background

B2B Collaborations

- modeling

- Protocol profile and agreement

A2A Integration Scenarios

BackgroundBackground

OAGIS and ebXML Like Hand and GloveOAGIS and ebXML Like Hand and Glove

TransactTransact

PartyA

PartyA

PartyB

PartyB

Messaging

Service

Run Time

Design Time

Define ContentDefine Content<PO>

…</PO>

Business Transactions

Business Collaborations

Business Documents

Implement DiscoverImplement Discover

PartyA

PartyA

PartyB

PartyB

CollaborationProtocolProfile

CollaborationProtocolProfile

ebXMLRegistryebXML

Registry

CollaborationProtocol

Agreement

ebXML (Published) SpecificationsebXML (Published) Specifications

TransactTransact

Define ContentDefine ContentOAGI

BusinessObject

Documents(BODs)

RosettaNetPartner

InterfaceProcess

PIPs

Implement DiscoverImplement Discover

ebXML Collaboration Protocol ProfileebXML Collaboration Protocol Profile

ebXML Collaboration Protocol AgreementebXML Collaboration Protocol Agreement

ebXML Messaging Service(Transport Routing and Packaging)

ebXML Messaging Service(Transport Routing and Packaging)

ebXMLRegistry Service

ebXMLRegistry Service

ebXML Business Process SpecificationebXML Business Process Specification

STARScenarios

&Subscenarios

OAGIScenarios

&Subscenarios

Correspondence Between ebXML and OAGISCorrespondence 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 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

ebXML Business Collaboration

Definitions

ebXML Business Collaboration

Definitions

ebXML Process SpecificationebXML Process Specification

• Business transaction specifications

• Document specifications

• Binary collaboration specifications

• Multi-party collaboration specificationsAll OAGIS Integration Scenarios

Can Be Formally Expressed With

an ebXML Process Specification

All OAGIS Integration Scenarios

Can Be Formally Expressed With

an ebXML Process Specification

A Collaboration is Composed of Business TransactionsA Collaboration is Composed of Business Transactions

Business Signals and ResponsesBusiness Signals and Responses

Response required Parameter Name Meaning of timeout

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.

Exchange of Signals Without ErrorsExchange of Signals Without Errors

OAG Adapter:Initiator

ebXMLInfrastructure:

Initiator

ebXMLInfrastructure:

Responder

OAG Adapter:Responder

1:BOD2:ebXML wrapped BOD

4: BOD

5: confirmBOD

3: acknowledgment of Receipt

6: acknowledgment of Acceptance

8: confirmBOD7: acknowledgment of Receipt

Scenario 55: RFQ / QuoteScenario 55: RFQ / Quote

Procurement / Purchasing

Sales Order Management

Cancel RFQ

BuyerOrganization

SupplierOrganization

Show RFQ

Getlist RFQ

Get RFQ

List RFQ

Add Quote

Change Quote

Cancel Quote

Add RFQ

Change RFQ

Cancel RFQ

Getlist Quote

Get Quote

Show Quote

List Quote

Intermediary

Respond RFQ

Respond Quote

Respond Quote

Sync RFQ

Respond RFQ

Cancel Quote

Sync Quote

getList RFQ Business TransactiongetList RFQ Business Transaction

Intermediary Supplier

//ItemNumber > 0

Success

RespondingActivity

GetList RFQRequesting

Activity

//ItemNumber = 0

Failure

List RFQ

Business Transaction Activity DefinitionsBusiness Transaction Activity Definitions Intermediary Supplier

show RFQ

getList RFQ

list RFQ

get RFQ

cancel RFQ

respond RFQ

respond RFQ

add Quote

sync Quote

change Quote

delete Quote

Choreography SpecificationChoreography Specification

getListRFQ

getRFQ

addQuote

Success

review Quote

review RFQ

BusinessFailure

syncQuote

respondQuote

cancelQuote

BusinessFailure

changeQuote

Binary Collaboration SpecificationBinary 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 SpecificationBOD 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 FailuresBusiness 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 CollaborationMulti-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-to-Application Integration

Scenarios

Using ebXML Collaboration Definitions

for Application-to-Application Integration

Scenarios

A2A MetamodelA2A Metamodel

Transaction

beginsWhen endsWhen isGuaranteedDeliveryRequired name postCondition preCondition

TransactionActivity

isConcurrent timeToPerform

Action

name

RequestingActivity

timeToAcknowledgeAcceptance

RespondingActivity

Activity

name

State

CollaborationActivity

BinaryCollaboration

beginsWhen endsWhen name postCondition preCondition timeToPerform

AuthorizedRole

isInitiator name

n

Performs

to

from

CommponentRole

name

n

A2A Collaboration Specification SchemaA2A Collaboration Specification Schema

OAGI ebXML SpecificationsOAGI ebXML Specifications

OAGIOAGI

E2EIntegrationScenarios

E2EIntegrationScenarios

CPPElements

CPPElements

Industry VerticalIndustry Vertical PartyParty

A2AIntegrationScenarios

A2AIntegrationScenarios

E2EIntegrationScenarios

E2EIntegrationScenarios

MoreCPP

Elements

MoreCPP

Elements

CPAElements

CPAElements

CPPCPP

CPACPA

Other A2AIntegrationScenarios

Other A2AIntegrationScenarios

E2EIntegrationScenarios

E2EIntegrationScenarios

Using ebXML Messaging Service

Using ebXML Messaging Service

(Preliminary)

How to exchange BODs with ebXML Messaging ServiceHow 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 StructureebXML Message Structure

ebXML Message HeaderebXML Message Header

      From

      To

      CPAId

      ConversationId

      Service

      Action

      MessageData

      QualityOfServiceInfo

      SequenceNumber

Description

N/A

Integration Scenario

BOD

ConclusionConclusion

ebXML and OAGIS are truly in a win-win situationebXML 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