IBM Tivoli Composite Application Agent for J2EE, Version 7.1.1

Configure Monitoring Agent settings

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 can change the port that is used for communication between the Data Collector and the monitoring agent (this communication is on the local host); the default port is 63336. You can 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 settings 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, perform the following procedure:
  1. Enter the Agent Configuration window. After installation of the Agent on Windows systems, this window opens automatically. Otherwise, see Entering the Agent Configuration window.
  2. Select Configure Tivoli Enterprise Monitoring Agent (TEMA) and click Next.
  3. In the Agent Configuration page you can set an alternative Node ID for identifying the agent. This ID, also known as an alias, is the identifier that will determine how the agent will be displayed in the Tivoli Enterprise Portal navigation tree. The default is 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. Click Next.
    Attention: Valid characters for the node ID include A-z, a-z, 0-9, underbar (_), dash (-), and period (.); do not use other characters.
  4. The monitoring agent is successfully configured. Click Home to return to the Agent Configuration window, or click OK to complete the configuration process.
  5. On Linux and Unix systems, the Agent advanced configuration window is displayed; see Configure the monitoring agent connection to the monitoring server for instructions about using this window.


Feedback