Configuring Trading Partner Agreements

TPA Parameter	Description
agreement	URI of the location that contains the partner agreement.
mepBinding	Select one of the following MEP type: One-Way/Push One-Way/Pull Two-Way/Sync Two-Way/Push-Pull Two-Way/Push-Push
initiator	Information that identifies the initiator of the message exchange. Configure the following initiator parameters:
	Parameter Name	Description
	id	External ID of the initiating MSH. The contents of this parameter map to the element Messaging/UserMessage/PartyInfo/From/PartyId.
	type	External ID type of the initiating MSH, as defined in the trading partner profile. For example, D-U-N-S.
	role	URI of the location where the agreement is stored
	host	Whether the partner profile is the host or not for a document exchange. If you set this parameter to 'true', then the certificates associated with this partner is selected. Configure this parameter only when the Trading Networks partner profile is not the enterprise profile during a document exchange between two partners. Note: Ensure that you configure either the initiator or the responder TPA parameter as the host.
	authorization	Optional. User credentials the pull signal receiver needs to authorize the pull signal. Specify username and password.
responder	Information that identifies the responder. Configure the following responder parameters:
	Parameter	Description
	id	External ID of the responding MSH, as defined in the trading partner profile.
	type	External ID type of the responding MSH, as defined in the trading partner profile. For example, D-U-N-S.
	role	URI of the location where the agreement is stored.
	host	Whether the partner profile is the host or not for a document exchange. If you set this parameter to 'true', then the certificates associated with this partner is selected. Configure this parameter only when the Trading Networks partner profile is not the enterprise profile during a document exchange between two partners. Note: Ensure that you configure either the initiator or the responder TPA parameter as the host.
legs	Defines processing, transportation binding, and business information parameters. Add one or more legs by clicking Add. Click Insert to add a leg before the current leg. Configure the following leg parameters:
	Parameter	Description
	label	MEP leg name. Select one of the following: requestUM: Select when using One-Way/Push, One-Way/Pull, Two-Way/Sync, Two-Way/Push-Pull, and Two-Way/Push-Push. requestSM: Select when using One-Way/Pull. replyUM: Select when using Two-Way/Sync, Two-Way/Push-Pull, and Two-Way/Push-Push.
	protocol	Identifies the type of transport between two MSHs and information related to the MSHs. Configure the following parameters: address: Endpoint URI of the responding MSH. For example, http://host:port/ws/msh/receive username: Username to authenticate the access to the partner's endpoint URI. password: Password to authenticate the access to the partner's endpoint URI. addActorOrRoleAttribute: Specifies whether the role attribute will be added to the message header. For more information, see Configuring Multi-Hop Messaging at an Endpoint
	businessInfo	Identifies message exchange service information for a pair of trading partners. Configure the following parameters: service: URI of the service that processes the message. serviceType: Name of the service type that indicates how the sender and receiver will interpret the service element. If you do not enter a value for this parameter, the service parameter must be a URI. action: URI of the element that identifies an operation or an activity within a service. properties: Properties required in the message. If the required properties are missing, the processing of the message stops and an error is returned. Click Add or Insert and configure the following parameters: name, description and, required. mpc: Message Partition Channel (MPC) identifier. The user message or signal will use this MPC. extendedInfo: Configure multiple message exchange service, service type, and action.