v2.0 websphere_mq AC Configuration

This section describes how to configure the WebSphere MQ Monitoring (websphere_mq) probe, including how to set up the monitoring parameters of the QMs, channels, queues, topics, and subscriptions. The probe automatically discovers the available QMs and other components of WebSphere MQ.
uimpga-ga
websphere_mq_2.0_AC
This section describes how to configure the WebSphere MQ Monitoring (websphere_mq) probe, including how to set up the monitoring parameters of the QMs, channels, queues, topics, and subscriptions. The probe automatically discovers the available QMs and other components of WebSphere MQ.
 
 
Verify Prerequisites
 The probe supports only IBM WebSphere MQ version 7.5.X for AIX 6.x (64-bit) operating system (OS) and versions 7.5.X (tested on 7.5.0.3) and 7.0.X (tested on 7.0.1.10) for all other supported OS (64-bit).
The preconfiguration requirements of the probe are as follows:
  • IBM WebSphere MQ is installed on the system, where the probe is deployed.
  • Install the appropriate MQSeries Java on the host system, if the probe is deployed on Linux or Solaris operating systems. For example, the MQSeriesJava-U200442-7.5.0-3.x86_64.rpm is required for monitoring 7.5.0.3 version of WebSphere MQ and the MQSeriesJava-7.0.1-3.x86_64.rpm is required for monitoring 7.0.1.3 version of WebSphere MQ. In case of multiple installations of WebSphere MQ, install the highest version of MQSeries Java.
  • Add hostname of the system, where the probe and IBM WebSphere MQ is installed, in the 
    /etc/hosts 
    file when the probe is deployed on Linux or Solaris operating systems. You can use the 
    vi /etc/hosts
     command for this purpose.
  • Ensure that command Server of the Queue Manager is up and running.
Preconfiguration Requirements for AIX
The controller of the robot where the probe is deployed must be configured to monitor IBM WebSphere MQ 7.5.x on the AIX 6.x family of operating systems.
 The probe supports only IBM WebSphere MQ 7.5.x on the AIX 6.x environment.
 
