98 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1
– If your site does not have a default queue manager specified, or if you are
configuring this agent to monitor a queue manager other than the default,
click Yes. A Notepad session opens. Supply the WebSphere MQ queue
manager name in the MANAGER NAME() and MGRNAME() parameters
of the .cfg file, then save and close the Notepad session. Click Yes at the
next prompt to continue.
7. You are returned to the Manage Candle Services window. This completes the
initial configuration, and the agent is ready to start.
4.2 WebSphere MQ Configuration Agent configuration
After the WebSphere Configuration Agent has been installed, it needs to be
configured. This involves configuring Agent-to-CMS communication. Do the
following steps to accomplish this configuration:
1. From Manage Candle Services, right-click WebSphere MQ Configuration
Agent and select Advanced → Configured Advanced (see Figure 4-30).
Figure 4-30 WebSphere MQ Configuration Agent
Chapter 4. Installation and configuration of WebSphere MQ Agents 99
2. Select TCP/IP for Protocol1. Click OK to continue (Figure 4-31).
Figure 4-31 WebSphere MQ Configuration Agent-to-CMS communication
3. Enter the host name or IP address of the machine where the primary Hub
CMS resides. Enter the CMS listening port for the agent. IBM recommends
you use port number 1918; however if you must change it, enter the new port
number (IBM recommends numbers 1025-65535). Click OK (Figure 4-32 on
Note: The agent we used will not communicate with the CMS across a
Chapter 4. Installation and configuration of WebSphere MQ Agents 101
Figure 4-33 Starting WebSphere MQ Configuration Agent
102 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1