ebXML Module 7.1 SP1 | Understanding and Using webMethods EBXML Module | Installing and Using ebxml Module | Working with CPAs, TN Document Types, and Processing Rules | Manually Creating a TPA | Modifying and Extending the TPA
 
Modifying and Extending the TPA
To modify and extend the TPA as per your requirements, it is important to know the ebXML CPA (v1.0 and v2.0) document structure and its parameters. Although some minor differences exist between the TPAs for exchanging v1.0 messages and v2.0 messages, the overall structure is the same.
A TPA document contains two "PartyInfo" documents. Each PartyInfo document represents the messaging capabilities of a trading partner, identified by the "PartyId" document within PartyInfo. The PartyId value should map to the "External ID" of any one of the profiles defined in Trading Networks. A TPA document also contains one or more "Packaging" documents that define how the ebXML Message Header and payloads (defined within the SimplePart document) are packaged for transmittal.
The messaging characteristics associated with each party are defined using the "DocExchange," "Transport," and "DeliveryChannel" documents available within a PartyInfo document:
*The DocExchange document defines parameters for reliable messaging, digital signature, and encryption.
*The Transport document defines parameters for specifying the transport protocols supported by the partner. One or more "DocExchange" and "Transport" documents can be defined based on the messaging configurations supported by the partner.
*The DeliveryChannel document references a DocExchange and Transport document and contains additional parameters that you can configure to specify whether to:
*Have a message exchange be synchronous or asynchronous.
*Return an acknowledgment to acknowledge the receipt of a message.
*Specify that the acknowledgment, if required, should be signed or unsigned.
*Eliminate duplicate messages.
You can define one or more DeliveryChannels for each PartyInfo document.
The "CollaborationRole" document within PartyInfo contains the Service "action" combinations that a party is capable of sending. Each action is linked to a DeliveryChannel and Packaging document.
Note:
If you want to share a TPA with more than one partner, you create a Default TPA by setting the sender and/or receiver to Unknown. The Default TPA then can be used as a template by any sender or receiver.