Application identity and system scope fields and their descriptions
Field | Description |
|
|
Application identity |
|
|
|
Name | Required. Unique name given to the template to represent the application. |
|
|
Version | Required. Version number of the application this template matches. |
|
|
Title | |
|
|
Description | |
|
|
System scope |
|
|
|
OS | 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. |
|
|
OSver | 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. |
|
|
Architecture | 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. |
|
|
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.
30 Procedures and examples