Application Discovery 7.2 User Guide

To identify other configuration problems that might be affecting Application Discovery server,
check the “Troubleshooting” notes in the Matrix Operating Environment help instructions, or
use vseassist(1M).
NOTE:
Be aware that one possible cause for incorrect configuration is the case where installation
and startup deviate from the documented process. In this situation, you might see the following
error message:
Application Discovery UI encountered an error: The UI and server
are out of sync.
If Application Discovery web application and Application Discovery server are not from the
same installation version, you must reinstall Application Discovery before using
vseinitconfig -a.
2. Check that Application Discovery server is running on the CMS.
On HP-UX, type ps -elf | grep amgrserver.jar on the command line of the CMS.
You should see a Java process running the Application Discovery server.
If you do not see this Java process, type /opt/amgr/bin/cms_start . You must be logged
in as user 'root' on the CMS to initiate this command.
On Microsoft Windows, type C:>net start on the command line of the CMS. You should
see a service called Application Discovery in the list of running services.
If you do not see this service, type cms_start from any directory in the Matrix Operating
Environment installed drive. You must be logged in as Administrator on the CMS to initiate
this command.
Java “UI exception” message displays
“UI exception” errors indicate that a problem internal to the Application Discovery user interface
exists. Please contact HP to report the error and receive assistance. See Chapter 5 (page 51) .
Errors due to incompatibilities between different versions of Application
Discovery agents and servers
Diagnosing problems with agent-server communication can be simplified by first checking that the
Application Discovery server that you are running on your CMS is compatible with the agents that
you are running on your managed systems.
The version 7.0 Application Discovery server can communicate with 6.0, 6.1, 6.2, 6.3, 7.0 and
4.x versions of the agent.
48 Troubleshooting