WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
cciTransactionEventCallback
The cciTransactionEventCallback function can be registered as a callback and is called every time a message flow transaction ends.
This function is called for every message flow transaction within the execution group where the callback was registered, if the user exit state is active. The callback is registered by providing a pointer to the function in the iFpTransactionEventCallback field of the CCI_UE_VFT struct passed to cciRegisterUserExit.
Syntax
typedef void (*cciTransactionEventCallback) (
CciDataContext* userContext,
CciTransactionEventType type,
CciMessage* environment,
CciNode* inputNode);
Parameters
- userContext (input)
- This is the value that was passed to the cciRegisterUserExit function.
- type
- This describes the event that occurred. Possible values are:
- CCI_TRANSACTION_EVENT_COMMIT
A transaction has been successfully committed.
- CCI_TRANSACTION_EVENT_ROLLBACK
A transaction has been rolled back.
- CCI_TRANSACTION_EVENT_COMMIT
- environment
- This is a handle to the environment object for the current message flow. Although the user exit can update this tree, it is cleared after returning from this function, so any updates are lost.
- inputNode
- This is a handle to the input node which reads the input message that triggered the transaction. It can be used to make calls to functions such as cciGetNodeName, cciGetNodeType, and cniGetBrokerInfo.
Return values
None
Example
void myTransactionEventCallback(
CciDataContext* userContext,
CciTransactionEventType type,
CciMessage* environment,
CciNode* inputNode){
…
…
}