IBM WebSphere Message Broker Monitoring 
Overview
WebSphere Message Broker is an enterprise service bus providing connectivity and universal data transformation for service-oriented architecture (SOA) and non-SOA environments. It performs comprehensive range of operations on data, including routing, filtering, enrichment, multicast for publish-subscribe, sequencing, and aggregation.
Monitored Parameters
Applications Manager monitors availability and performance of the Message Broker, execution group and message flow and memory usage of the execution group. It supports IBM WebSphere Message Broker versions upto 10.x. You can also collect Message Flow Accounting and Resource Statistics and configure thresholds to the attributes monitored by the server based on these details. The monitoring details of IBM WebSphere Message Broker are represented graphically that helps to understand the parameters with ease.
- Availability tab, gives the Availability history for the past 24 hours or 30 days.
- Performance tab gives the Health Status and events for the past 24 hours or 30 days.
- List view enables you to perform bulk admin configurations.
The WebSphere Message Broker attributes monitored are classified under the following tabs in Applications Manager:
Performance Overview
| Parameter | Description |
|---|---|
| Graphical view of Execution Group status |
|
| Graphical view of Message Flow status |
|
Execution Group
| Parameter | Description |
|---|---|
| Name | Name of the Execution Group |
| Used Memory In MB | The amount of memory that is currently in use. |
| Free Memory In MB | The amount of memory that is currently free.Its value might be undefined. |
| Committed Memory In MB | The amount of memory that is allocated to the JVM by the operating system. |
| Max Memory In MB | The maximum amount of memory that can be used for memory management. Its value might be undefined. |
| Garbage Collection per Min | The total number of garbage collections that have occurred per minute for this instance of the JVM |
| Garbage Collection Time | The garbage collection elapsed time in seconds for this instance of the JVM |
| Status | Status of the Execution Group |
Message Flow
| Parameter | Description |
|---|---|
| Name | Name of the Message Flow |
| Execution Group Name | Name of the Execution Group |
| Messages Processed per Min | Total number of messages that are processed |
| MQ Errors per Min | Total Number of MQGET errors |
| Total Commits per Min | Number of transaction commits that occur when processing a message |
| Total Back outs per Min | Number of transaction backouts that occur when processing a message. |
| Timeouts per Min | Number of transaction timeouts that occur when processing a message |
| Processing Time in milliseconds | CPU time in milliseconds spent processing an input message |
| Status | Status of the message flow |
You can also compare the values between the various attributes.
Message Flow Accounting and Statistics
Message flow accounting and statistics data is the information that can be collected by a broker to record performance and operating details of message flow execution. Use the below commands to trigger statistics and reports for the message flows.
- mqsichangeflowstats <BROKER> -a -e <ExecutionGroup> -j -c active -o xml -n basic(enable statistics for particular execution group)
[OR]
mqsichangeflowstats <BROKER> -a -g -j -c active -o xml -n basic(enable statistics for all execution group) - mqsichangebroker <BROKER> -v <PollInterval> (Poll Interval of the monitor in minutes)
Message Broker Resource Statistics
Resource statistics are collected by a broker to record performance and operating details of resources that are used by execution groups. Use the below command to trigger resource statistics
- mqsichangeresourcestats <BROKER> -c active -e <ExecutionGroup>(enable statistics for particular execution group)
- mqsichangeresourcestats <BROKER> -c active(enable statistics for all execution group)
- The broker should be restarted after executing the commands.
- Enabling the above statistics will moderately affect performance. So it is recommended that you enable these statistics only for the required executions groups.
