# Introduction

# Supported Report Types

Level 2 includes historical reporting, real-time monitoring, and a proactive pop-up alert.

# Historical

# Process Accounting

This report type periodically logs the processes used by users, including CPU or memory usage, and the number of times the application runs. To generate reports using the following data types, make sure that the collection of application usage data is activated.

# Active vs Inactive

This report type provides an overview of application disable status and the events associated with applications monitored. To generate reports using the following data types, make sure that freezemonitor is activated.

# Work and Break

This report type shows the collected statistics regarding keyboard and mouse activities. You can also use this to assess the intensity of application usage which helps in determining whether the user actively uses the application or simply opens it and leaves it running. To generate reports using the following data types, make sure that the collection of application resource activity data is activated.

# Web App Tracking

This report type provides an overview of the historical usage of web applications based on web browser logs, plugin cache, and web proxy logs. To generate reports using the following data types, make sure that the collection of web browser log data is activated.

# Real-time

The Analysis Server's License Monitor Portal displays all active and inactive user details based on the filter. To view this, make sure to set the Analysis Server Web Component configuration key Root.Level value to Level2.

# Pop-up

Level 2 starts the pop-up disabler when an application is inactive. To enable this, make sure to use alert as the value of the method attribute, while configuring applications.

# Requirements

To fully access the benefits offered by Level 2, make sure to meet the following prerequisites:

An Open iT Client that is connected to an Open iT Server and has LicenseOptimizer collection activated; or a coexistent Open iT setup
Activated Process Accounting - this will generate Process Accounting reports
Activated Application Resource Activity Data Collection - this will generate Work and Break reports
Activated Freeze Monitor - this will generate Active vs Inactive reports
Activated WebApp Tracker - this will generate Web App Tracker reports

# Configuring Level 2 Applications

You can update the cold_master.conf file to specify applications and licenses to monitor their activity levels; this has four(4) different parts:

Name	Description
applications	Contains configurations listing the applications to be monitored and considered for optimization.
global	Contains configurations applied to all the components related to application optimization.
priorities	Contains configurations to set the priorities of applications on the host, user, and/or group level for optimization.
rules	Contains configurations setting various rules as criteria for optimization for each application.

Cold Configuration Main Parts

The following sections will guide you on the required configuration to specify the applications and further configure how you want them monitored.

# Configuring Applications

The applications section specifies the criteria for logging and alerting users. Here, the keyboard, mouse, cpu, and i/o threshold and weight values are defined. This is also where the executable(s), feature(s), and license server(s) are specified.

These are the required steps to list and configure applications to monitor.

In the Open iT server, open cold_master.conf in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\.
Locate the line:
cold_master.conf
```
BEGIN applications
```

Add a new application with attributes, following the format:

cold_master.conf
--------------------------------
<attribute> = <attribute_value>
...
--------------------------------

These are the Basic Application Attributes that you can use to configure each application.

# handle

This is a text string used to uniquely identify the application. The handle name is case-sensitive, and it is used in the priorities and rules sections of cold_master.conf.

Example
handle = Petrel

# method

This is used to specify the method for disabling the application. There are two possible values that you can use for Level 2:

log - collect usage data, simply log. This can be used to determine the suitable values for the thresholds since it may be difficult to arrive in good threshold levels in the first attempt. Logging while experimenting with this can be helpful. If this method is used, then the application will not be affected by the irq.
alert - informs the user of inactivity with a pop-up based on the set criteria. Here's a sample inactive alert.

Example
method = alert

# irq

This is used to specify the timespan in which the user is warned via the disabler interface of the application to be disabled. Specify its value to your desired timespan based on the ISO-8601 duration format PnDTnHnMn.nS.

Example
irq = P15M

# exe

Executable Name Identifier. This is used to specify the globbing pattern the executables need to match. If applicable, include the parameters and options when specifying the path for the optimizer to match the executable name corresponding to the process. The user can specify several executables with more than one exe line.

Note that two (2) glob patterns of different handles must not match the same process since the match is performed on the whole command line.

Example
exe = *Petrel.exe*
exe	= *StudioManager.exe*
exe	= *ILXAdmin.exe*

