Enabling the Message Ordering Feature

To enable Message Ordering, create a TPA on the sender side and the receiver side.

To configure ebXML Module for Message Ordering

1. Start the Trading Networks Console.

2. Open the agreement for edit:

a. From Trading Networks Console, select View > Agreements.

b. Select the agreement you would like to edit. ClickEdit.

The Agreements Details screen appears.

c. On the right side of the Agreement Details screen, click Set Inputs.

The input for com.wm.estd.ebxml.documents appears.

Note:
You can edit the TPA parameters in an agreement only if the Agreement Status is Proposed. For information about changing the TPA agreement status, see the webMethods Trading Networks Administrator’s Guide for your release.

3. Modify the default TPA parameters, as necessary. For a list of the TPA parameters and the valid values for individual parameters, see Trading Partner Agreement Parameters Version 2. 0 and Trading Partner Agreement Parameters Version 2. 0.

4. Update the settings in the TPA structure to enable reliable messaging as shown:

If you are using ebXML Message Service Version 1.0 Specification, set the following parameters:

Parameter	Value
CollaborationProtocolAgreement.PartyInfo.DocExchange.ebXMLBinding.ReliableMessaging:deliverySemantics	OnceandOnlyOnce
CollaborationProtocolAgreement.PartyInfo.DocExchange.ebXMLBinding.ReliableMessaging:messageOrderSemantics	Guaranteed
CollaborationProtocolAgreement.PartyInfo.DocExchange.ebXMLBinding.ReliableMessaging:PersistDuration	10 (time in seconds)
CollaborationProtocolAgreement.PartyInfo.DeliveryChannel.Characteristics:syncReplyMode	none

If you are using ebXML Message Service Version 2.0 Specification, set the following parameters:

Parameter	Value
CollaborationProtocolAgreement.PartyInfo.DeliveryChannel.MessagingCharacteristics:duplicateElimination	always
PartyInfo.DeliveryChannel.Characteristics:ackRequested	always
CollaborationProtocolAgreement.PartyInfo.DocExchange.ebXMLSenderBinding.ReliableMessaging:RetryInterval	5 (time in seconds)
CollaborationProtocolAgreement.PartyInfo.DocExchange.ebXMLSenderBinding.ReliableMessaging:Retries	30
CollaborationProtocolAgreement.PartyInfo.DocExchange.ebXMLReceiverBinding:PersistDuration	10 (time in seconds)
CollaborationProtocolAgreement.PartyInfo.DeliveryChannel.MessagingCharacteristics:syncReplyMode	none

Note:
For Message Ordering, do not set the syncReplyMode parameter to work in synchronous mode because as per the ebXML Message Service Version 1.0 Specification and ebXML Message Service Version 2.0 Specification, Message Ordering is not supported with synchronous messaging. Also the duplicateElimination parameter must not be set to never.

5. Invoke the wm.ip.ebxml.MSH:sendUsingTPA service for the ebXML Module to deliver a sequence of messages to the receiver. Trading Networks creates a sender specific TPA to track the sequence of messages that the sender sends.

When a message is sent using the Message Ordering feature, this TPA keeps track of the sequence of the messages as sent by the sender. The messages that the ebXML Module cannot deliver to the receiver are persisted by the sender, and the sender retries to send the messages. The receiver does not pass the messages to the receiver application if the messages are out of sequence. The ebXML Module starts the processing of the messages on the receiver side only after receiving all the messages of the defined sequence. You can view the transactions in My webMethods: Monitoring > Integration > B2B > Transactions. For more information about viewing transactions, see Viewing Transactions.