How to enable WebSphere MQ events

Process Events enable the processing of WebSphere MQ events of various types. These events correspond to events WebSphere MQ places on the SYSTEM.ADMIN.QMGR.EVENT, SYSTEM.ADMIN.CHANNEL.EVENT, SYSTEM.ADMIN.CONFIG.EVENT, and SYSTEM.ADMIN.LOGGER.EVENT queues. For events to be generated and placed onto these system queues, the respective events must be enabled for the queue manager for which events are required. This can be done from the Events tab of the Properties view for the queue manager.

In some instances, WebSphere MQ puts multiple event types onto an event queue. The supported event types are mapped to the system event queues as shown below:

  • SYSTEM.ADMIN.QMGR.EVENT receives Authority Events (not available on z/OS), Inhibit Events, Local Events, Remote Events, and Start/Stop Events (not available on z/OS for initial queue manager start)
  • SYSTEM.ADMIN.CHANNEL.EVENT receives Channel Events, SSL Events and Bridge Events (available on z/OS only)
  • SYSTEM.ADMIN.CONFIG.EVENT receives Configuration Events
  • SYSTEM.ADMIN.LOGGER.EVENT receives Logger Events (not available on z/OS)

Event messages on the SYSTEM.ADMIN.COMMAND.EVENT, SYSTEM.ADMIN.PERFM.EVENT, and SYSTEM.ADMIN.PUBSUB.EVENT event queues are not processed.

You can use agentpref to enable events:

agentpref --host <AgentHostname) --port <QpeaPort> --set "WebSphere MQ Monitor" ProcessChannelMQEvents true
agentpref --host <AgentHostname) --port <QpeaPort> --set "WebSphere MQ Monitor" ProcessConfigMQEvents true
agentpref --host <AgentHostname) --port <QpeaPort> --set "WebSphere MQ Monitor" ProcessLoggerMQEvents true
agentpref --host <AgentHostname) --port <QpeaPort> --set "WebSphere MQ Monitor" ProcessQMgrMQEvents true

where:

--host is the hostname of the agent machine where QPEA is running (required unless specified in an eaapi.ini file or agent on the same machine).
--port is the port number for QPEA (optional, defaults to 2612 or as specified in an eaapi.ini file).

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Cics Team

    This page was useful, in as far as I can see that Channel Events are being processed by Middleware Monitor.

    I am hoping to be able to see the detail from the Channel Events (Particularly around the area of Channel Authentication where Warn has been specified so that we can identify usage and potential issues before closing up the gaps) It would be helpful if there is further documentation around processing Channel Events from TMM for this to point in that direction.

    Jul 11, 2018 08:17
    1. Ashley Pearson

      Thank you for your feedback on the documentation. 

      Detail from the Channel Events can be found in the WMQ_Agents_Standard_EventTarget (BEM, EMail, LogToFile) Agent Policy. Specifically, the relevant Object Policy is WMQ_QMgr_ChannelEventsEnabled_EventTarget which contains the WMQ_QMgr_AddEventTemplate_ChannelEvent_BlockedWarning_EventTarget Policy Action which in turn references the WMQ_ChannelEvent_ChannelBlockedWarning_EventTarget Event Template.

      Jul 12, 2018 09:53