Please use v7.3.0 Fix Pack 1 of the broker monitoring agent in OMEGAMON XE for Messaging and ITCAM for Applications to monitor Version 10 of IBM Integration Bus. To get to this level on z/OS, you can apply PTF UA78812, and on distributed platforms, you can install Passport Advantage part number CN6R0EN.
Note that this level of the monitoring agent additionally supports more types of Resource Statistics for the Integration Server (Execution Group) for TCPIP Client Nodes, TCPIP Server Nodes, and Sockets.
The following technote also has information about this fix pack: http://www-01.ibm.com/support/docview.wss?uid=swg24040581
The remainder of this entry is a list of our best practice recommendations for the broker monitoring agent for your convenience:
- Queue manager and queue monitoring can be helpful in many broker environments, in which case it is recommended to use the MQ monitoring agent along side the broker monitoring agent so that you can automatically detect queues getting full, queues with messages sitting on them for too long, channels not running, and other problematic situations. With MQ monitoring agent, there is not much that you must enable externally for recommended monitoring, except that if you are interested in Oldest Message Age and Queue timing (latency) attributes for monitoring your queues, you must turn on Queue Monitoring (MONQ) for queues in your queue manager (at least for the ones that are involved with your broker flows).
- Archive Accounting Statistics will provide the message flow counts and rates of messages, elapsed and CPU timings, sizes of messages, and error counts. Archive Accounting Statistics generally are preferred to using CandleMonitor Node statistics nowadays. They are easier to enable, do not require changes to message flows like CandleMonitor node usage does, and they contain CPU timings.
The following attribute groups provide these statistics at four levels:
Accounting Message Flow Statistics
Accounting Node Statistics
Accounting Terminal Statistics
Accounting Thread Statistics
You enable the data in the broker by using the mqsichangeflowstats command. It is available as a take action command from the WebSphere Message Broker monitoring agent as well. To enable the recommended "archive" accounting statistics across the broker, with all levels of data available, issue the following command:
z/OS: F <broker>,changeflowstats --a=yes -g=yes -j=yes -c=active -n=advanced -t=basic -o=xml
distributed: mqsichangeflowstats <brokername> -a -g -j -c active -n advanced -t basic -o xml
(a) -o xml setting is required for the monitoring agent to get the data. The agent will automatically start receiving the data with no other action required.
(b) It is not recommended to use the "snapshot" (-s option) accounting statistics in production monitoring, except if required for debugging an issue with a particular message flow, because snapshot generally produces too much data. The archive and snapshot data is all exactly the same, just the interval for snapshot record production is very short, so it can impact performance and agent memory requirements.
(c) You can modify the interval for archive accounting statistics by using the mqsichangebroker command (also available as a take action command of the monitoring agent). You will likely want to do this because the default is 60 minutes. This is the command to issue to specify a 5 minute interval (minimum is 1 minute):
z/OS: F <broker>,changebroker -v=5
distributed: mqsichangebroker <brokername> -v 5
JVM Resource Statistics
JDBC Connection Pools Resource Statistics
ODBC Resource Statistics
File Resource Statistics
Parsers Resource Statistics
SOAP Input Resource Statistics
TCPIP Client Nodes Resource Statistics
TCPIP Server Nodes Resource Statistics
Sockets Resource Statistics
You enable the data in the broker with the mqsichangeresourcestats command. The command to enable for all execution groups in the broker is as follows:
z/OS: Run command "mqsichangeresourcestats <brokername> -c active" by customizing and submitting BIPCHRS
distributed: mqsichangeresourcestats <brokername> -c active
If you want to enable only for a particular execution group, add "-e <egname>" to the command.
Message Processing Nodes
Processing Node Attributes
Message Flow Node Topology
For this data, set the following parameter to YES in your agent parameter XML file:
The reason why this data is not enabled by default is that the amount of this data can be quite high, depending on the number of message flows, nodes, and attributes in your broker, and collecting this data can use more resources than you desire for your agent. If having the Message Flow Topology and node detail data available in the TEP is interesting to you, it is recommended that you try enabling the data, and then check to make sure your agent still performs as desired.
The attribute groups most recommended for historical collection are given here. However, most attribute groups are eligible for enabling for historical collection and data warehousing. Once in the TDW, a Cognos data model is provided for Tivoli Common Reporting with some sample reports.
Accounting Message Flow Statistics
Execution Group Status
Message Flow Status (if you want the status of each message flow recorded historically)
Broker Status Events (if you are interested in configuration events being recorded historically to tell when the broker was deployed with a change)
All attribute groups that begin with the words "Monitor Node" will not have data if the CandleMonitor node is not configured and deployed in your message flows. As mentioned above, Accounting Statistics are now usually preferred because of easier enablement and CPU timings being available. The CandleMonitor node dates back to broker releases in which there were no other statistics available.