Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

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:

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.

Related topics

Installing-the-WebSphere-MQ-BTM-extension

Running-application-transaction-tracing-transaction-monitoring-extensions

Running-performance-and-availability-monitoring-extensions 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*