Synchronous Request Response Operation

The Synchronous Request Response Operation sends a document to the trading partner and wait for a response. It waits until the response is received and suspends any further processing for that request. This operation is used to send documents to trading partners and require a response for further processing.

The flow of operation is shown in the following figure.

Figure 14: Synchronous Request-Response Operation

The following process flow occurs with the Synchronous Request-Response Operation:

  1. The Initiator private process sends the request to the Initiator.

  2. The Initiator sends the request to the Responder and waits for the response until the timeout specified in the appropriate transport has expired.

  3. The Responder BusinessConnect Container Edition sends the request to the Responder private process.

  4. The Responder private process sends a response. If the private process does not respond on time, the Responder BusinessConnect Container Edition times out and ends the transaction. If the response from the private process arrives after this time out, the message is rejected and an error occurs.

  5. The response is forwarded to the Initiator BusinessConnect Container Edition.

  6. The Responder acknowledgment is sent to the private process indicating whether the response has been forwarded to the trading partner. It does not indicate whether the trading partner has received it or not.

  7. On receiving the response from the Responder, the Initiator sends the Initiator Response message. If the Initiator times out, an audit log entry is generated, a timeout error advisory is sent, and the connection is closed.

Note: Resending of Responder.Request and Responder.Response for the Synchronous Request Response operation is not supported for BusinessConnect Container Edition – Services Plug-in.

Supported transports are: HTTP, HTTPS, and HTTPSCA.