Configuring monitoring of IBM MQ Series

As an administrator, you want to keep your environment up and running at all times. For this purpose, you use BMC Helix Operations Management and TrueSight Operations Management. You start by collecting information (in the form of metrics) about your environment and then use this information to proactively resolve issues. After installing PATROL Agent and knowledge modules (KMs), you create a monitor policy. When the policy is enabled, data collection starts. For more information about monitor policies, see Defining monitor policies.

Related topics

Monitor-types-and-attributes

To configure monitoring of IBM MQ Series environment

  1. Perform one of the following actions:
    1. In BMC Helix Operations Management, click Configuration > Monitor Policies > Create.
    2. In TrueSight Operations Management, click Configuration > Infrastructure Policies > Create Policy.
  2. Click Add Monitoring Configuration.
  3. From the Monitoring Solution list, select BMC Performance Manager for WebSphere Business Integration.
    The values in the Version (latest) and Monitor Profile fields are set automatically.

  4. In the MQ Monitoring Configuration section, click Add.
    In the Environment Configurations window, enter the following details:

    Field

    Description

    Environment Configuration

    Environment name

    Enter a unique name for the environment under which IBM MQ Series instances are discovered.
    Use only alphanumeric characters in the name (A-Z, a-z, 0-9).
    Do not use any of the following characters:  ![@#$%?{}^\\\/|+=\&*();']

    Connection Details

    MQ Server

    Enter the Local or Remote MQ Server, for example, mqserver.abc.com. If $HOSTNAME is not functional, use the actual hostname, localhost, IP address, or 127.0.0.1.

    For local monitoring, do not configure remote queue manager details.

    Local installation path

    MQ installation path

    If your IBM MQ is installed at the default location, skip this field and default installation path is used for monitoring.
    If you have installed IBM MQ at a custom location other than the default one, enter the custom installation path here.
    The default installation path for Linux operating system is /opt/mqm.
    The default installation path for     Windows operating system is C:\\Program Files\\ibm.

    Monitor Remote Queue Manager

    Remote Queue Managers

    Remote Queue Manager Connection Details

    Remote Queue Manager Name

    Enter the remote queue manager name to monitor.

    MQ Listener Port

    Enter the port number of the MQ listener.

    Server-connection channel

    Enter the channel to the server connection.

    MQ Server Credentials

    User name

    Enter the username to connect to the MQ queue manager.

    Password

    Enter the password.

    Device Mapping

    Remote Queue Manager Device

    Select the required option from the list to enable the device mapping of the nodes.
    Host name: Device is created using the host name, which is returned from the API.
    DNS lookup: Device is created by resolving the DNS name.
    None: Device is not created.
    When you select one of the device mapping option, all the database instances are discovered under the host device.

    SSL Certificate Details

    Use SSL

    Select this option to enable the SSL connection.

    Trust store file

    Enter the path of the trust store file.
    For example, for Windows     C:\\ibm_mq\\jks\\truststore.jks and for Linux /opt/mqm/ibm_mq/jks/truststore.jks.

    Trust store password

    Enter the password for the trust store.

    Key store file

    Enter the path of the key store file. This is optional for client and can be used for two-way authentication for client.
    For example, for Windows     C:\\ibm_mq\\jks\\keystore.jks and for Linux /opt/mqm/ibm_mq/jks/keystore.jks.

    Key store password

    Enter the password for the key store. This is optional for client and is required only if  is configured.

    Filtering Options

    MQ Queue Manager Filter

    Enter the MQ queue manager names that you want to include or exclude from the monitoring.
    You can enter the exact MQ queue manager name or regular expression matching one or more names.
    For example, QMGR_PROD.* or QMGR_DEV.*|QMGR_QA.*

    MQ Queue Manager Filter Type

    Select the include or exclude option to filter the MQ queue manager names.

    MQ Listener Filter

    Enter the MQ listener names that you want to include or exclude from the monitoring.
    You can enter the exact MQ listener name or regular expression matching one or more names.
    For example, Listener1.*|Listener2.*

    MQ Listener Filter Type

    Select the include or exclude option to filter the MQ listener names.

    MQ Channel Filter

    Enter the MQ channel names that you want to include or exclude from the monitoring.
    You can enter the exact MQ channel name or regular expression matching one or more names.
    For example, Channel.*|Channel2.*

    MQ Channel Filter Type

    Select the include or exclude option to filter the MQ channel names.

    MQ Queue Filter

    Enter the MQ queue names that you want to include or exclude from the monitoring.
    You can enter the exact MQ queue name or regular expression matching one or more names.
    For example, Notif.* or Config.*|Deploy.*

    MQ Queue Filter Type

    Select the include or exclude option to filter the MQ queue names.

    KM Administration

    Optional JVM args

    Enter JVM arguments for the Java collector.

    Logging

    Select this option to enable PSL and Java debug.

    Administration

    Java home

    By default, the KM uses Java Runtime Environment (JRE) that is installed in the PATROL_HOME directory. To use your own JRE that is installed at a different location, enter the path for the Java home directory.
    For example, if your Java executable exists at the /usr/java/jdk1.8.0_45/jre/bin/java     path, enter /usr/java/jdk1.8.0_45/jre as the value of this field.

 

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