# timeout

This is used to specify how long the process must be inactive before considering it for disabling. Change its value to your desired interval based on the ISO-8601 duration format PnDTnHnMn.nS.

Example
timeout = P45M

When a process has been inactive for this much time, the user is notified that the process may be disabled or, if the irq is zero, it is disabled immediately.

# keyboard

The keyboard line has two parameters separated by at least one space. The first value is the keyboard activity threshold, in events per second. An event is either a key press or a key release. The second value is the weight associated with an activity.

Example
keyboard = 0.9 1

# mouse

The mouse line has two parameters separated by at least one space. The first value is the mouse activity threshold, in mouse clicks per second. The second value is the weight associated with an activity below the threshold.

Example
mouse = 0.9 1

# cpu

The cpu line has two parameters separated by at least one space. The first value is the cpu load threshold, and the second is the weight associated with a load below the threshold. If the activity level measured is less than or equal to the threshold, the weight will contribute to the sum used to decide whether a process should be disabled.

Example
cpu = 1.5 1

# i/o

The i/o line has two parameters separated by at least one space. The first value is the i/o activity threshold, in bytes transferred per second. The second value is the weight associated with an activity below the threshold.

Example
i/o = 1.5 1

The summary of the examples used in the basic application attributes would look like this in the configuration file:

Example: Configuring Applications
BEGIN applications
-----------------------------------------
handle    = Petrel
method    = alert
irq       = P15M
exe       = *Petrel.exe*
exe	      = *StudioManager.exe*
exe	      = *ILXAdmin.exe*
timeout   = P45M
keyboard  = 0.9 1
mouse     = 0.9 1    
cpu       = 1.5 1
i/o       = 1.5 1
-----------------------------------------

In the Open iT server, open cold_master.conf in the etc directory, which is by default in /var/opt/openit/etc.
Locate the line:
cold_master.conf
```
BEGIN applications
```

Add a new application with attributes, following the format:

cold_master.conf
--------------------------------
<attribute> = <attribute_value>
...
--------------------------------

These are the Basic Application Attributes that you can use to configure each application.

# handle

This is text string used to uniquely identify the application. The handle name is case-sensitive and it is used in all configuration sections in cold_master.conf except the global section.

Example
handle = OpenWorks

# method

This is used to specify the method for disabling the application. There are two possible values that you can use for Level 2:

log - collect usage data, simply log. This can be used to determine the suitable values for the thresholds since it may be difficult to arrive in good threshold levels in the first attempt. Logging while experimenting with this can be helpful. If this method is used, then the application will not be affected by the irq.
alert - informs the user of inactivity with a pop-up based on the set criteria. Here's a sample inactive alert.

Example
method = log

# irq

Example
irq = P10M

# exe

Note that two (2) glob patterns of different handles must not match the same process since the match is performed on the whole command line.

Example
exe = *OpenWorks*jre64/bin/java*

# timeout

This is used to specify how long the process must be inactive before considering it for disabling. Change its value to your desired interval based on the ISO-8601 duration format PnDTnHnMn.nS.

Example
timeout = P30M

When a process has been inactive for this much time, the user is notified that the process may be disabled or, if the irq is zero, it is disabled immediately.

# cpu

Example
cpu = 0.2 1

# i/o

Example
i/o = 0.2 1

The summary of the examples used in the basic application attributes would look like this in the configuration file:

Example: Configuring Applications
BEGIN applications
-----------------------------------------
handle    = OpenWorks
method    = log
irq       = P10M
exe       = *OpenWorks*jre64/bin/java*
timeout   = P30M
cpu       = 0.2 1
i/o       = 0.2 1
-----------------------------------------

These are the Advanced Application Attributes that you can use in addition to the basic attributes to better configure the applications.

# feature (required for feature-level reporting)

Feature Name Identifier. This is used to specify the feature or product (i.e., <feature-name>\<version>) to return the license when the application is disabled. Multiple features are allowed.

This is applicable to all license managers that create license status data.

Example
feature = *\*

# lmserver (required for feature-level reporting)

