IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Configure monitoring agent settings- Windows - WAS agent
If the IBM Tivoli Monitoring infrastructure is used, you must configure Monitoring Agent settings before configuring the data collector to monitor any application server instances. Do not perform this configuration in a deep dive diagnostics only installation, where IBM Tivoli Monitoring is not used.
You may change the port used for communication between the data collector and the monitoring agent (this communication is on the local host); the default port is 63335. You may also set an alternate node name that determines how the agent will be displayed in the Tivoli Enterprise Portal navigation tree.
While you can change these at a later time, it is normally most convenient to set them when initially configuring the communication. In this case no manual changes to configuration files is required to change the port number, and no customization of the Tivoli Enterprise Portal view could have been performed by any user. So, if you need to make such changes, make them at installation time if possible.
To configure Monitoring Agent settings:
- Enter the Agent Configuration window. After installation of the agent, this window opens automatically. Otherwise, see Enter the Agent Configuration window.
Figure 1. Configuring Communication to the monitoring agent, window 1
- Select Configure Tivoli Enterprise Monitoring Agent (TEMA) and click Next.
- In the agent Configuration page you can set an alternative Node ID for identifying the agent. This is the identifier that will determine how the agent will be displayed in the Tivoli Enterprise Portal navigation tree. Default Primary, used in conjunction with the host name of the computer where the agent is installed. In the Port field you can specify a TCP socket port that the monitoring agent will use to listen for connection requests from the data collectors. Normally, do not change this value. The port will only be used for local communication on the host (except if you use the monitoring agent to support data collectors on IBM i hosts, see IBM Tivoli Composite Application Manager: Agent for WebSphere Applications data collector Installation Guide for IBM i. Click Next.
Figure 2. Configuring Communication to the monitoring agent, window 2
Enter the Node ID if necessary; change the port number if necessary. Click Next.
Valid characters for the node ID include A-z, a-z, 0-9, underbar (_), dash (-), and period (.); do not use other characters.
- In the next step, you can choose to create a response file to save your configuration settings. You can use the response file to perform a silent configuration with the same parameters.
Figure 3. Configuring Communication to the monitoring agent, window 3
To create a response file, check the box Save your settings in a response file and click Browse to select the file location, then click Next. Otherwise, leave the box unchecked and click Next.
- The monitoring agent is successfully configured.
Figure 4. Configuring Communication to the monitoring agent, window 4
Click Home to return to the Agent Configuration window, or click OK to complete the configuration process.
Parent topic:
Configure ITCAM Agent for WebSphere Applications on Windows