Application Discovery 6.0 Software: User Guide

3. Check that Application Discovery is showing that the discovery ratio is 100%.
a. Click the following tabs in Application Discovery: Admin/Config, then Discovery.
b. Find the following column headings in the data table on this screen. Check that the
value for Discovery ratio is 100%.
When the discovery ratio is less than 100%, this may indicate that an inventory is still
being taken for that host. Expect the warm-up period for completing the process
inventory to take about 20 minutes.
4. Check that templates that you have defined are done correctly and do not conflict with
other template definitions. (See My application does not appear in the “Applications
effected...” table. Why? (page 25) for more information.)
5. Check that any usage of regular expression syntax in the defining application template
is correct.
Application Discovery recognizes regular expressions constructed using Perl 5 or POSIX
syntax and semantics.
To learn how to review and change application template attributes, see “Change application
template values” (page 24)
6. Check that any string or regular expression used in the executable path field of the defining
application template describes the desired running process.
Application Discovery differs from HP Insight Global Workload Manager software for
Integrity (gWLM) in how it matches user input data to discovered applications. gWLM uses
a combination of a fully qualified path and retrieved inode information to find a process on
one managed node. Application Discovery does not infer the location of running processes
based on the presence or location of installed applications. For broader coverage of all
running processes (not just those associated with installed software packages) within a
network of machines, Application Discovery matches strings and regular expressions exactly
when comparing templates to running processes.
It may help to think of the difference between AD and gWLM this way:
In AD, an executable and arg[0] are compared directly to one another to make a match.
In gWLM, the inode of an executable and the inode of arg[0] are compared to one
another to make a match.
See Table 3-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 HP
Insight Global Workload Manager software for Integrity (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.)
Or, to see examples of working templates, click the following tabs: Admin/Config, then AD
Templates. Click a template name to see its attributes.
Data missing in Application Discovery screens 41