IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
data collector configuration tips
The following content provide some tips on data collector configuration.
Configure the data collector when using hyphenated Managing Server host name or a lengthy FQDN
The problem: How to configure the data collector when using hyphenated Managing Server host name or a lengthy fully qualified domain name (FQDN).
The reason: If you are using a hyphenated Managing Server host name or a lengthy FQDN, the data collector Config may fail during configuration.
The solution: To resolve this problem, continue the configuration even if the configuration says it cannot reach the Managing Server. After the configuration is complete, simply edit the app_server_name.node_name.server_name.datacollector.properties file in the DC_home/runtime/node_name directory using the following method:
Change the hyphenated host name or FQDN in the kernel.codebase and kernel.rfs.address fields in this file to the IP address of the Managing Server and then restart the server. Also, if needed, make changes to wherever referred to the lengthy Managing Server FQDN in this file.
Non-root data collector configuration cannot lock system preferences
The problem: When using a non-root user to install and configure the data collector, system preferences cannot be locked. The following error is displayed in the console:
java.lang.SecurityException: Could not lock System prefs. Lock file access denied. at java.util.prefs.FileSystemPreferences. checkLockFile0ErrorCode(FileSystemPreferences.java:937) at java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) at java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) at java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) at java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:476) at java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) at java.util.prefs.FileSystemPreferences$4.run(FileSystemPreferences.java:437) at java.util.TimerThread.mainLoop(Timer.java:447) at java.util.TimerThread.run(Timer.java:397)The reason: This problem is a limitation of JRE, please reference http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4438983 for more information.
Verifying the Data Collector Configuration
The question: How can I verify if the data collector was configured properly?
The answer: The best way to tell if the ITCAM for WebSphere Data Collector is configured properly is to check the following items.
- When using an ITCAM console (which is part of the Managing Server):
- If the data collector shows up in the ITCAM console, it means that:
- the WebSphere definitions are added properly;
- the files in the DC_home/runtime directory were created with no permission problems;
- the network connectivity is good between the Managing Server and the data collector.
- The Managing Server must be at an equal or greater fix pack level than the data collector. You can verify the fix pack level by comparing the following two files:
- MS_home/etc/am-version.properties
- DC_home/itcamdc/etc/version.properties
- When using a Tivoli Enterprise Portal Interface:
- You can verify that the data collector is connected to the Tivoli Enterprise Monitoring Agent by verifying that the WAS icon and the tree that is displayed under it in the navigator are present and available.
- The Tivoli Enterprise Monitoring Agent and the data collector must be at the same level. You can verify it by comparing the data collector level in DC_home/itcamdc/etc/version.properties to the Tivoli Enterprise Monitoring Agent level which can be determined by running the following commands on the Tivoli Enterprise Monitoring Agent machine:
- For UNIX: ITM_home/bin/cinfo -i
- For Windows: ITM_home/InstallITM/kincinfo -i
- If Tivoli Enterprise Portal screens have bad labels in the navigation tree or if workspaces are not formatted properly for tables/graphs, you may have a problem with the wrong level of Application Support Files being installed on the Tivoli Enterprise Monitoring Server /Tivoli Enterprise Portal Server /Tivoli Enterprise Portal Desktop as compared to the Tivoli Enterprise Monitoring Agent. Use the preceding commands on the Tivoli Enterprise Monitoring Agent, Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop to confirm that all are in consistence. For ITCAM Agent for WebSphere, the two byte code is yn; for ITCAM Agent for HTTP Servers, the two byte code is ht.
Parent topic:
All platforms