This topic contains sections marked as revised for this release
WebSphere Message Brokers
File: ac02150_
Writer: Stephanie J Strugnell Task topic This build: July 31, 2007 21:17:03
Developing a user exit
To develop a user exit, follow these steps:
Declare the user exit.
Declare a user exit by using
the bipInitializeUserExits function to specify the following
properties:
Name (used to register and control the active state of the exit)
User context storage
A function to be invoked (for one or more Event Types)
Implement the user exit behavior.
When the user exit
is declared, a set of functions is registered, and these functions are invoked
when specific events occur. The behavior of the user exit is provided by implementing
these functions. The following table lists the events and their associated
functions:
Event
Function
Message dequeued from input source
cciInputMessageCallback
Message propagated to node for processing
cciPropagatedMessageCallback
Node completed processing
cciNodeCompletionCallback
Transaction ended
cciTransactionEventCallback
Your user exit code must implement the cleanup function.
The user exit library must implement the bipTerminateUserExits function.
This function is invoked as the ExecutionGroup's process is ending, and your
user exit must clear up any resources allocated during the bipInitializeUserExits function.