Log subflow for the Message Correlator for WebSphere MQ: request-response with persistence pattern

If the Log subflow is included in the Request flow, the logging of requests is controlled by the user-defined property: RequestLoggingOn. If the Log subflow is included in the Response flow, the logging of responses is controlled by the user-defined property: ResponseLoggingOn.

If the RequestLoggingOn property is selected, logging is required, the Log subflow is called and ends the flow. If the logging fails, the exception is caught within the flow and the information is written to a Trace node.

If logging is included in the Response flow, the Log subflow is called. All errors in logging are caught, the flow ends successfully and the flow transaction is committed.

Log messages are written as persistent WebSphere MQ messages to a WebSphere MQ queue. These log messages are then processed separately in accordance with the standard practices within your organization.

The message log contains the original message and the following information in an MQRFH2 header:
Back to the Message Correlator for WebSphere MQ: request-response with persistence pattern specification