Running IBM MQ configuration and monitoring extensions

This section contains information about configuring and controlling the IBM MQ configuration extension and the IBM 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.

Related topics

Installing-the-IBM-MQ-configuration-and-monitoring-extensions

Uninstalling-the-IBM-MQ-configuration-and-monitoring-extensions

Running-performance-and-availability-monitoring-extensions

Configuring-IBM-MQ-agentless-services

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

In IBM 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-IBM-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-IBM-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 

MVMM 

Extensible Agent and extension files, then do so now. See Using-Deployments-to-distribute-the-agent-and-extensions-packages for details.

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

The IBM MQ monitoring extension collects information from various IBM MQ properties and passes it to the MVMM Extensible Agent, which then sends it to the MVMM Topic Service and on to the MainView Middleware MonitorManagement Console.

Note

The IBM 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 IBM MQ versions are installed, when IBM MQ is not installed in the default location, or when no IBM MQ 7.1 is designated as the primary installation. In this situation you must configure the IBM MQ Monitor preference DefaultMQInstallationPath to point to the path to any valid IBM 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

 

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