About this blog

Welcome to the Application Performance Management Blog, where you can read the perspectives from APM experts. This Blog provides insights into the Application Performance Management solution, as well as technical details about specific IBM products.

The history files for the ITCAM Message Broker agent can become large very quickly. Warehousing is enabled for history collection, and Warehouse Proxy agent is working fine, but all history files continue to grow. A fast growing history file can fill up file system. Agent needs sufficient disk space to perform trimming of the history files, and when this space is not available, trimming fails, and all history files start growing, making the problem worse. To control the history file size, the history collection settings need to be... [More]

Abstract: Message Broker agent V730 FP1 is not able to connect to IIB 10 Message Broker Problem: It has been reported from several people that the Message Broker agent V730 FP1 is not able to connect to IIB 10 Message Broker even if it's supported at that agent level. It gives errors like: "Failed to operate on java sub-process, phase = writing pipe error = 32" or "KQIA033W (kqiagent.034) KQIAgent has not discovered any brokers to monitor, or that match MonitorBroker name parameters. " Solution: This is due to the fact... [More]

We don't have formal performance figures so all information given below are based on experience of support teams. There are many factors that may affect CPU usage. Generally speaking, it depends on how many EG/MF are deployed in the broker and if message broker agent (KQI) is configured to get detailed data. 1. In kqi.xml, set defaultCollectNodeData or collectNodeData to "YES". It will show all nodes data in the workspace 'broker status'. It might cause CPU or memory issue if you have more than 1000 nodes in one broker. 2.... [More]

It's often a problem for customers to correctly set up historical data collection for Accounting Message Flow Statistics (KQITACMF). Here we will see the 3 simple but important steps to put in place the correct configuration. 1) First of all you need to enable/start historical data collection for Accounting Message Flow Statistics from History Collection Configuration panel on TEP Refer to... [More]

IBM Tivoli Composite Application Manager for SOA vNext Beta is now at Milestone 3 and refreshed drivers are now available for download. New in this Milestone WebSphere Message Broker 8.0.0.0 Support Previous Milestones contained: Monitoring Enhancements for WebSphere DataPower More detailed fault records, to better identify failing transactions. Option to exclude fault data from service operation metrics. New workspaces for DataPower SQL and MQ connection monitoring Performance Enhancements Also featured... [More]

WebSphere Message Broker Monitoring agent is a component of IBM Tivoli OMEGAMON XE for Messaging on z/OS to monitor WebSphere Message Broker. A paper is published on the Wiki that provides a best practice for configuring WebSphere Message Broker Monitoring agent 7.1.0 to monitor WebSphere Message Broker 7.0 on z/OS 1.13 platforms. An example of appropriate parameter configurations is also provided in the paper. The URL of the paper is: Using OMEGAMON XE for Messaging on z/OS V7.1.0 to monitor WebSphere Message Broker V7.0 or later