Application Discovery 7.2 User Guide

See Table 3 (page 27) for a demonstration of the different results that you can expect when
using the same executable and arguments in Application Discovery as compared to Global
Workload Manager (gWLM).
To check your application template data against the process data that Application Discovery
has catalogued, you can consult the following:
• “Processes unmatched by this template” table for a particular host.
• “Processes unmatched by this template” table.
• "Applications effected by this template" table. See Individual application template view
in the Application Discovery Online Help.
Or, to see examples of working templates, click the following tabs: Admin/Config, then AD
Templates. Click a template name to see its attributes.
NOTE: Where large amounts of data are present in tables, it can be useful to sort or filter
the data to find the exact process and associated attributes for which you are searching.
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 42) and
“Errors due to incompatibilities between different versions of Application Discovery agents and
servers” (page 48) .
Host not visible in Application Discovery screens
1. Check that the host appears on the list of hosts managed via Systems Insight Manager.
An unlisted host is not being managed via Systems Insight Manager, and therefore, cannot
be discovered by Application Discovery.
To learn how to add a managed system to the system list, see “Setting up managed systems”
in HP Systems Insight Manager Help Online Help.
2. Check that the managed systems (including virtual machines) have valid sign-in credentials
defined in Systems Insight Manager.
3. Check that an Application Discovery agent is running on the managed host. To view the list
of hosts running an Application Discovery agent, click the Admin/Config tab, and then the
Agents tab. The Agents tab lists all discovered hosts running the Application Discovery agent.
4. Check that the host is marked as 'visible' in Application Discovery.
a. Click the following tabs in Application Discovery: Admin/Config, then Discovery.
b. Find the column heading “Visible”. Hosts marked with 'Y' are currently visible in
Application Discovery screens. Hosts marked with 'N' are hidden.
5. Check that no firewall is blocking port 22 (used by SSH) or port 5989 (used by WBEM) on
managed systems.
Unblock the ports.
Once this action is taken, check that Application Discovery is receiving messages from the
host. (See #8 in this section.)
6. Check that the managed node has been configured to allow remote command execution by
the CMS.
To set the managed node to allow remote command execution, type the following:
/opt/mx/bin/mxagentconfig -a -n hostname -u root
Once this action is taken, check that Application Discovery is receiving messages from the
host. (See #8 in this section.)
42 Troubleshooting