This is used to specify the license server(s). Identify the license server (or set) as lmserver=<port>@<host>. If more than one server is in the set, list them as comma-separated. If there is more than one server set, put it in a separate line.

This is applicable to all license managers that create license status data.

Example
lmserver = 27000@MNL368WIN,27003@MNL369WIN
lmserver = 27010@OSL350WIN

In the example, there are two servers in the first set and one in the second set. Each server is specified as port@hostname which needs to match the server listed in the lmstat output.

# lm

License Manager Identifier. This is the type of license manager used by the application. The possible values are flex, lum, or lmx.

Example
lm = flex

# multiple

If set to yes, all processes using the executables in the exe line(s) will be viewed as components of a single application. All processes must be inactive for the joined application to be considered inactive.

Example
multiple = yes

# match-children

If set to yes, all child processes will be handled together while optimizing the application.

Example
match-children = no

# show-window-titles

If set to yes, the window titles of the optimized applications will be listed in the disabler pop-up. This will be automatically set to yes when match-children is enabled.

Example
show-window-titles = yes

# combine-threshold

This combines the threshold values of the CPU and I/O for all instances of the applications to consider idleness.

average - threshold values are averaged
sum - threshold values are summed up

Example
combine-threshold = sum

# exclude

This is a globbing pattern used to specify excluded executables from the exe list. You can include more than one exclude lines.

Example
exclude = *.txt

# arch

Machine Architecture Identifier. This is used to specify the architecture in which the application handle should be valid. Globbing is allowed.

Example
arch = i386

# os

Machine Operating System Identifier. This is used to specify the operating systems in which the application handle should be valid. Globbing is allowed.

Example
os =  windows*

# More Example of Applications Configurations

The following examples show applications configurations with advanced configurations.

cold_master.conf
BEGIN applications
-----------------------------------------
handle           = Petrel
method           = alert
irq              = P15M
exe              = *Petrel.exe*
exe	             = *StudioManager.exe*
exe	             = *ILXAdmin.exe*
timeout          = P45M
keyboard         = 0.9 1
mouse            = 0.9 1    
cpu              = 1.5 1
i/o              = 1.5 1
feature          = Petrel_*\*
feature          = OCEAN_SLB_*\*
lmserver         = 27000@MNL368WIN,27003@MNL369WIN
lmserver         = 27010@OSL350WIN
exclude          = *pluginmanager.exe*
match-children   = no
-----------------------------------------

cold_master.conf
BEGIN applications
-----------------------------------------
handle           = OpenWorks
method           = log
irq              = P10M
exe              = *OpenWorks*jre64/bin/java*
timeout          = P30M
cpu              = 0.2 1
i/o              = 0.2 1
os               = !windows*
feature          = OPENWORKS\*
lmserver         = 27020@MNL1111LIN
lmserver         = 27021@MNL1112LIN
match-children   = yes
-----------------------------------------

BEGIN applications
-----------------------------------------
handle           = RationalPurify
method           = log
timeout          = P1H
irq              = P5M
exe              = *\rational
cpu              = 0.2 1
i/o              = 0.2 1
-----------------------------------------

cold_master.conf
BEGIN applications
-----------------------------------------
handle           = Open iT Client
method           = log
exe              = *\openit_client.exe*
timeout          = P15M
keyboard         = 0 1
mouse            = 0 1
cpu              = 1 1
i/o              = 1000 1
-----------------------------------------

# Configuring Global Threshold

The value to be compared with the threshold is the sum of the weights for the CPU and I/O. A weight is added if the activity of the corresponding measured entities is less than or equal to the threshold, as defined in the applications section in cold_master.conf. If the sum of these weights is greater than or equal to the global threshold, then the process is considered idle and becomes a candidate for disabling. The default value of this threshold is 4.

These are the required steps to change the threshold value.

In the Open iT server, open cold_master.conf in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\.
Locate the line:
cold_master.conf
```
BEGIN global
```
Configure the global disable threshold. Locate the line:
cold_master.conf
```
disable-threshold: 4
```
The thresholds on CPU and I/O are the lower bound of the active levels. That is, if a value is 0.2, then any activity level equal to 0.2 or below will cause the weight to be added.
Save the changes.

