WebSphere Message Brokers
File: ac02140
Writer: Kate Hostler

Concept topic

This build: July 31, 2007 21:17:02

User exits

A user exit is user-provided custom software, written in C, to track data passing through message flows.

User-provided functions can be invoked at specific points during the life-cycle of a message as it passes through the message flow, and can invoke utility functions to query information about the point in the flow, and the contents of the message assembly.

The user exits can be invoked when one or more of the following events occurs:
Basic message flow
In the basic message flow shown above, you can track messages at two levels:
At the transaction level, you can track the following events:
At the node level, you can track the following events:
Therefore, you can track four different types of events, which occur in the following sequence:
  1. Message dequeued from the input source (read into the flow)
  2. Message propagated to the node for processing
  3. Node processing completed
  4. End of the transaction
Related tasks
Exploiting user exits
Developing a user exit
Deploying a user exit
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:17:02

ac02140 This topic's URL is: