Is it necessary to start the M6-WMQ Publish-Subscribe Server if you want to distribute events to different system management services?
What is the best configuration for this service?
When coupled with M6-WMQ Publish-Subscribe Server, AutoPilot M6-WMQ will provide fault tolerance of the network's systems management infrastructure. M6-WMQ Publish-Subscribe Server is a server process that distributes WebSphere MQ (MQSeries) and application events to multiple subscribers. These subscribers can include:
- Various systems management products
- User applications
Monitoring the dead letter queue (DLQ) is one of the major features of M6-WMQ Publish-Subscribe Server . When messages arrive on the DLQ, M6-WMQ Publish-Subscribe Server generates events that are compliant with IBM's Programmable Command Format (PCF). In this way, M6-WMQ Publish-Subscribe Server DLQ monitoring capabilities add improved management functionality in an area critical to MQSeries.
If NASTEL.PUBSUB.EVENT.QUEUE is defined, ensure NSQPUB is running.
For nsqpub to work properly, the SYSTEM.ADMIN.*****.EVENT queue must be aliased to NASTEL.PUBSUB.EVENT.QUEUE, and that local queue must exist.
If it is defined but publisher is not meant to be running:
Re-alias all SYSTEM.ADMIN.XXX.EVENT queues to NASTEL.EVENT.QUEUE
Unmanage and manage the system.
If not defined, make sure SYSTEM.ADMIN.XXX.EVENT queues point to NASTEL.EVENT.QUEUE.