In the Open iT server, open cold_master.conf in the etc directory, which is by default in /var/opt/openit/etc.
Locate the line:
cold_master.conf
```
BEGIN global
```
Configure the global disable threshold. Locate the line:
cold_master.conf
```
disable-threshold: 2
```
The thresholds on CPU and I/O are the lower bound of the active levels. That is, if a value is 0.2, then any activity level equal to 0.2 or below will cause the weight to be added.
Save the changes.

# Configuring CPU Calculation

You can also specify how the CPU threshold will be calculated in the global section. By default, this will use the updated calculation, which considers the number of logical processors for both platforms and uses % utilization as the unit of measurement for the CPU threshold. The old calculation only considers the logical processors on Windows machines and uses CPU seconds per second as the unit of measurement.

Add the following in the global section:

cpu-formula-v2: yes

This is, by default, set to yes in version 10 onwards.

# Configuring Priorities

This section specifies the prioritization of application usages based on the type of application, the host, the user, and the usergroup. Specific applications, users, usergroups, and hosts hold greater significance in terms of application usage compared to others. Some setups may require the uninterrupted availability of certain applications.

These are the required steps to elevate or lower application priority for hosts, users, and usergroups.

In the Open iT server, open cold_master.conf in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\.
Locate the line:
cold_master.conf
```
BEGIN priorities
```

Start the configuration in the table with the provided examples.

cold_master.conf
# HANDLE            HOST           USER                GROUP           PRIORITY
Calculator,         *,             *,                  *,              low
Calculator,         *,             Administrator,      *,              normal
NotePad,            *,             *,                  Administrators, total
InternetExplorer,   tiger,         *,                  *,              high
OpenWorks,          *,             root,               *,              total
RationalPurify,     *,             root,               *,              high

Refer to the Cold Configuration Column Properties table to learn the accepted values for configuring each application.

Column Name	Accepted Value	Description
HANDLE	String (e.g., `Notepad`)	Application Name Identifier. The valid name that identifies the application. This is the value of the handle when configuring applications.
HOST	String (e.g., `hou150win`)	Host Name Identifier. The valid name that identifies the machine that hosts the application. Globbing is allowed.
USER	String (e.g., `Administrator`, `$DOMAIN\user`)	User Name Identifier. The valid name that identifies the user that uses the application. Globbing is allowed.
GROUP	String (e.g., `Administrators`)	Group Name Identifier. The valid name that identifies the group where the user using the application belongs. Local group/s and globbing are allowed.
PRIORITY	`total`, `high`, `normal`, `low`	The keyword representing the priority range of the application. `total` - Never disable the application even if the method used is suspend, terminate, or standby. The application will be in LOGGED state and will be reported as inactive. `high` - Elevated priority. The application timeout time is doubled. `normal` - The default priority for all applications. `low` - Lowered priority. The application timeout time is reduced by half.

Cold Configuration Column Properties

Add new entries by either inserting a new line into the existing priority table or, if preferred, replace the existing entries with the applications you added.
Example: Configuring Priorities
```
BEGIN priorities
# HANDLE            HOST           USER                GROUP           PRIORITY
Petrel,             *,             *,                  *,              low
Petrel,             gullvinge,     *,                  *,              normal
Petrel,             gullvinge,     *,                  Administrators, total
OpenWorks,          *,             root,               *,              total
RationalPurify,     *,             root,               *,              high
Open iT Client,		*,			   *,				   Administrators, total   
END
```
When an application matches on multiple lines, the priority is given to the first matching line from the bottom. Therefore, it's advisable to specify general priorities before specific ones.

The example means that the application Petrel is assigned with three priorities, but for different values for other parameters. This application will never be disabled if it is used by the Administrators group on the host gullvinge. For other groups on gullvinge, it has a limited timeout. For other hosts, it will be disabled after half the original timeout time.
Save the changes.

In the Open iT server, open cold_master.conf in the etc directory, which is by default in /var/opt/openit/etc.
Locate the line:
cold_master.conf
```
BEGIN priorities
```

