You must configure the Data Collector for each application
server instance that you need to monitor.
To configure the Data Collector to monitor a server instance, perform
the following procedure:
- Enter the Agent Configuration window. After installation of the
Agent on Windows systems,
if you have selected Launch Manage Tivoli Monitoring Services
for additional configuration options and to start Tivoli Monitoring
services, this window opens automatically. Otherwise,
see Entering the Agent Configuration window.
- Select Configure Application Server for DC Monitoring and
click Next.
- If you want to configure the Data Collector to communicate with
the Managing Server, check the Enable communication to Managing
Server for deep-dive diagnostics box. Then, Click Next.
If you left the box unchecked, go to step 7.
- Enter the fully qualified host name of the
Managing Server. If a split Managing Server installation is used,
this must be the host where the Kernel is located. If the Managing
Server is installed on the same host as the Agent, the address and
port for this Managing Server will be displayed by default, but you
can change them.
After entering the host name, you can also change
the port number on which the Managing Server Kernel is listening.
Then, click Next.
Note: This port number is defined as the
value of the key "PORT_KERNEL_CODEBASE01" in the .ITCAM61_MS_CONTEXT.properties
file located under the Managing Server Home directory. See IBM® Tivoli® Composite Application
Manager for Application Diagnostics Managing Server Installation Guide.
- Set the Managing Server home directory, which
is the destination directory chosen during the installation of the
Managing Server.If the Managing Server is running and the configuration
utility has been able to communicate to it, its home directory is
displayed by default. If the Managing Server is not available at the
time of communication, you need to enter the home directory.
If
the Managing Server home directory is not displayed, input it. Click Next.
- If there are multiple IP address on this
host, select the address that the Data Collector needs to use for
communication with the Managing Server. Also, if you need to change
the ports that the Data Collector uses to accept incoming connections
from the Managing Server (in case of split Managing Server installation,
the Publish Server), select "Specify the RMI Port Number", and enter
the "RMI Port Number" and "Controller RMI Port Number". Make sure
the ports are not being blocked by the firewall or other applications.
The default RMI port Number range is 8200-8299; the Controller RMI
Port Number range is 8300-8399. After making any necessary changes,
click Next.
- You can enable the Transaction Tracking API
function in the following window. Transaction Tracking Application
Programming Interface (TTAPI) enables the integration of ITCAM Agent for J2EE and
ITCAM for Transactions. With TTAPI, the Data Collector can send transaction
information to ITCAM for Transactions; also, if ITCAM for Application Diagnostics Managing
Server is
used, transaction specific information is available in the Visualization
Engine. TTAPI also enables integration of the Data Collector with
the Robotic Response Time component (or T6 agent). To enable TTAPI,
check the Configure Transactions Integration box, and enter
the fully qualified host name or IP address for ITCAM for Transaction
Tracking agent and the port number that the Data Collector uses to
connect to it. Then, click Next. If you do not need to enable
the Transaction Tracking API function, leave the box unchecked and
click Next.
- A window for choosing the type of application server that the
Data Collector monitors is displayed. The following server types are
available:
- Weblogic Server
- SAP NetWeaver Application Server
- JBoss Application Server
- Tomcat Server
- J2SE Application
Select the application server type, and click Next.
The subsequent configuration steps depend on the application
server type.