ebXML Module 7.1 SP1 | Understanding and Using webMethods EBXML Module | Installing and Using ebxml Module | Trading Partner Agreement Parameters Version 1. 0 | TPA Parameters for ebXML Message Service Version 1.0 Specification | Default Parameter Values
 
Default Parameter Values
In Trading Networks, when you specify the initialization service ( wm.ip.ebxml.cpa:initTPA1), the TPA IS document type parameters listed in the following table are populated with the default values indicated.
Parameter Name
Default Value
version
1.0
schemaLocation
http://www.ebxml.org/namespaces/tradePartner http://ebxml.org/project_teams/trade_partner/cpp-cpa-v1_0.xsd
Status
agreed
PartyInfo.CollaborationRole.ServiceBinding:channelId
DC1
PartyInfo.CollaborationRole.ServiceBinding:packageId
PKG1
PartyInfo.DeliveryChannel:channelId
DC1
PartyInfo.DeliveryChannel:docExchangeId
DX1
PartyInfo.DeliveryChannel.Characteristics:syncReplyMode
none
PartyInfo.DeliveryChannel.Characteristics:nonrepudiationOfOrigin
False
PartyInfo.DeliveryChannel.Characteristics:ackRequested
None
PartyInfo.DocExchange:docExchangeId
DX1
PartyInfo.DocExchange.ebXMLBinding:version
1.0
PartyInfo.DocExchange.ebXMLBinding.ReliableMessaging:deliverySemantics
OnceAndOnlyOnce
PartyInfo.DocExchange.ebXMLBinding.ReliableMessaging:deliveryReceiptRequested
None
PartyInfo.DocExchange.ebXMLBinding.ReliableMessaging:messageOrderSemantics
NotGuaranteed
Packaging:id
PKG1
Packaging.SimplePart:id
SP1
Packaging.SimplePart.mimetype
text/xml
Packaging.CompositeList.Composite:id
C1
Packaging.CompositeList.Composite.Constituent:idref
SP1
Note:
PartyInfo parameter settings are applicable to both sender and receiver parties.
Ensure the following points, when you create the TPA structure manually:
*The value of PartyInfo.DeliveryChannel:docExchangeId parameter is the same as the PartyInfo.DocExchange:docExchangeId parameter, in this case, DX1.
*The value of Packaging.CompositeList.Composite.Constituent:idref parameter is the same as the Packaging.SimplePart:id parameter, in this case, SP1.
*The values of PartyInfo.CollaborationRole.ServiceBinding:channelId parameter and PartyInfo.CollaborationRole.ServiceBinding:packageId parameter are the same as the PartyInfo.DeliveryChannel:channelId parameter and Packaging:id parameter respectively, in this case DC1 and PKG1 respectively.
To configure the TPA manually, for exchange of payload messages, you need to configure the following parameters:
Parameter
Default Value
PartyInfo.CollaborationRole.ServiceBinding.Service:body
util:testService
PartyInfo.CollaborationRole.ServiceBinding.Service:type
webMethods
PartyInfo.CollaborationRole.ServiceBinding.Override:action
testAction
PartyInfo.CollaborationRole.ServiceBinding.Override:channelId
DC1
PartyInfo.CollaborationRole.ServiceBinding.Override:packageId
PKG2
Packaging:id
PKG2
Packaging.SimplePart:id
SP2
Packaging.SimplePart:mimetype
Application/xml
Packaging.CompositeList.Composite.Constituent[0]:idref
SP1
Packaging.CompositeList.Composite.Constituent[1]:idref
SP2
To create the TPA structure manually for message exchange with payloads, configure the following parameters:
1. Define the Service Element. Specify a value for the PartyInfo.CollaborationRole.ServiceBinding.Service:body parameter. This value is used as the value of the Service element, ebXML Message Header of the payload messages.
For example, if the value of PartyInfo.CollaborationRole.ServiceBinding.Service:type is webMethods, the ebXML Module interprets the service as a webMethods Integration Server service and invokes it to process the message payloads.
2. Define the Action Element. Specify a value for PartyInfo.CollaborationRole.ServiceBinding.Override:action parameter. This value is used as the value of the Action element in the ebXML Message Header of the payload message.
3. Associate the Delivery Channel and Packaging for the Payload Message Exchange. Specify values for PartyInfo.CollaborationRole.ServiceBinding.Override:channelId and PartyInfo.CollaborationRole.ServiceBinding.Override:packageId parameters.
If the messaging requirements specified in the TPA for the payload message is not met by the DocExchange element DX1 associated with the default deliveryChannel DC1, you have to define a new DocExchange element say DX2 and a corresponding deliveryChannel DC2. Associate the Action element that you specified in step 2 with this deliveryChannel DC2.
4. Define the Packaging.SimplePart:id Parameter. Specify a value for Packaging.SimplePart:id parameter, say SP2, that attributes for the payload of the ebXML message.
5. Define the Packaging:id Parameter. Specify a value for the Packaging:id parameter, say PKG2.
6. Associate the CompositeList parameters to the Message. Specify the corresponding Packaging.CompositeList.Composite.Constituent[0]:idref parameter and Packaging.CompositeList.Composite.Constituent[1]:idref parameters to refer to the corresponding ebXML message, SP1 for the SOAP envelope and SP2 for the ebXML message with payload. Also, specify the value of the PartyInfo.CollaborationRole.ServiceBinding.Override:packageId parameter to PKG2.