# /opt/amgr/bin/agent_wbem_config
Loading Application Discovery schema
Loading Application Discovery metadata
4.
Check that the Application Discovery agent certificate has been installed on the managed
node.
Type the following on the command line of the managed node:
# ls /var/opt/amgr/ssl/agent_cert.pem
/var/opt/amgr/ssl/agent_cert.pem
If
agent_cert.pem
is not listed, you can create the certificate by typing the following on
the command line:
# /opt/amgr/bin/make_agent_cert
Host name is xyz.cup.hp.com
...
Finished agent certificate creation.
Data Missing in Application Discovery Screens
Issues listed in this section include the following:
•
“Applications Not Visible in Application Discovery Screens” (page 44)
•
“Host Not Visible in Application Discovery Screens” (page 46)
•
“Packages Not Visible in Application Discovery Screens” (page 48)
Applications Not Visible in Application Discovery Screens
1.
Check that the application is not hidden from view in the application table.
Tables that list applications are preceded by the 'Application Visibility' drop-down that lets
you toggle to
Show hidden apps
. Select this option and scan the table for your application.
Also, check that no filters are in operation in the table. (If one or more filters have been
applied to the table, they are listed on the right in the dark gray table header bar.) To remove
current filters, right-click anywhere on the table, and select
Clear all filters
.
If you cannot find the application, Application Discovery is not currently recognizing the
application as matched to a template.
2.
It is possible that certificate exchange has not been completed.
See
“Completing Certificate Exchange” (page 63)
for instructions on completing the certificate
exchange. The Application Discovery agent starts running (and begins sending data to the
Application Discovery server) on completion of the certificate exchange.
44
Troubleshooting and Error Messages