Request flow for the Service Facade to WebSphere MQ: request-response pattern

Details about the Request flow, including logging and exceptions, for the Service Facade to WebSphere MQ: request-response pattern.

  1. A SOAP request is received on a SOAP node. The request is validated if validation is required, by the pattern parameters for each pattern instance.
  2. The SOAP and HTTP headers are removed to leave the basic XML message targeted at the provider application.
  3. The message then passes to a request processing subflow, which provides a place for customization of a pattern instance.
  4. An MQMD header is inserted with the Reply address of the message broker and the expiry time is set in accordance with the expected response time.
  5. The message is placed on the provider queue.
  6. A message to store the SOAP reply identifier is set up. The message identifier that is generated for the outgoing message is retrieved from the written destination data in the local environment, and is used in the MQMD correlation identifier; the SOAP reply identifier is retrieved from the local environment and is used as the body of the message. This data is written to an internal queue.
  7. If exceptions occur before the message is sent to the provider, a SOAP fault is returned to the provider. If error messages are required, an error message is sent to the error queue.
  8. If logging of requests is required and the message flow succeeds, the logging subflow is called to log the incoming message.
Back to the Service Facade to WebSphere MQ: request-response pattern specification