Start the configuration in the table with the provided examples.

cold_master.conf
# HANDLE            HOST           USER                GROUP           PRIORITY
Calculator,         *,             *,                  *,              low
Calculator,         *,             Administrator,      *,              normal
NotePad,            *,             *,                  Administrators, total
InternetExplorer,   tiger,         *,                  *,              high
OpenWorks,          *,             root,               *,              total
RationalPurify,     *,             root,               *,              high

Refer to the Cold Configuration Column Properties table to learn the accepted values for configuring each application.

Column Name	Accepted Value	Description
HANDLE	String (e.g., `OpenWorks`)	Application Name Identifier. The valid name that identifies the application. This is the value of the handle when configuring applications.
HOST	String (e.g., `hou150lin`)	Host Name Identifier. The valid name that identifies the machine that hosts the application. Globbing is allowed.
USER	String (e.g., `Administrator`, `$DOMAIN\user`)	User Name Identifier. The valid name that identifies the user that uses the application. Globbing is allowed.
GROUP	String (e.g., `Administrators`)	Group Name Identifier. The valid name that identifies the group where the user using the application belongs. Local group/s and globbing are allowed.
PRIORITY	`total`, `high`, `normal`, `low`	The keyword representing the priority range of the application. total - Never disable the application even if the method used is suspend, terminate, or standby. The application will be in LOGGED state and will be reported as inactive. high - Elevated priority. Application timeout time is doubled. normal - The default priority for all applications. low - Lowered priority. Application timeout time is reduced by half.

Cold Configuration Column Properties

Add new entries by either inserting a new line into the existing priority table or, if preferred, replace the existing entries with the applications you added.
Example: Configuring Priorities
```
BEGIN priorities
# HANDLE            HOST           USER            GROUP             PRIORITY
Petrel,             *,             *,              *,                low
Petrel,             gullvinge,     *,              *,                normal
Petrel,             gullvinge,     *,              Administrators,   total
OpenWorks,          *,             root,           *,                total
RationalPurify,     *,             root,           *,                high
Open iT Client,		*,			   *,			   Administrators,   total   
END
```
The example means that the application Petrel is assigned with three priorities, but for different values for other parameters. This application will never be disabled if it is used by the Administrators group on the host gullvinge. For other groups on gullvinge, it has a limited timeout. For other hosts, it will be disabled after half the original timeout time.
Save the changes.

# Configuring Rules

The rules section determines when applications should be considered for disabling. Multiple rules can be created for each application. It is possible that more than one rule is valid for a particular application handle. In this case, the first rule that is valid will be used.

Each handle in the configuration file must have a defined rule. Handles that lack rules will be ignored.

These are the required steps to set various rules as optimization criteria for each application.

In the Open iT server, open cold_master.conf in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\.
Locate the line:
cold_master.conf
```
BEGIN rules
```

Start the configuration in the table with the provided examples.

cold_master.conf
# ID   HANDLE              RULES
1,     Calculator,         count > 0
2,     NotePad,            wday=[1-5] + hour=[8-16]
3,     InternetExplorer,   wday=[1-5] + hour=[0-7]
4,     InternetExplorer,   wday=[1-5] + hour=[17-23]
5,     InternetExplorer,   wday=[6-7]
6,     Games,              count > 1
#7,    OpenWorks,          license-use > 70
7,     OpenWorks,          count > 1
#8,    RationalPurify,     license-use > 85
8,     RationalPurify,     count > 1

Use the following syntax for each entry:

Entry Syntax
<id>,    <handle_name>,     <rule1> + <rule2> + ... <ruleN>

Where:
The <id> is a unique number to identify the entry.

The ID uniquely identifies each line and must be unique; duplicates will be ignored and logged as errors.

The <handle_name> is the application name identifier defined in the applications section.

The <rules> are the conditions that define the behavior of the entry.

Each rule should have the following syntax:

rule syntax
<key> <operator> <value>

Refer to the Rule Keys and Rule Operators tables to create a rule.

