This scenario describes how you can use the WebSphere MQ Monitoring agent to monitor multiple alias queues that are used by different applications.Background:
The XYZ company uses WebSphere MQ network to enable communication between multiple applications. In their WebSphere MQ environment, there are 150 alias queues pointing at one local queue. They want to know the impact that each alias queue has on the local queue with the WebSphere MQ Monitoring agent. Especially when the local queue is overloaded, they expect to know which of the alias queues causes the overload.
Because no statistical data on alias queues has been generated by WebSphere MQ and all statistical data is for actual local queues, the WebSphere MQ Monitoring agent cannot provide this information directly.
Instead of monitoring alias queues directly, the XYZ company can monitor these queues from an application perspective as long as different alias queues are used by differently identifiable applications. The monitoring is done differently on distributed systems from on z/OS systems.
- On distributed systems, after the application accounting is enabled for the local queue in WebSphere MQ, the monitoring agent will get the queue accounting information and report it. Use the Queue Accounting workspace and attribute group that are provided by WebSphere MQ Monitoring agent to view the statistical data with the breakdown of the queue by the applications that are using it. You can see the number and rate of puts and gets for each application. Although the displayed queue name is the name of local queue, since different applications uses different alias queues, you can detect which one of the alias queues causes overload. You can access the Queue Accounting workspace by right-clicking Application Statistics navigator item in the physical view and clicking Queue Accounting. The Application Statistics workspace and attribute group present the statistical data for each application summarized for all queues that the application is using.
- On z/OS systems, after the application statistics function is enabled in WebSphere MQ Monitoring agent, the monitoring agent can provide detailed statistical information on an application's use of WebSphere MQ resources in Application Statistics workspaces. These workspaces provide various statistics, including the number of puts and gets by an application to all queues that it uses for all transactions/programs. You can use the Application Statistics by Tran/Pgm workspace to get the summarized data for all queues that are used by a specific application. Besides, the Application Queue Statistics table within the Queue Access Statistics by Tran/Pgm workspace shows a row per queue for a specific transaction/program in a specific application. It also contains the same statistics that are summarized at higher levels including the number of message puts and gets. Although the displayed queue name is the local queue name, the data will be with respect to a particular application transaction/program's use of that queue, so you can detect which transaction/program (and thus alias queue) is the cause of overload.
- Use the ACCTQ attribute of the local queue and the queue manager to enable the collection of queue accounting information. For detailed information about proper MQSC command to issue, see the following information:
- For information about the related attribute group and workspace, see the product online help or check out the WebSphere MQ Monitoring agent user's guide from ITCAM for Applications information center
- Enable the collection of application statistics information for the WebSphere MQ Monitoring agent.
- Enable the collection of queue statistics information for the WebSphere MQ Monitoring agent.
- For information about the related attribute group and workspace, see the product online help or check out the agent user's guide from Tivoli OMEGAMON XE for Messaging on z/OS information center