Prerequisites
Before you can use the CandleMonitor node to monitor message flows, perform the following tasks:
- Make the CandleMonitor node available
in the broker environment.
- For broker environment on distributed systems, see Making the CandleMonitor node available in broker environments.
- For broker environment on z/OS® systems, see IBM Tivoli OMEGAMON XE for Messaging for z/OS: Planning and Configuration Guide, SC32-1830.
- Make the CandleMonitor node available in the Message Brokers Toolkit, as described in Making the CandleMonitor node available in Message Brokers Toolkit.
Exception: If the broker to which the
CandleMonitor node is deployed runs on AIX® systems,
enable the shared memory on AIX systems
before the node is deployed to the broker. Because the WebSphere® Message
Broker is
a 32-bit application that is memory intensive, the broker cannot attach
to more than 11 shared memory segments. When it runs short of process
address space, the broker cannot attach to the queue manager-related
shared memory resources.
To enable the shared memory on AIX systems, do the following steps:
- Stop the broker by running the following command, where broker is
the name of your broker:
mqsistop broker - Run the following command to ensure that the broker is running
in an environment with the extended memory variable exported:
export EXTSHM=ON - Restart the broker by running the following command, where broker is
the name of your broker:
mqsistart broker - On the DB2® server, ensure that the shared memory support is enabled.