Follow this process
:
  1. Select the robot where the 
    websphere_mq
     probe is deployed for monitoring the AIX system.
  2. Open the 
    controller
     probe and navigate to the 
    Setup
     node.
  3. Create or reconfigure the following variables and their respective values in the 
    Environment Variables
     section:
    •  
      MQ_LIB_PATH:
       indicates the path of the MQ library to load the files that are required to run the probe.
      For example, specify the following path for different WebSphere MQ server installation:
      • 32-bit: 
        /usr/mqm/java/lib 
         
      • 64-bit: 
        /usr/mqm/java/lib64
         
    •  
      MQ_CLASSPATH:
       indicates the path of the specific jar available for WebSphere MQ that is required to run the probe. Example: 
      /usr/mqm/java/lib/* 
       
The websphere_mq probe can now be configured to monitor the AIX system.
Enable the Queue Monitors
The default configuration of IBM WebSphere MQ does not expose all monitoring data of the Message Queues to an external application. Therefore, when the probe runs a command to fetch monitoring data, WebSphere MQ does not return any value for the following monitors:
  • Oldest Message Age
  • On Queue Time
  • Time Since Last Get
  • Time Since Last Put
Set the MONQ property value of the message queue to LOW, MEDIUM, or HIGH to fetch the monitoring data. The recommended value is HIGH.
 
Follow these steps:
 
  1. Open the Linux or Solaris terminal.
  2. Go to the installation directory of WebSphere MQ. The default location is 
    /opt/mqm/bin
     on Linux.
  3. Go to the Queue Manager of the target message queue you want to monitor. For example, if your Queue Manager name is QM1, you can execute the following command:
    ./runmqsc QM1
  4. Execute the DISPLAY ALL command and verify if the MONQ property value is OFF.
  5. Execute the ALTER QMGR MONQ(HIGH) command and change the MONQ property value to HIGH for all message queues.
    Alternatively, execute the ALTER QLOCAL(MYQUEUE.Q) MONQ(HIGH) for changing the MONQ property value to HIGH for the given message queue. The QLOCAL is the queue type and MYQUEUE is the queue name.
The 
MONQ
 property value is changed to HIGH, therefore, allowing the probe to collect monitoring data about the message queues in the subsequent interval.
 Use the WebSphere MQ Explorer on Windows for updating the 
MONQ
 property value.
Root User Authorization for MQI Calls
The Message Queue Interface (MQI) calls are used to access QMs and its related components of WebSphere MQ installation. Any user of the 
mqm 
user group has rights to execute these MQI calls. However, the probe has 
root 
user rights in the Linux, Solaris, and AIX
 
environments. This 
root 
user is not added to the 
mqm 
user group, by default. Therefore, the probe requires the 
root 
user to be added in the 
mqm 
user group, for monitoring WebSphere MQ.
If it is not possible to add the 
root
 user in your environment due to security concerns, you can use an alternative option. This option uses the 
setmqauth
 command to authorize the root user to execute the MQI calls for each QM.
The websphere_mq probe is shipped with a script file, 
setmqprobe_auth.sh
, which uses the 
setmqauth 
command to authorize the 
root 
user to execute the MQI calls. This option does not require adding 
root
 user to the 
mqm
 user group.
 
Follow these steps: 
 
  1. Open the Linux, Solaris, or AIX terminal.
  2. Go to the probe installation directory. The default location is 
    /opt/nimsoft/probes/application/websphere_mq
    .
  3. Set the execution rights for the script by executing the 
    chmod +x setmqprobe_auth.sh
     command.
  4. Log in as 
    mqm
     user by executing the 
    su - mqm
     command.
    You get logged in as 
    mqm
     user and moved to the mqm home directory.
  5. Go to the probe installation directory again.
  6. Execute the 
    setmqprobe_auth.sh
     script using the following command:
    ./setmqprobe_auth.sh <
    QM Name> all
     
    <QM Name>:
     identifies the actual QM name, for which you want to authorize the root user for executing the MI calls.
    all:
     discovers all QMs of WebSphere MQ installation and authorize the root user for executing the MQI calls on all QMs.
     You can use only one of the given parameters and without brackets. Recommendation is to use the 
    all
     parameter when probe is deployed for the first time and later the 
    QM Name
    .
    The script prompts you to provide the WebSphere MQ installation path where the 
    bin
     folder exists.
  7. Define the path and press 
    Enter
    .
    The script uses the default path 
    /opt/mqm/bin
    .
    The probe reads WebSphere MQ configuration and updates the 
    root 
    user access for given QMs. The probe is now ready to fetch the monitoring data of WebSphere MQ.
     If a QM is not activated the script throws the
     "AMQ7028: The queue manager is not available for use"
     error. You can restart QM and re-execute the script. Similarly, run the script again for newly discovered QMs.
Start Monitoring
After deploying the probe for the first-time it displays only the websphere_mq node in the navigation pane. The probe requires initial configuration to discover WebSphere MQ installation and to start monitoring.
 
Follow these steps:
 
  1. Click the websphere_mq node.
  2. Configure the following fields of the 
    WebSphere MQ Auto Configuration
     section:
    • Auto Discovery Interval (minutes)
    • Default Interval (seconds)
    • Activate All QMs
    • Channel Status Coding Scheme
  3. Configure the 
    WebSphere MQ Installation Path
     field of the 
    WebSphere MQ Configuration
     section for connecting and querying WebSphere MQ.
     Refer the 
    websphere_mq Node
     in the v2.0 websphere_mq AC GUI Reference article for field descriptions.
  4. Select the 
    Verify Path
     option from the 
    Actions
     drop-down list of the 
    WebSphere MQ Configuration
     section.
    The probe displays a success message after connecting to WebSphere MQ, else an error message is displayed.
  5. Click 
    Save
    .
    The probe saves the updated configuration, queries WebSphere MQ, and loads WebSphere MQ details on the probe GUI. 
  6. (Optional) If the process takes some time, the PPM-023 error is displayed stating that the probe configuration cannot be loaded.
  7. (Optional) Click 
    Retry 
    on the error dialog until WebSphere MQ details are displayed on the probe GUI.
    The list of all QMs is displayed under the 
    QueueManager 
    and 
    ClusterQueueManager 
    nodes in the navigation pane of the probe GUI. The queues, channels, topics, and subscriptions of the QM are displayed after one measurement interval on the GUI.
Activate QoS Data for Monitors
After loading WebSphere MQ details on the probe GUI, you can activate QoS data for various monitors of QM, channels, or queues. The QoS data helps you understand the trend for the specific monitor. The process of activating QoS is identical for QM, channels, queues, subscriptions, and topics.
 
Follow these steps:
 
  1. Navigate to the appropriate 
    queue manager name
     node in the navigation pane.
    The list of available monitors is displayed on the probe GUI.
  2. Select the appropriate monitor from the 
    Monitors
     section of the probe GUI.
  3. Select the 
    Publish Data
     check box to generate QoS data for the required monitor.
  4. Click 
    Save
    .
    The probe saves the updated configuration and generates QoS data for the configured monitor of the QM.
     Avoid saving the configuration frequently as the probe takes considerable time to save and reload the configuration. CA recommends to configure all necessary monitors and then save the configuration.
Stop Receiving Alarms for Deleted Components
Use this procedure to stop getting alerts for any WebSphere MQ component you delete. For example, you are monitoring a local queue, which is deleted from the queue manager before deactivating its monitoring. The probe is unable to query the queue details and generates false alerts because the queue is deleted from the WebSphere MQ configuration. The probe also does not display the queue in the navigation pane.
Modify the detach configuration parameter of the probe to stop receiving false alerts.
 
Follow these steps: 
 
  1. Open the 
    Raw Configure
     GUI of the probe.
  2. Add the 
    show_detached_configuration
     key under the 
    setup
     section and set the key value to 
    yes
    .
  3. Click 
    Apply
     to close the
     Raw Configure
     GUI for restarting the probe and applying changes.
    The navigation pane of the probe GUI shows a new node 
    Detached Configuration
    . This node contains the components which are deleted from WebSphere MQ but still selected for monitoring in the probe.
  4. Click the 
    Options
     icon next to the component name you want to stop receiving alerts and select 
    Delete
    .
  5. Click 
    Save
    .
The probe stops sending false alerts for the deleted components.
Manage System Channels Monitoring
IBM WebSphere MQ consists of ten system channels, which define the WebSphere MQ channel schema for transferring messages between applications. The default configuration of the probe lets you monitor only three system channels out of 10, which are as follows:
  • SYSTEM.AUTO.RECEIVER*
  • SYSTEM.AUTO.SVRCONN*
  • SYSTEM.DEF.CLUSRCVR
  • SYSTEM.DEF.CLUSSDR
  • SYSTEM.DEF.RECEIVER
  • SYSTEM.DEF.REQUESTER
  • SYSTEM.DEF.SENDER
  • SYSTEM.DEF.SERVER
  • SYSTEM.DEF.SVRCONN*
  • SYSTEM.DEF.CLNTCONN
 The channel names marked with an asterisk (*) are available for monitoring, by default. The other channels are unmonitored, as they do not provide any valid monitoring data.
You can manage (add or remove) your system channels list as required for your WebSphere MQ monitoring:
 
Follow these steps:
 
  1. Open the 
    Raw Configure
     GUI of the probe.
  2. Go to the 
    disabledSystemChannelList
     key under the 
    setup
     section.
  3. Edit the key value by providing the system channel names in a comma-separated format. For example, use 
    Channel1,Channel2
     to exclude 
    Channel1
     and 
    Channel2 
    monitoring.
  4. Click 
    Apply
    .
    The 
    Raw Configure
     GUI closes and the probe restarts for applying the changes.
The system channels, which are configured in the 
disabledSystemChannelList 
key are excluded from the probe GUI.
Monitor Multi-Instance WebSphere MQ
IBM WebSphere MQ lets you run more than one instance of Queue Managers in high availability (HA) mode. The HA mode ensures uninterrupted messaging between applications during hardware or software failures with minimum downtime. As an application administrator, you can monitor the HA status of QM when configured with WebSphere MQ multi-instance QMs.
 
Follow these steps:
 
  1. Install the websphere_mq probe on all the systems where WebSphere MQ is running.
  2. Complete the preconfiguration requirements of the probe.
  3. Configure 
    General Properties
     and the 
    WebSphere MQ Installation path
     to load WebSphere MQ installation details on the probe GUI.
  4. Navigate to the appropriate 
    queue manager name
     node.
     The 
    queue manager name
     node represents the actual QM name, which is visible in navigation pane of the probe GUI.
  5. Select the 
    Multi-Instance QM Status
     monitor from the 
    Monitors
     section.
  6. Select the 
    Publish Data
     option to generate QoS for the monitor and click 
    Save
    .
     Repeat steps 2-6 on all instances of the probe.
    After configuring the 
    Multi-Instance QM Status
     monitor for the QMs, you can observe value of the monitor, which returns one of following values:
    • 0: QM is working in high availability mode and currently is in 
      active
       state.
    • 1: QM is working in high availability mode and currently is in 
      standby
       state. You cannot activate QoS on channels, queues, subscriptions, and topics when the QM is not in active state.
    • 2: QM is not working in high availability mode and the state is always 
      standalone
      .
If the 
active
 QM goes down, it appears in the 
Detached Configuration
 node on the probe GUI. Further, the 
Multi-Instance QM Status
 monitor value changes from 
0
 to 
1
.
 The probe does not monitor those Queue Manager clusters which are configured with any third-party high availability manager, for example, HACMP and MSCS.