IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Move the data collector to a different host computer - J2EE Agent

The following prerequisites are required if you want to move the data collector to a different host computer while keeping the same Probe ID and Controller ID:

To maintain the Probe ID and Controller ID when moving to another physical host, you will need to use the ID file:


Locations of the ID file

WebLogic If the monitored server instance is represented by a weblogic machine:

DC_home/runtime/wlsapp_server_version.domain_name.machine_name.instance_name/wlsapp_server_version.domain_name.machine_name.instance_name.id

else:

DC_home/runtime/wlsapp_server_version.domain_name.host_name.instance_name/wlsapp_server_version.domain_name.host_name.instance_name.id

Tomcat DC_home/runtime/tomcatapp_server_version.host_name.instance_name/DC_home/runtime/tomcatapp_server_version.host_name.instance_name.id
Sun Java System Application Server (JSAS) DC_home/runtime/sjsasapp_server_version.domain_name.node_name.instance_name/sjsasapp_server_version.domain_name.node_name.instance_name.id
JBoss DC_home/runtime/jbossapp_server_version.host_name.instance_name/jbossapp_server_version.host_name.instance_name.id
NetWeaver DC_home/runtime/netweaverapp_server_version.sap_node_ID_host_name.sap_instance_number/netweaverapp_server_version.sap_node_ID_host_name.sap_instance_number.id
Oracle DC_home/runtime/oracleapp_server_version.host_name.node_name.instance_name/oracleapp_server_version.host_name.node_name.instance_name.id
J2SE DC_home/runtime/j2se.application_name.host_name.instance_name/DC_home/runtime/j2se.application_name.host_name.instance_name.id


ID file name

WebLogic If the monitored server instance is represented by a weblogic machine:

DC_home/runtime/wlsapp_server_version.domain_name.machine_name.instance_name.id

else:

DC_home/runtime/wlsapp_server_version.domain_name.host_name.instance_name.id

Tomcat DC_home/runtime/tomcatapp_server_version.host_name.instance_name.id
Sun Java System Application Server (JSAS) DC_home/runtime/sjsasapp_server_version.domain_name.node_name.instance_name.id
JBoss DC_home/runtime/jbossapp_server_version.host_name.instance_name.id
NetWeaver DC_home/runtime/netweaverapp_server_version.sap_node_ID_host_name.sap_instance_number.id
Oracle DC_home/runtime/oracleapp_server_version.host_name.node_name.instance_name.id
J2SE DC_home/runtime/j2se.application_name.host_name.instance_name.id

Perform the following procedure:

  1. On host A, stop the instance of the application server monitored by the data collector.
  2. On host B, install the data collector and configure it using the Application Monitor user interface. Configuring the data collector will generate the ID file and other data collector runtime property files.
  3. On host B, unconfigure the data collector. This step deletes all information about this data collector from the ITCAM for J2EE database.
  4. On host B, stop the instance of the application server monitored by the data collector.

  5. Copy the contents in host A's ID file to host B's ID file.
  6. On host B, save the ID file.
  7. On host B, start the instance of the application server monitored by the data collector.

The data collector on host B assumes the identity of the data collector on host A and is configured with the runtime configuration of the data collector on host A.


Parent topic:

Customization and advanced configuration for the data collector