Running WebSphere MQ configuration and monitoring extensions

This section contains information about configuring and controlling the WebSphere MQ configuration extension and the WebSphere MQ monitoring extension on the supported platforms, and includes:

Supported middleware monitoring technologies for performance and availability provides a list of the technology/platform pairs and appropriate versions that are supported in this release.

For information on installing this extension on the various supported platforms, see Installing the WebSphere MQ configuration and monitoring extensions.

Configuring WebSphere MQ agentless services

Running application transaction tracing (transaction monitoring) extensions

In IBM WebSphere MQ Version 8 and higher, individual queue managers can be configured to allow or require connecting applications to supply an explicit userid and password for Connection Authentication. Refer to Configuring the WebSphere MQ Extensions for queue managers which require authentication for configuration instructions if you are using this IBM MQ feature.

Note

When installing in an Agentless Configuration, follow the instructions for the platform where the Agentless Services are to be installed rather than that of the target queue manager. Also note that BMC does not support the installation of the Agentless Services on all platforms. See Configuring WebSphere MQ agentless services for details. Finally, note that all target queue manager platforms are not supported for agentless configurations.

If you have not already distributed your TMTM Extensible Agent and extension files, then do so now. See Distributing the Agent and extensions via the launch page for details.

The WebSphere MQ configuration extension allows you to configure your WebSphere MQ environment.

The WebSphere MQ monitoring extension collects information from various WebSphere MQ properties and passes it to the TMTM Extensible Agent, which then sends it to the TMTM Topic Service and on to the TMTM Monitor Console.

Note

For WebSphere MQ 7.1 and later: The WebSphere MQ Monitor and Configuration extensions must be able to find an MQ 7.1 installation on the installed host. The extensions look in the default installation location automatically, but might fail to locate the installation when multiple WebSphere MQ versions are installed, when WebSphere MQ is not installed in the default location, or when no WebSphere MQ 7.1 is designated as the primary installation. In this situation you must configure the WebSphere MQ Monitor preference DefaultMQInstallationPath to point to the path to any valid WebSphere MQ 7.1 installation. This can be configured via the Configuration Manager Agent Preferences dialog box or via agentpref, such as in this example:

agentpref --set "WebSphere MQ Monitor" DefaultMQInstallationPath /opt/My/Installation/Path --notify "WebSphere MQ Monitor" --notify "WebSphere MQ Configuration"

Note

The --notify option is only needed on 7.0 agents and earlier; 8.x agents are notified automatically.

Running WebSphere MQ configuration and monitoring extensions

Comments