internet monitor internet monitor buy statlook internet monitor internet monitor
surveillance software
surveillance software
screen capture
remote desktop
internet monitor
productivity improvement
spector pro
surveillance software
-- previous chapter -- -- table of contents -- -- next chapter --

Creating and edit a pattern

How to create efficient application patterns

You can create a new application pattern or edit an existing one from a dialogue box of Application Patterns Wizard. The definition is entered in a dialogue box shown below.

The Producer list includes all defined software producers. You can define a producer by clicking

Into the Name field you enter a name and in the Version field – an application version. When audit results are displayed, these fields are combined as a single text specifying a software name and version e.g. ANASIL 2.2. 

If a defined application is to be excluded from audit, insert a checkmark into the Exclude from audit checkboxThis application, although identified, will not be displayed on the list of identified applications. It will be included into the list of identified omitted applications. 

The table providing information on an application is the most important element for defining a pattern. To define the pattern correctly, you should define a minimal number of parameters which identify application uniquely. To identify an application, all information entered has to be compliant. Parameters’ names are displayed in the Parameter column, and their values in the Value column. If any value is omitted it means that the relevant parameter will not be analysed in the course of audit. If a pattern is defined on the basis of data of unidentified applications, relevant parameters are only provisionally specified.

The first two parameters File name and File size [B] are usually used for DOS applications or for other applications which do not contain version information inside a file (VesrionInfo). 

Other parameters are entered into relevant fields with version information which is provided with most software designed for Microsoft Windows environment. It is not necessary to define all parameters. In general, CompanyName, ProductName, OriginalFilename and FileVersion fields are sufficient to identify application appropriately. However, if there are two or more applications with identical values for these parameters, you have to specify other values, which enable you to identify a program precisely.

It happens frequently that a producer changes internal information for an application, even for a single version e.g. to specify a language version. It is also widespread that programs differ from one another only in last sequences of version numbers e.g. 8.0.1.5and 8.0.2.6. In such a case it is possible to define a mask which will enable proper identification. For this purpose, you should use the so called regular expressions and highlight the Reg field in the column. 

When defining a pattern on the basis of unidentified application data, you can check whether this pattern enables to identify the application. To do so, click the Check button. 

After you define or modify a pattern click OK to accept the changes or click Cancel to reject the changes. Moreover, a dialogue box includes a status field providing information on possible errors which might occur while entering a change.

This is an example pattern for uplook including the statlook module.

ProductName: UpLook Master Professional
InternalName: UpLookMasterPro
OriginalFilename: UpLook.exe
FileVersion: 1\..*\.21\..*
ProductVersion: 1\..*\.21\..*

FileVersion and ProductVersion parameters use regular expressions. If for an analysed file fields ProductName, InternalName, OriginalFilename are compliant with a relevant pattern and the FileVersion and ProductVersion fields contain values starting with 1.21., the application is identified as uplook with the statlook module.

-- previous chapter -- -- table of contents -- -- next chapter --
surveillance software