IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Restore the application server configuration after a failed data collector configuration - WAS agent
If the data collector configuration fails, for example if the application server fails to start up, you can use restoreConfig.sh to restore the application server configuration.
Restore in a non-Network Deployment environment
- Locate the backup configuration file...
DC_home/config_dc/backup
If several backup files are present, check the modification date and time of the file; it must be the date and time of the failed configuration. If you did not perform any other data collector configurations on the same host after the failed one, use the most recent file in the directory.
- Stop all instances of the application server.
- Run...
cd Appserver_home/profiles/profile_name/bin
./restoreConfig.sh DC_home/config_dc/backup/backup_file
For example...
cd Appserver_home/profiles/profile_name/bin
./restoreConfig.sh /opt/IBM/itcam/WebSphere/DC/config_dc/backup/WebSphereConfig_2006-04-22.zip
- Start the instances of the application server.
Restore in a Network Deployment environment
- Locate the backup configuration file...
DC_home/config_dc/backup
If several backup files are present, check the modification date and time of the file; it must be the date and time of the failed configuration. If you did not perform any other data collector configurations on the same host after the failed one, use the most recent file in the directory.
- Stop all instances of application servers. Perform the steps in Stop the application server.
- Create a temporary directory in any convenient path (temp_directory). On a UNIX or Linux host, create it under /tmp.
- Run
cd Appserver_home/profiles/profile_name/bin
./restoreConfig.sh DC_home/config_dc/backup/backup_file -location /path/to/tmpdir
For example...
cd Appserver_home/profiles/profile_name/bin
./restoreConfig.sh /opt/IBM/itcam/WebSphere/DC/config_dc/backup/WebSphereConfig_2006-04-22.zip -location /path/to/tmpdir
Running restoreConfig.sh restores the original application server configuration to the temporary directory.
- Copy server.xml, variables.xml, and pmi-config.xml from the following path:
temp_directory/restored_configuration_home/cells/cell_name/nodes/node_name/servers/server_name
...to the following path on the Deployment Manager host:
Appserver_home/profiles/profile_name/config/cells/cell_name/nodes/node_name/servers/server_name
- Perform a node sync from the deployment manager's administrative console for the node.
- In the deployment manager's administrative console, save changes to the master configuration.
- Start the instances of the application server.
Split the data collector installation into two parts
- Generate the data collector run time directory
- Modify the WebSphere parameters.
For more information, refer to the OPAL website. In the search field, type in the following search criteria,
Composite Application Manager for WebSphere Data Collector Configuration Solution for Large Scaled WebSphere
Parent topic:
Manual changes to application server configuration for the data collector