Key	Description
`count`	Number of processes
`license-use`	Percentage of licenses currently in use
`year`	Year
`month`	Month (1-12)
`mday`	Day of month (1-31)
`week`	Week of year (1-53)
`wday`	Day of week (1-7)
`time`	Time of the day and the timezone (07:00-16:00 or 23:50Z).

Rule Keys

While you can still use the hour and minute keys, please note that these keys are slated for deprecation in version 11.

When using the time key, make sure to use the +/-hh:mm format, which works both with and without a timezone. If you don't specify a timezone, it will automatically default to your machine's local time zone. Z (Zulu time) means UTC.

Operator	Description
`=`	Equal to
`!=`	Not equal to
`>`	Greater than
`>=`	Greater than or equal to
`<`	Less than
`<=`	Less than or equal to

Rule Operators

The <value> may be a single numerical value, a set of numbers, or a range. Single numerical values are given as is. Sets and ranges must be enclosed in square brackets [ ]. The values of a set are separated by commas, and a range is indicated by a hyphen.

Rules can be presented on the same line, separated by a plus sign (+), or displayed individually on multiple lines.

If the rules are presented on a single line separated by +, the application must meet all of the conditions to be eligible for disabling.

Single Line Rules
1, Openworks, license-use > 80 + count > 1

The example will be interpreted as: If license-use is greater than 80% AND if the count is greater than 1, the application may be considered for disabling.

If the rules are presented on multiple lines, the application must fulfill at least one of the conditions to qualify for disabling.

Multiple Line Rules
1, Openworks, license-use > 80
2, Openworks, count > 1

This example will be interpreted as: If license-use is greater than 80% OR if the count is greater than 1, the application may be considered for disabling.

It is advisable to put the lines for the same handle together to easily locate them while updating.

Add new entries by either inserting a new line into the existing rules table or, if preferred, replace the existing entries with the applications you added.
Example: Configuring Rules
```
# ID   HANDLE              RULES
1,	   Petrel,			   count > 2
2,	   Petrel,			   license-use > 85
3,     OpenWorks,          wday=[1-5] + time=[08:00-17:00]
4,     RationalPurify,     time=[23:50Z]
5,     Open iT Client      count > 0
```
The examples indicate that the application Petrel can be disabled under either of two conditions: when the number of processes exceeds two or when the license usage percentage surpasses 85%. OpenWorks can be disabled from Monday to Friday between 8:00 AM and 4:59 PM. RationalPurify will be terminated 10 minutes prior to midnight GMT. The Open iT Client can also be disabled if at least one instance is running.
Save the changes.

In the Open iT server, open cold_master.conf in the etc directory, which is by default in /var/opt/openit/etc.
Locate the line:
cold_master.conf
```
BEGIN rules
```

Start the configuration in the table with the provided examples.

cold_master.conf
# ID   HANDLE              RULES
1,     Calculator,         count > 0
2,     NotePad,            wday=[1-5] + hour=[8-16]
3,     InternetExplorer,   wday=[1-5] + hour=[0-7]
4,     InternetExplorer,   wday=[1-5] + hour=[17-23]
5,     InternetExplorer,   wday=[6-7]
6,     Games,              count > 1
#7,    OpenWorks,          license-use > 70
7,     OpenWorks,          count > 1
#8,    RationalPurify,     license-use > 85
8,     RationalPurify,     count > 1

Use the following syntax for each entry:

Entry Syntax
<id>,    <handle_name>,     <rule1> + <rule2> + ... <ruleN>

Where:
The <id> is a unique number to identify the entry.

The ID uniquely identifies each line and must be unique; duplicates will be ignored and logged as errors.

The <handle_name> is the application name identifier defined in the applications section.

The <rules> are the conditions that define the behavior of the entry.

Each rule should have the following syntax:

rule syntax
<key> <operator> <value>

Refer to the Rule Keys and Rule Operators tables to create a rule.

Key	Description
`count`	Number of processes
`license-use`	Percentage of licenses currently in use
`year`	Year
`month`	Month (1-12)
`mday`	Day of month (1-31)
`week`	Week of year (1-53)
`wday`	Day of week (1-7)
`time`	Time of the day and the timezone (07:00-16:00 or 23:50Z).

