IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Use the 7.1.0.1 Managing Server with a 6.0 data collector
You may use data collectors from ITCAM for WebSphere 6.0 or ITCAM for J2EE 6.0 with the current Managing Server. To do this on the Managing Server.
- You can perform this procedure only under the following conditions:
- You still have an existing version 6.0 installation of the data collector.
- You still have an existing version 6.0 of the Managing Server.
You do not need to perform this procedure to use a data collector from ITCAM for WebSphere 6.1, ITCAM for J2EE 6.1, or ITCAM for Web Resources 6.2 with the current Managing Server. To enable the 7.1.0.1 Managing Server to communicate with a version 6.0 data collector:
- Stop the version 7.1.0.1 Managing Server. See Stop the Managing Server.
- Copy the lib6.0 directory from the 6.0 MS_home directory to the version 7.1.0.1 MS_home directory. Do not rename the lib6.0 directory.
- On each host where the 6.0 data collector is installed:
- modify the DC_home/etc/datacollector.properties file to point to the version 7.1.0.1 Managing Server:
- If the version 7.1.0.1 Managing Server is on a different computer than the version 6.0 Managing Server, modify the values for the host name. Here is an example of the modified parameters:
kernel.codebase=http://linux-machine1.usa.company.com:9122/kernel.core.jar http://linux-machine1.usa.company.com:9123/kernel.core.jar http://linux-machine1.usa.company.com:9122/ppe.publish-intf.jar http://linux-machine1.usa.company.com:9123/ppe.publish-intf.jar http://linux-machine1.usa.company.com:9122/ppe.publish.jar http://linux-machine1.usa.company.com:9123/ppe.publish.jar kernel.rfs.address=linux-machine1.usa.company.com:9120 linux-machine1.usa.company.com:9121- By default, the version 7.1.0.1 Managing Server has only one kernel, while the version 6.0 Managing Server has two. If you do not plan on manually creating an additional kernel for the version 7.1.0.1 Managing Server, remove references to the second listed port for the kernel.codebase and kernel.rfs.address parameters. (By default, the second port is 9123 and 9121, respectively.) Match what you would see in the datacollector.properties file for a 7.1.0.1 Data Collector. The values in the 6.0 datacollector.properties file should match what you would see in the datacollector.properties file for a 7.1.0.1 Data Collector. For example,
kernel.codebase=http://linux-machine.usa.company.com:9122 /kernel.core.jar http://linux-machine.usa.company.com:9122 /ppe.publish.jar http://linux-machine.usa.company.com:9122 /ppe.publish-intf.jar kernel.rfs.address=linux-machine.usa.company.com:9120
- If the version 7.1.0.1 Managing Server is on a different computer than the version 6.0 Managing Server, modify the permission java.net.SocketPermission in the DC_home/etc/datacollector.policy file to point to the version 7.1.0.1 Managing Server's host name. For example: permission java.net.SocketPermission "linux-machine.usa.company.com", "connect,accept,resolve";
- If the version 7.1.0.1 Managing Server is on a different computer than the version 6.0 Managing Server, in the DC_home/etc directory, delete node_name.server_name.datacollector.properties
- If you are not migrating data from the version 6.0 Managing Server to the version 7.1.0.1 Managing Server, in the DC_home/etc directory, delete node_name.server_name.cyaneaGpsCounter.txt
- (optional) If you want the data collector runtime to generate a new set of IDs for Probe and ProbeController, delete the DC_home/etc/node_name.server_name.id file.
- If the path for the version 7.1.0.1 MS_home is different than the path for the version 6.0 MS_home, change the MS_AM_HOME environment variable in the WAS administrative console to point to the version 7.1.0.1 Managing Server's installation directory by completing the following steps:
- Log into the WAS administrative console, in the Navigation Pane, select Environment -> WebSphere Variables.
- Select the scope of the variable to add. Most variables used by the data collector are at the server scope of your monitored server.
- Change the following environment variable to point to the MS_home for the version 7.1.0.1 Managing Server: MS_AM_HOME=MS_home
- Click Apply or OK. In the Messages dialog box, click Save.
- In the Save to Master Configuration dialog box, do one of the following:
- If you are under a Network Deployment environment, select Synchronize changes with Nodes and click Save.
- If you are not under a Network Deployment environment, click Save.
- Start the version 7.1.0.1 Managing Server. See Start the Managing Server.
- Check the SystemOut.log to verify that the data collector has connected to the version 7.1.0.1 Managing Server. You should get a message similar to the following:
[1/9/08 14:11:34:380 PST] 00000028 SystemOut O <PPECONTROLLER, 60a8abc2-abcd-dc01-a111-01111e000001.12345, 9.11.111.111> Successfully joined Kernel linux-machine.usa.company.com:9120- Log into the Visualization Engine (Application Monitor) user interface and configure the version 6.0 data collector to be monitored by the version 7.1.0.1 Managing Server by taking the following steps:
- Select Administration -> Server Management -> Data Collector Configuration -> Unconfigured data collectors.
- Check to see that the server for the data collector is listed.
- Apply a configuration to the data collector in the Application Monitor user interface.
- Verify that the data collector components are enabled and running in the Self-Diagnosis page of the Application Monitor user interface.
- Verify that the data collector is communicating with the Managing Server.
- (optional) Since the version 6.0 data collector does not connect to the version 6.0 Managing Server anymore, unconfigure it from the Application Monitor user interface for the version 6.0 Managing Server.
Parent topic:
Customization for the Managing Server on UNIX and Linux