IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Application Server subnode not available
The problem: Tivoli Enterprise Monitoring Agent to data collector connection fails and the application Server subnode is not available in Tivoli Enterprise Portal.
The solution: Check connection between the Tivoli Enterprise Monitoring Agent and the data collector:
- Check that the physical socket connection between the Tivoli Enterprise Monitoring Agent and the data collector exists. You can use the net stat utility to check. For example, using the command bash-2.05b# netstat -a | grep 63335, the following table shows that the Tivoli Enterprise Monitoring Agent has established a connection with one application server:
Tivoli Enterprise Monitoring Agent Connections
localhost.41576 localhost.63335 49152 0 49152 0 ESTABLISHED localhost.63335 localhost.41576 49152 0 49152 0 ESTABLISHED *.63335 *.* 0 0 49152 0 LISTEN
- If socket connection is not established, check that the data collector is configured correctly. The DC_home/runtime/platform.node.server/platform.node.server.kwjdc.properties properties file should have two properties uncommented and set as follows:
com.ibm.tivoli.kwj.agentport=63335 com.ibm.tivoli.kwj.agenthostname=127.0.0.1- If the Tivoli Enterprise Monitoring Agent listen port is not bound, check the Tivoli Enterprise Monitoring Agent configuration in GUI or command-line mode.
Parent topic:
Troubleshooting: Tivoli Enterprise Portal