Technical Blog Post
Abstract
MQ Monitoring agent: Agent-side configuration
Body
Configuration of a working MQ agent to collect statistics from WebSphere MQ is to be done on both sides: MQ agent and WebSphere MQ itself.
This blog entry will deal with the MQ agent-side configuration.
A separate blog entry has been created for the configuration needed on the WebSphere MQ side
/support/pages/node/1084731.
From the MQ agent side you need to edit the following files/member:
Unix/Linux:
<ITMHome>/config/mq.cfg (default instance)
<ITMHome>/config/<hostname>_mq_<instname>.cfg
Windows:
<ITMHome>\TMAITM6\mq_<instname>.cfg
zOS:
RKANCMD(KMQUSER) - RKANCMD(KMQSTART)
In the proper file you need to be sure to have coded the STATISTICS keyword in the needed SET QUEUE statement:
SET GROUP NAME (GROUP1) -
DEFAULT(YES) -
RETAINHIST(120) -
COMMAND (YES) -
MSGACCESS(DESC) -
EVENTS(REMOVE) -
ACCOUNTINGINFO(REMOVE) -
STATISTICSINFO(REMOVE)
SET MANAGER NAME(qmgr_name)
SET QUEUE NAME(*) MGRNAME(qmgr_name) QDEFTYPE(PREDEFINED) STATISTICS(YES)
SET CHANNEL NAME(*) MGRNAME(qmgr_name)
PERFORM STARTMON SAMPINT(30) HISTORY(YES)
Notes:
| EVENTS(REMOVE) | Agent reads messages from event queues and remove them. ‘Browse’ is another option. |
| SET MANAGER NAME | QMGR to be monitored. Without it, the agent will monitor the QMGR that is defined as Default in WMQ. If there is no Default QMGR, the agent will not start. |
| STATISTICS(YES) | Many workspaces are empty if STATISTICS is not set to YES. Default is NO. Also some settings on WMQ side are needed. |
| SAMPINT | Agent goes and gets WMQ data every SAMPINT and put data into an internal memory buffer |
| HISTORY | Used to enable historical data collection. TEP settings are not enough for MQ agent. |
UID
ibm11084725