Error subflow for the Service Access from WebSphere MQ: one-way pattern

This subflow tests whether an error notification message must be written. Error notification messages do not preserve error data, but are used to notify system management that an error has occurred and that action might be required. The requirement for an error notification message is determined by the user-defined property: Error notification.

  1. If you have configured the pattern parameters to include error notification messages and the user-defined property Error notification is selected, an error message is prepared and written to the error queue. Details of the exception are written as an XML message. These details include:
    • Broker name
    • Flow name
    • Time stamp
    • Summary of the exception data

    The summary of the exception data contains the message flow label, error number, text description, and a list of inserts giving further details.

  2. This pattern is a one-way reliable pattern, and the incoming message data must therefore be persisted in the case of error.
    • If the Error action value is Roll back, an exception is produced and the message is backed out onto the input queue, which must be configured with a backout queue. In this case, all error events are written to the event log. You can use this action to detect the cause of the error.
    • If the Error action value is Error queue, the incoming message is written as a persistent message to an error queue for later corrective action. In this case, error events are not written to the event log. You can detect the cause of the error from the information that is in the error notification message.
Back to the Service Access from WebSphere MQ: one-way pattern specification