ebXML Module Message Status Request Service

1. If you have not already done so, set up the profiles for using the wm.ip.ebxml.MSH:pingUsingTPA service as described in Initiating the ebXML Module Handshake.

3. Go to My webMethods: Monitoring > Integration > B2B > Transactions and select a DocumentID from the Seller Inc. partner's transaction view.

4. From Developer, invoke the wm.ip.ebxml.MSH:statusUsingTPA service. Set the MessageID input variable to the DocumentID value that you selected in the previous step. Also set the following example parameters:

5. Go to My webMethods: Monitoring > Integration > B2B > Transactionsand view the transactions for both trading partners. Here is an example that illustrates the transactions:

On the Buyer Inc. side:
TN Document Type	Sender	Receiver	UserStatus
ebXML Default	Buyer Inc.	Seller Inc.	SendMessage:sent
ebXML Default	Seller Inc.	Buyer Inc.	StatusResponse

On the Seller Inc. side:
TN Document Type	Sender	Receiver	UserStatus
ebXML Default	Buyer Inc.	Seller Inc.	StatusRequest
ebXML Default	Seller Inc.	Buyer Inc.	SendMessage:sent

The first message on the Buyer Inc. side is the ebXML Message Status Request message that the Buyer Inc. created and sent to the Seller Inc. partner. When the Seller Inc. partner receives it (see the first message on the Seller Inc. side), it creates an ebXML Message Status Response message and sends it back to the Buyer Inc. partner (see the second message on the Seller Inc. side).

Note that User Status of the second message for the Seller Inc. partner is SendMessage:sent. This indicates that the response message is asynchronous, based on the TPA parameter, syncReplyMode = none, that you set in the configuring the pingUsingTPA service procedure in The pingUsingTPA Service.

Note:
The syncReplyMode parameter takes four values, none, responseOnly, signalsAndResponse, signalsOnly. For ebXML Message Service Version 2.0 Specification, there is also an additional value, mshSignalsOnly. When the value is set to none the reply is asynchronous. At present, ebXML Module interprets the values of responseOnly, signalsAndResponse, signalsOnly, and mshSignalsOnly as synchronous, and does not specifically handle each of these values.

When the status response message arrives at the Buyer Inc. partner, the ebXML Module recognizes it as an ebXML Message Status Response message.

The ebXML Message Status Response will indicate the status of the message. For information on the status of the message, see the ebXML Message Service Version 1.0 Specification and ebXML Message Service Version 2.0 Specification.