Defining Trading Partner Agreements
The Trading Partner Agreement (TPA) schema used by Module for AS4 is based on Processing Modes (P-Modes), the P-Modes control how AS4 messages are processed. For more information about P-Modes, see OASIS ebXML Messaging Services 3.0 Version 1.0, Part 1, Core Features.
Every TPA is uniquely identified by a sender, a receiver, and an agreement ID. During a transaction between trading partners, the module retrieves the appropriate TPA based on this information and uses the TPA to process the business document being exchanged. Each TPA is associated with an MEP; therefore, for every MEP between a pair of trading partners, you must define a separate TPA.
Note:
With ENTSOG, the agreement ID and TPA are optional. For more information about the optional
pmodeId, see
wm.ip.estd.as4.msh:submit.
Based on the message type, the module uses the appropriate leg (requestUM, requestSM, or replyUM) to process the AS4 message. For more information about configuring MEPs and legs, see
Configuring Trading Partner
Agreements.
Define TPAs in My webMethods on the Administration > Integration > B2B > Trading Partner Agreements > Agreement Details page. For more information about defining TPAs, see webMethods Trading Networks Administrator’s Guide.