Rule Keys

While you can still use the hour and minute keys, please note that these keys are slated for deprecation in version 11.

Operator	Description
`=`	Equal to
`!=`	Not equal to
`>`	Greater than
`>=`	Greater than or equal to
`<`	Less than
`<=`	Less than or equal to

Rule Operators

Rules can be presented on the same line, separated by a plus sign (+), or displayed individually on multiple lines.

If the rules are presented on a single line separated by +, the application must meet all of the conditions to be eligible for disabling.

Single Line Rules
1, Openworks, license-use > 80 + count > 1

The example will be interpreted as: If license-use is greater than 80% AND if the count is greater than 1, the application may be considered for disabling.

If the rules are presented on multiple lines, the application must fulfill at least one of the conditions to qualify for disabling.

Multiple Line Rules
1, Openworks, license-use > 80
2, Openworks, count > 1

This example will be interpreted as: If license-use is greater than 80% OR if the count is greater than 1, the application may be considered for disabling.

It is advisable to put the lines for the same handle together to easily locate them while updating.

Add new entries by either inserting a new line into the existing rules table or, if preferred, replace the existing entries with the applications you added.
Example: Configuring Rules
```
# ID   HANDLE              RULES
1,	   Petrel,			   count > 2
2,     OpenWorks,          wday=[1-5] + time=[08:00-17:00]
3,     RationalPurify,     time=[23:50Z]
4,     Open iT Client      count > 0
```
The examples mean that the application Petrel can be disabled when the number of processes is more than two while the application OpenWorks can be disabled from Monday to Friday (8:00 to 16:59). The application RationalPurify will be terminated 10 minutes before GMT midnight. The Open iT Client application can be disabled if at least one instance is running.
Save the changes.

Here's an example of the cold_master.conf file with all the sections configured:

cold_master.conf
BEGIN applications
-----------------------------------------
handle          = Petrel
method          = alert
irq             = P15M
exe             = *Petrel.exe*
exe	            = *StudioManager.exe*
exe	            = *ILXAdmin.exe*
timeout         = P45M
keyboard        = 0.9 1
mouse           = 0.9 1    
cpu             = 1.5 1
i/o             = 1.5 1
feature         = Petrel_*\*
feature         = OCEAN_SLB_*\*
lmserver        = 27000@MNL368WIN,27003@MNL369WIN
lmserver        = 27010@OSL350WIN
exclude         = *pluginmanager.exe*
match-children  = no
-----------------------------------------
handle          = OpenWorks
method          = log
irq             = P10M
exe             = *OpenWorks*jre64/bin/java*
timeout         = P30M
cpu             = 0.2 1
i/o             = 0.2 1
os              = !windows*
feature         = OPENWORKS\*
lmserver        = 27020@MNL1111LIN
lmserver        = 27021@MNL1112LIN
match-children  = yes
-----------------------------------------
handle          = RationalPurify
method          = log
timeout         = P1H
irq             = P5M
exe             = *\rational
cpu             = 0.2 1
i/o             = 0.2 1
-----------------------------------------
handle          = Open iT Client
method          = log
exe             = *\openit_client.exe*
timeout         = P15M
keyboard        = 0 1
mouse           = 0 1
cpu             = 1 1
i/o             = 1000 1
-----------------------------------------
END


BEGIN global
disable-threshold: 4
END


BEGIN priorities
# HANDLE            HOST           USER            GROUP             PRIORITY
Petrel,             *,             *,              *,                low
Petrel,             gullvinge,     *,              *,                normal
Petrel,             gullvinge,     *,              Administrators,   total
OpenWorks,          *,             root,           *,                total
RationalPurify,     *,             root,           *,                high
Open iT Client,		*,			   *,			   Administrators,   total   
END


BEGIN rules
# ID   HANDLE              RULES
1,     Petrel,             count > 2		   
3,     OpenWorks,          wday=[1-5] + time=[08:00-17:00]
4,     RationalPurify,     time=[23:50Z]
4,     Open iT Client      count > 0
END

cold_master.conf

cold_master.conf 2.21KB