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:
- Host A and host B must have the same configuration at the operating
system level.
- You must move the same version of the Data Collector from
host A to host B.
To maintain the Probe ID and Controller ID when moving to another
physical host, you need to use the ID file:
Table 1. 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/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/DC_home/runtime/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 |
| J2SE |
DC_home/runtime/j2se.application_name.host_name.instance_name/DC_home/runtime/id |
Perform the following procedure:
- On host A, stop the instance of the application server that
is being monitored by the Data Collector.
- On host B, install the Data Collector and
configure it using the Application Monitor user interface.
Configuring the Data Collector generates
the ID file and other Data Collector runtime
property files.
- On host B, unconfigure the Data Collector.
This step deletes all information about this Data Collector from
the ITCAM for J2EE database.
- On host B, stop the instance of the application server that
is being monitored by the Data Collector.
- Copy the contents in the ID file of host A to the ID file of host
B.
- On host B, save the ID file.
- On host B, start the instance of the application server that
is being 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.