IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Message flow statistics and accounting data

Message flow statistics and accounting data can be collected to record performance and operating details of one or more message flows.

Message flow statistics and accounting data captures dynamic information about the runtime behavior of a message flow. For example, it indicates how many messages are processed and how large those messages are, as well as processor usage and elapsed processing times. The statistical data is collected and recorded in a specified location when an event occurs, such as when a snapshot interval expires or when the integration server that you are collecting information about stops.

You can use the statistics generated for the following purposes:

The broker takes information about statistics and accounting from the operating system. On some operating systems, such as Windows, Linux, and UNIX, rounding can occur because the system calls that are used to determine the processor times are not sufficiently granular. This rounding might affect the accuracy of the data.

The following restrictions apply to data collection:

Collecting message flow accounting and statistics data is optional; by default it is switched off. To use this facility, request it on a message flow or integration server basis. The settings for accounting and statistics data collection are reset to the defaults when an integration server is redeployed. Previous settings for message flows in an integration server are not passed on to the new message flows deployed to that integration server.

You can start and stop data collection by using the mqsichangeflowstats command, the web user interface, or the IBM® Integration Explorer; you do not need to modify the broker or the message flow, or redeploy the message flow, to request statistics collection.

You can activate data collection on both your production and test systems. If you collect the default level of statistics (message flow), the effect on broker performance is minimal. However, collecting more data than the default message flow statistics can generate high volumes of report data that might affect performance slightly.

When you plan data collection, consider the following points:

The following topics contain reference information that you might find helpful when analyzing and tuning the performance of your message flows:

You can find more information about how to use the accounting and statistics facility to monitor the performance of a message flow in this developerWorks® article on WebSphere Message Broker Explorer accounting and statistics.

You can also find information about how to use accounting and statistics data in this developerWorks article on message flow performance.


ac19100_.htm | Last updated Friday, 21 July 2017