Add or edit applications: Reference

Refer to the tables below for field descriptions when you want to add new applications to your Private Application Catalogue in Snow Atlas.

Application details

The Application details tab lets you, for example, add the version, edition, and metric of the application.

Field label	Description
Name	The name of the application as it appears in Snow Atlas. (Required)
Manufacturer	The name of the application manufacturer. (Required) If you cannot find the manufacturer in the list, you have the possibility to add the manufacturer as a new one in your Private Application Catalogue.
Family	The family that the application belongs to. The application family name does not include a version or edition name. Example: "Microsoft Excel" or "iTunes". Application families are used for managing license upgrades and downgrades. If you cannot find the family in the list, you have the possibility to add the family as a new one in your Private Application Catalogue.
Edition	The edition of the application. Example: "Standard" or "Professional".
Edition index	The edition index of the application drives categorization of the editions, such as Enterprise and Standard, for cross edition rights as well as license upgrades and downgrades. Only numbers between 1 and 999 are allowed.
Version	The version of the application. Example: "10" , "v11" , or "2.4".
Version index	The version index of the application determines the paths of the upgrade and downgrade rights for the application. It is a licensing construct and does not reflect real versions. Version indexes should follow the same order as the released versions: a more recent version should have a higher version index than a previously released version. Only numbers between 1 and 999 are allowed.
License required	If this setting is enabled, the application requires a license and you must also select a Preferred metric for the application.
Preferred metric	The preferred metric describes the general licensing conditions for the application. Requires that License required is enabled.
Operating system	The operating system that the application is running on.
Operating system	If turned on, the application is an operating system.

Application discovery

On the Application discovery tab, under Rule, you can add search parameters, or rules, to identify the application and to collect usage information.

When you have the exact name of the application, manufacturer, version, or executable path, you can use them for your rules. However, if you don't know the exact names or if you want to search for similar names or versions, you can use "%" and "_" as wildcard characters.

EXAMPLE

• If you enter application name VMware HGFS Client, the search will result in software rows where the application name is exactly VMware HGFS Client.
• If you enter application name VMware HG%, the search will result in software rows where the application name starts with VMware HG.
• If you enter version name 10._, the search will result in software rows where the version is, for example, 10.1 or 10.5. The "_" character allows for one additional character.
• If you enter executable path %word.exe, the search will result in software rows where the executable path ends with word.exe.

Field label	Description
Name definition	All applications with this name definition are identified by this rule. The definition is matched against the Name column of the inventoried data.
Manufacturer definition	All applications with this manufacturer definition are identified by this rule. The definition is matched against the Manufacturer column of the inventoried data.
Version definition	All applications with this version definition are identified by this rule. The definition is matched against the Version column of the inventoried data.
Executable path definition	All applications with this executable path definition are identified by this rule. The definition is matched against the ExecutablePath column of the inventoried data. It is advisable to use "%" as a wildcard character before the executable name to catch all software rows. If Registry key is turned on, this parameter will not be used.
Registry key	When turned on, only data collected from the Windows registry is considered in the search. If you have added also an Executable path definition as a search parameter, that parameter will not be used. The Snow inventory agent collects data rows from the Windows registry. These additional data rows play an important role when traditional identification of executable files is not enough. SWID tag data is included when you use this type of rule. As an example, the DIS gets useful information on IBM SWID tags through the registry data. IBM SWID tag data collected by the Snow inventory agent is labeled as IsRegistry. If you need to identify any IBM components that are not globally available, you can use the registry data to add recognition of the respective product. The DIS also deploys several scripts to identify software applications which cannot be identified by the executables. These datarows are reported back labeled as IsRegistry.

On the Application discovery tab, under Filters, you see a list of available collection filters that you can select to run your rules against.

On the Application discovery tab, under Added rules, you see a list of all search parameters added for the application.