HP 5992-3838 - Manual (Page 51)

4. Check to see if the workload is parked.
A parked workload does not generate process maps anywhere. Process maps that existed
prior to parking the workload are deleted. See the discussion of “General Workload Properties
” in Virtualization Manager Help and the glossary for information about parked workloads.
5. Check to see that the application associated with the workload is currently running.
In Application Discovery, click the Applications tab. Then, under the Running tab, sort by
host. (Click the 'Host' column header to toggle the list to sort in ascending or descending
alphabetical order.) To rule out the possibility that the running application is hidden, click
the drop-down menu above the 'Application Instances' to 'Show hidden apps'. If the
application that you are looking for is not in this list, you must run the application so that
it can be discovered.
6. Check that Application Discovery server is running on the CMS.
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.
NOTE: If none of these measures are sufficient, other underlying problems may be the
cause. See also the suggestions in “Host Not Visible in Application Discovery Screens”
(page 46) that relate to communication between the Application Discovery server and the
WBEM provider and between the WBEM provider and the Application Discovery agent.
Cannot Enter Application Discovery User Interface
You can see this message when this problem occurs:
You are not authorized to view this screen.
Please login with the right credentials.
To gain access to Application Discovery user interface via links in Virtualization Manager, you
must set your user authorizations to include AD Monitor Tools or AD All Tools, depending on
your job role. See “User Authorizations” in VSE Management Software Help for more information.
Errors in Application Discovery User Interface Operation
Issues listed in this section include the following:
•
“UI “Unable to Connect to Server” Messages” (page 51)
• “Java 'UI exception' Message Displays” (page 52)
UI “Unable to Connect to Server” Messages
1. Application Discovery might not be correctly configured.
Run vseinitconfig -a on the command line to correct the configuration of Application
Discovery. (See also vseinitconfig(1M.)
To identify other configuration problems that might be affecting Application Discovery
server, check the “Troubleshooting” notes in the VSE Management Software Help instructions,
or use vseassist(1M).
Introduction 51