IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Move the data collector to a different host computer
If the data collector communicates to ITCAM for Application Diagnostics Managing Server, you may move it to a different host computer while maintaining the same Managing Server identity (Probe ID and Controller ID). The Managing Server will see the new host as the continuation of the old, preserving history, analysis, etc.
The following section describes some prerequisites for moving the data collector to a different host computer while keeping the same Probe ID and Controller ID:
- Host A and host B have the same configuration at the operating system level.
- 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:
- On host A, stop the instance of the application server monitored by the data collector.
- On host B, install the data collector and configure it using the Visualization Engine (Application Monitor) user interface. Configuring the data collector will generate the file...
DC_home/runtime/appserver_version.node_name.server_name/id
...and other data collector runtime property files.
- Use the Visualization Engine (Application Monitor) user interface, unconfigure the data collector on host B. This step deletes all information about this data collector from the ITCAM for Application Diagnostics database. Do not unconfigure the data collector using the Configuration tool.
- On host B, stop the instance of the application server monitored by the data collector.
- Copy the contents of the file...
DC_home/runtime/appserver_version.node_name.server_name/id
...on host A to the file...
DC_home/runtime/appserver_version.node_name.server_name/id
...on host B.
- On host B, save DC_home/runtime/appserver_version.node_name.server_name/id
- 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 by the Managing Server with the runtime configuration of the data collector on host A. This does not affect monitoring in Tivoli Enterprise Portal.
Parent topic:
Customization and advanced configuration for the data collector