Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Running the WebSphere MQ BTM extension
A BTM WebSphere MQ API is provided as a dynamic (or shared) library that is loaded when the queue manager is started.
The BTM WebSphere MQ API monitors:
messages output via put or put1 APIs using a queue or topic
messages input via get or callback APIs using a queue or topic.
This section includes:
Warning
Note
Encryption and compression messages that are encrypted must be decrypted before they reach the BMC API to be processed by the BTM WebSphere MQ API exit. To ensure that the exits are processed in the correct order, the decryption API exit must have a larger sequence number than the BTM WebSphere MQ API exit. In addition, any compressed messages must be uncompressed before the BTM WebSphere MQ API exit can read them.