Technical Blog Post
MQ Monitoring agent: WebSphere MQ side configuration
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 WebSphere MQ side configuration.
A separate blog entry has been created for the configuration needed on the MQ agent side:
First of all it is useful to know something more on WebSphere MQ itself.
Here are some control commands. Among them we need to keep in mind the runmqsc command which will be used in our configuration work:
crtmqm – To create a queue manager on WMQ.
strmqm / endmqm – To start/stop a queue manager
dspmq – To show the status of the defined queue managers
dspmqver – To display WebSphere MQ version and build information.
runmqsc – Run WebSphere MQ commands on a queue manager.
RUNMQSC allows to run commands against a queue manager.
Here is a list of few useful commands:
dis qmgr – Display properties of a specified queue manager
dis ql – Display properties of a specified local queue
alter qmgr/ql/channel – Change a specified property
Now for the configuration that we are working on, we need to enable generation of statistics from WebSphere MQ side so that MQ agent will be able to gather the needed statistics and report them to TEP.
To do this configuration we need to check what are the current values for the queue manager and then alter the queue manager itself to enable statistics generation.
> DIS QMGR
|ACCTMQI/STATMQI||Enable creation of MQI statistics (put/get count etc)|
|*EV||Enable creation of MQ events in the SYSTEM.*.*.EVENT queues|
|MONQ/MONCHL||Start Queue/Channel monitoring|
|STATQ/STATCHL||Enable creation of Queue/Channel statistics (eg. numbers of the opened queues, open queue handles, etc)|
Subscribe and follow us for all the latest information directly on your social feeds:
|Academy Twitter :||https://goo.gl/AhR8CL|