Visibility and Tracking

You can use an IBM visibility tool, InFlight, to review the status of processed IBM Sterling Synchronous B2B Process Service documents.

The service gives a green status to successfully processed transactions, and gives a red status to transactions that cannot be processed successfully. Because the Synchronous B2B Process Service document flows are synchronous flows, they are tracked as one transaction, with detailed steps and statuses of all processing steps.

When you search for documents that are related to the Synchronous B2B Process Service in InFlight, you might see the following messages:
Message Description
Primary Request This message is the initial web service request. You or your trading partner initiates a request to the service.
Secondary Request This message is the service making a secondary web service request to you or your trading partner.
Secondary Response This message is the response received from the secondary request.
Primary Response This message is the response from the service to the initiator of the primary request.

For more information about InFlight, see the IBM® Sterling InFlight Data Management User Guide.

Troubleshooting

Due to the nature of web service communication over HTTP, the most common errors you can expect to see are Failed to connect and Connection timed out. It is also possible that the data transformation can generate errors. If there is an error in the data transformation, the service sends an error response to you and logs a red event in InFlight.

Most of the messages contain a Source Message ID that uniquely identifies any particular session. To find this ID in InFlight, select a document and click the More Info icon to display the data detail.

Transaction numbers can be searched in InFlight as customer-defined reference fields.

Tip: If you must contact IBM for assistance, it is helpful for you to have the Source Message ID in order for customer support to be able to find out what happened to your data.
For data flows over SOAP protocol, the data format might be modified temporarily when the message is processed by or passes through the InFlight:
  • The element name is changed from Envelope to SOAP_Domain_Msg.
  • A Context node is inserted before the message body.
This temporary modification does not persist when the message is received or sent, but it does affect the information that is shown for tracking. Because the tracking information is gathered while the message is being processed, the modifications to the data format are visible if you look at the Data Details for the message in InFlight. The message body or content is not modified.