HP Matrix Operating Environment Software - Manual (Page 27)

NOTE:
Application Discovery (AD) interprets executable path strings differently than Global Workload
Manager (gWLM).
Application Discovery looks at a process from the perspective of how it is named when it is running.
Therefore, to successfully construct an application that Application Discovery recognizes, you must
provide attributes (data strings) that describe the running process.
Also, when defining an application, keep in mind that Application Discovery looks across your
entire network for likely matches, and not just on one particular managed node.
It might 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.
The following examples demonstrate the different results that you can expect when using the same
executable and arguments in Application Discovery as compared to Global Workload Manager
(gWLM).
Table 3 An example comparison of match behavior in AD and gWLM for same executable path
and arguments
gWLM AD Example inputs
Process arg[0] Executable
match match /usr/sbin/biod
/usr/sbin/biod match no match biod
match no match ./biod
not allowed match /usr/sbin/biod
biod not allowed match biod
not allowed match ./biod
Application identity and system scope fields and their descriptions
Description Field
Application identity
Required. Unique name given to the template to represent the application. Name
Required. Version number of the application this template matches. Version
User-defined name for the template. Title
User-defined summary describing the template. Description
System scope
Operating system to which the template applies. If this field is left blank, Application
Discovery tries to match the template within all operating systems for which it has
information. OS
Managing application templates 27