Chat now with support
Chat with Support

Foglight for IBM WebSphere MQ 5.5.5.9 - Installation Guide

Queue manager events

1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
3
Locate the Event Settings properties.
4
Select the Queue Manager Events option: True or False.
Select True if you want the MQ Agent to monitor queue manager events. Otherwise, select False.
5
Select the Consume Queue Manager Event Message option: True or False.
NOTE: This agent property requires a get permission on this queue. This permission is set on the IBM WebSphere MQ Server.
Select True if you want the MQ Agent to remove events from the SYSTEM.ADMIN.QMGR.EVENT queue as they are read.
Select False if you want the MQ Agent to retain queue manager events in the SYSTEM.ADMIN.QMGR.EVENT queue as they are read.
When this option is set to False, the MQ Agent does not consume any events in event queues. With no other means to remove event messages from the event queues, the event queues become full, and the corresponding event collection does not work.
a
Click the Clone button to the right of Queue Manager Event List.
a
Click the Edit button to the right of Queue Manager Event List.
MQGET calls are currently inhibited for the queue.
MQPUT and MQPUT1 calls are currently inhibited for the queue.
The ObjectQMgrName field specifies the local definition of a remote queue (in order to specify a queue-manager alias). In that local definition, the RemoteQMgrName attribute is the name of the local queue manager. However, the ObjectName field specifies the name of a model queue on the local queue manager.
A local definition of a remote queue (or an alias to one) was specified, but the RemoteQName attribute in the remote queue definition is blank, or the ObjectQMgrName field in the object descriptor is not blank and does not contain the name of the local queue manager, but the ObjectName field is blank.
The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but either XmitQName is not blank and specifies a remote queue, or it is blank and RemoteQMgrName specifies a remote queue.
ObjectQMgrName specifies the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION.
ObjectName or ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue and either XmitQName is not blank but specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION, or XmitQName is blank and RemoteQMgrName specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION.
The BaseObjectName in the specified alias queue is not recognized as a queue or topic name.
The ObjectName in the object descriptor is not recognized as the specified object type.
Placing a message on a remote queue failed due to an unresolved queue name. The XmitQName attribute of the definition is not blank and not the name of a locally-defined queue.
b
In the dialog box, click Add Row to add an entry.
Queue Manager Event: Type the name of the queue manager event.
Monitor: Select the check box to enable the monitoring of this event, or clear the check box to disable monitoring.
c
Click Save Changes in the dialog box. The dialog box closes.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .

Statistics events properties

1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
3
Locate the Statistics Events property.
4
Select the Consume Statistics Event Message option: True or False.
NOTE: This agent property requires a get permission on this queue. This permission is set on the IBM WebSphere MQ Server.
Select True if you want the MQ Agent to remove statistics events from the SYSTEM.ADMIN.STATISTICS.EVENT queue as they are read.
Select False if you want the MQ Agent to retain statistics events in the SYSTEM.ADMIN.STATISTICS.EVENT queue as they are read.
When this option is set to False, the MQ Agent does not consume any statistic messages in event queues. With no other means to remove event messages from the event queues, the event queues become full, and the corresponding event collection does not work.
5
Click Save.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .

Listener monitoring property

Use the Miscellaneous agent properties to set the monitoring of the listeners.
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
3
Locate the Miscellaneous property.
4
Select the Monitor Listeners option: True or False.
Select True to enable the monitoring of the listeners. Otherwise, select False.
5
Click Save.

Advanced (batch) properties

1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
3
Locate the Advanced Settings properties.
4
In the Batch Inquiry Delay Interval (milliseconds) box, type a value for the amount of time the MQ Agent should wait between successive queries of the MQ Server. The default value is 300 milliseconds.
5
In the Batch Inquiry Size (Queues, Channels) box, type a value for the number of objects to query at one time. The default is ten.
6
Click Save.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating