Agreement Identification in ebMS

TPA Identification details

Following are the various mechanisms with which the agreement would be identified using ebMS protocol.

Outbound scenario:

1) From, To, Document Type and Document Revision: In Oracle AS B2B, it is possible to identify the agreement using these attributes.

2) Service based Identification
If document Type and Document Revision is not present and if the ebMS service is available, which is enqueued using the ACTION attribute, then the ebMS service attribute is used to identify the Document Type and Document Revision and identify the agreement based on step 1.

3) Action based Identification
If document Type and Document Revision is not present and if the ebMS Action is available, which is enqueued using the ACTION attribute, then the ebMS action attribute is used to identify the Document Type and Document Revision and identify the agreement based on step 1.


Inbound Scenario

1) From, To, Document Type and Document Revision: In Oracle AS B2B, it is possible to identify the agreement using these attributes. Since Oracle AS B2B supports custom over ebMS Business protocol, the custom Document Type and Document Revision can be retrieved by applying the Xpath expression on the payload.

2) Action based Identification
If the Business Action matches with the ebMS header Action of the incoming message, then the respective Document Type and Document Revision will be used to identify the agreement based on step 1.

3) CPAId based Identification
The following property in tip.properties, “oracle.tip.adapter.b2b.ebms.IdentifyAgreement.cpaId=true” indicates then the incoming document’s agreement Identification will be based on ebMS header CPAId with the Agreement ID. If this value is set true, then this overrides all the above mechanisms for inbound agreement identification, as this is a global setting.