Configuring & Troubleshooting the IIB10 Field Pack.

Document ID : KB000009836
Last Modified Date : 14/02/2018
Show Technical Document Details

  The IIB10 Field pack was developed to monitor IBM Broker(IIB) version 10 and later. It has 2 components: 

   1. To monitor MQ Queue manager

   2. To monitor Message flows running in IIB (Broker)


  The MQ monitoring part is same as the equivalent component in CA APM Powerpack for MQ. The only changes are in the MQ Broker component.


All APM 10.x releases with IIB version 10 and later.

  The following are frequent issues faced by customers and how to resolve them. Refer to the Product documentation as well as this Knowledge Doc to resolve field pack issues.


    1. Configuring the Monitoring Environment: Queue Manager (QM) + Broker

    For IIB version 10, the QM dependency is removed. i.e. one can install and run the Broker without installing QM. It is recommended to install and integrate QM with Broker, because many features in Broker require QM.

    Monitoring QM is same as existing MQ Extension.

    Monitoring message flows in Broker require some configuration. Follow the steps below to do this: 


  1. Broker monitoring requires QM as well. APM subscribes to message flow stats using JMS Queues.

     a. Identify the Queue Manager where you have to define JMS queues

     b. Find the file MBMonitorJMSQueues.mqsc in the IIB10Fieldpack/properties directory. The file contains a series of MQSC commands

     c. Execute the following command on your Message Broker host, where queueMgr_name is the name of the Queue Manager identified in an earlier step.

     runmqsc queueMgr_name < MBMonitorJMSQueues.mqsc


     d. Verify whether the JMS queues are created or not in QM.


     e. To confirm whether allmqi permission is applied on the Queue Manager of the JMS QM: 

       dspmqaut -m <JMS_QMGR> -t qmgr -p <user>@<domain>


     f. To confirm whether allmqi permission is applied to all JMS pub sub queues (ten in all) defined in the JMS Queue Manager:

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.ADMIN.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.D.SUBSCRIBER.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.MODEL.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.ND.SUBSCRIBER.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.ND.SUBSCRIBER.WILY.MBBROKER -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.ND.SUBSCRIBER.WILY.MBMSGFLOW -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.PS.STATUS.QUEUE -p <user>@<domain>

       dspmqaut -m <JMS_QMGR> -t q -n SYSTEM.JMS.REPORT.QUEUE -p <user>@<domain>


  2. Enable flow stats in xml output format. Run the below command to enable for all flows

  mqsichangeflowstats Broker_Name -s -g -j -c active -o xml -n basic


  3. To check whether flows stats enabled or not, run the below command

   mqsireportflowstats Broker_Name -s -g -j


  4. To control the update interval for status metrics configure the below property in the file


    The default value for this property is 1800 seconds. You can reduce the interval, but it will have some performance impact if there are too many message flows running.


 2. Common problems

     The following are common issues using the field pack:

    1. Seeing security exceptions when the user is in the mqm group. To remedy, run the following

       runmqsc QMGR_NAME


       refresh security

     For more information, refer to this link


  2. Using the incorrect Java libraries: e.g. 32-bit java library on 64-bit server and vice versa.


  3. Not getting metrics for some of the execution groups and message flows. To fix,

     - check if there are any filter properties are configured in


 4. Message flow stats metrics do not update OR running status not updating. If this happens:

     - Make sure you have the Integration node running. 

     - Check the delay time property update interval

     - Use the latest build which has a fix to a similar issue