Application Discovery 7.2 User Guide

DescriptionField
Operating system version to which the template applies. If this field is left blank,
Application Discovery tries to match the template against all operating system versions
for which it has information.
OSver
Architecture to which the template applies. If this field is left blank, Application
Discovery tries to match the template against all architectures for which it has
information.
Architecture
NOTE:
If you want to define a template based on where the processes that you want to collect into an
application are running, you can check the “Unmatched processes” table on a particular host
screen or the “Processes not matched by this template” table on a template editing screen to get
this information. See Filling in the System Scope fields using table data for tips on finding specific
process attributes for this purpose.
Separation rule fields and their descriptions
DescriptionField
By default during initial discovery, Application Discovery sets objects recognized as packages
to 'no' and objects recognized as templates to 'yes'.
This field designates whether or not the application shall be visible to users of the Application
Discovery user interface:
• yes – show the application data associated with this object.
• no – hide the application data associated with this object.
NOTE: Visibility actually has no affect on template matching, but is included here as a
convenience. It is a global setting that allows you to control data presentation in all
Application Discovery screens. It is not stored as a user preference.
Is visible?
How many process identifiers (pids) are allowed in an application:
• one — one pid per running application.
Effect: Each new concurrent run of this application is shown as a separate instance from
the others in Application Discovery.
• session – any number of pids per application for the duration of one terminal group
session.
Effect: All associated pids are treated as one running application instance for that session.
However, because sessions on HP-UX and Linux are maintained per user, this has the
effect of delineating running applications per user. Thus, if you log in twice (two concurrent
terminal windows), you can have two separate instances of this running application. This
effect is similar to that obtained by setting user scope=one.
• any – any number of pids per application.
Effect: Pids have no specific effect on defining the application described by this template.
Pid scope
28 Procedures and examples