ZenPacks

IBM WebSphere MQ Components ZenPack

This Monitoring Zenpack provides monitoring of MQ Managers, Channels, and Queues for IBM Websphere MQ.

Support

This ZenPack is developed by the Zenoss user community and supported via our online forums. Zenoss, Inc. does not provide direct support for this ZenPack.

Releases

Version 1.0- Download
Compatible with Zenoss Core 3.2.x, Zenoss Resource Manager 4.1.x
Version 1.1- Download
Released on 2012/04/02
Compatible with Zenoss Core 3.2.x
Version 2.0- Download
Summary of changes: ConstructionKit support (3.x, 4.x compat), other minor revisions
Released on 2013/04/02
Requires ConstructionKit ZenPack
Compatible with Zenoss Core 3.2.x, Zenoss Core 4.2.x
Version 2.1
Summary of changes: trying to fix auto-build issues
Released on 2013/05/15
Requires ConstructionKit ZenPack
Compatible with Zenoss Core 3.2.x, Zenoss Core 4.2.x
Version 2.2- Download
Summary of changes: updated to support ConstructionKit 2.0, rewrote data parser and changed modeler plugins to multiplatform
Released on 2013/11/05
Requires ConstructionKit ZenPack
Compatible with Zenoss Core 4.2.x

Background

This Monitoring Zenpack provides monitoring of MQ Managers, Channels, and Queues for IBM Websphere MQ.

   No agent is needed on the remote server.
   Support for Windows and Unix-based platforms
   Provides component-level modeling of the IBM MQ application components.

This ZenPack was inspired by the "IBM Websphere MQ ZenPack", and I'm grateful to its author for sharing some of his expertise regarding MQ.

I have been using a shell script to monitor specific MQ Queues on Windows/Unix servers for a couple of years. The good thing about the script is that it requires minimal support to run against Windows and Unix servers. The bad part is that all of the MQ-specific paramters (Manager, Queue) have to be supplied to it. It is also a pain to use to monitor multiple queues on a single machine, as new command definitions have to be made on a locally bound template that differ only in the command line options. A component-based template provides a much better solution, while the modelling scripts remove the need to keep track of the needed parameters.

Components:

The ZenPack has the following Device Class(es)

   /Server/Linux/MQ, /Server/Windows/MQ Device Classes
       MQManager Template provides:
           Data Sources
               mgr-status-nix (Command)
               mgr-status-win (Command)
           Thresholds
               Manager Status (Min/Max)
       MQQueue Template provides:
           Data Sources
               queue-status-nix (Command)
               queue-status-win (Command)
           Thresholds
               Queue Depth (Min/Max)
       MQChannel Template provides:
           Data Sources
               channel-status-nix (Command)
               channel-status-win (Command)
   ZenModeler plugins:
       MqManagerMap
       MqQueueMap
       MqChannelMap
       Common (shared class--do not use as a plugin)
   Event Class:
       /App/MQ

Installation:

After installing this Zenpack as usual, ensure that the authentication zProperties are set for Windows and Unix-based servers respectively.

SSH requires username/password, assumes mqm is the MQ user.

WINEXE on later Windows versions (2003(?) and up) may fail with an error similar to "problem installing winexesvc". This can be corrected by running the following commands from the Command Prompt (on the Windows server):

         sc create winexesvc binPath= WINEXESVC.EXE start= auto DisplayName=

winexesvc

         sc description winexesvc "Remote command provider for Zenoss

monitoring"

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.community.zenIbmMQ-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone git://github.com/j053ph4/ZenPacks.community.zenIbmMQ.git
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.community.zenIbmMQ
  4. Finally, restart these serivices:
    $ zenoss restart

Community

This ZenPack is developed and supported by the Zenoss User Community. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Community ZenPacks.

randomness