IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Turning on or turning off the data collector connections

The following content provides information about turning on or turning off the data collector connections.


data collector cannot be connected to the Managing Server in a computer outside the DNS

The problem: The data collector fails to connect the Managing Server when the data collector is on a computer outside the DNS.

The cause: The xml parser tries to resolve URLs in the WebSphere variables.xml and cannot because the xml parser being invoked by the WebSphere config code is a non-local resolver.

The solution: ITCAM agent for WebSphere does not support installation of the data collector on computers that are not in the DNS.


Enable communications with Tivoli Enterprise Monitoring Agent if not done during initial installation

The problem: You chose not to enable communications with Tivoli Enterprise Monitoring Agent during the initial installation of the data collector, but you now want to enable it.

The solution: Perform the following procedure:

  1. In the DC_home/runtime/app_server_version.node_name.server_name/app_server_version.node_name.server_name.kwjdc.properties file, make the following modifications:

    1. Uncomment the following line and enter the port number to be used by the Tivoli Enterprise Monitoring Agent:
      com.ibm.tivoli.kwj.agentport=

    2. Uncomment the following line and enter the IP address of the Tivoli Enterprise Monitoring Agent:
      com.ibm.tivoli.kwj.agenthostname=

  2. Restart the data collector by restarting the application server associated with it.


Turn off correlation between the CICS data collector and the WAS data collector

The question: How to turn off correlation between the CICS data collector and the WAS data collector?

The answer: Perform the following steps:

  1. Make a backup of the DC_home/etc/bcm.properties file.

  2. Update the DC_home/etc/bcm.properties file for the Distributed WAS data collector to remove the reference to the *_request_ctg.xml files. This will turn off CTG correlation which is turned on by default in the Distributed WAS code.

  3. Delete the generated bcm.properties file from the DC_home/etc directory (one for each Application Server).

  4. Restart the Distributed WAS Application Server.


Parent topic:

All platforms

+

Search Tips   |   Advanced Search