Including or Excluding Features from Data Collection
The license.exclude
file serves as a general configuration file for including and excluding features in data collection.
- Windows
- Unix
-
Open the
license.exclude
configuration file located atC:\Program Files\OpeniT\Core\Configuration
. Notice the written instructions for proper configuration.Use the following format for each entry:
license.exclude format<vendor_license>:<feature<;version><:component>> <use>
where
<use>
is eitherinclude
orexclude
, depending on the purpose of the entry.The
vendor_license
,feature
(in the formatfeature;version
), andcomponent
fields can be a single string or a comma-separated list.Multiple Entries
To specify more than one value for a field, separate them with commas. For example:
Multiple Vendor Licensealpha,beta,gamma:*:*
If a vendor license name itself contains a comma, you must escape it using a backslash (
\
). For example, a vendor license namedalpha,beta,gamma:msc
should be written as:Vendor License Name with Commaalpha\,beta\,gamma:msc:*:*
Globbing Support
You can use globbing patterns with
*
and?
for flexible matching. These patterns are useful for partial name matches.Case Insensitivity
All entries are case-insensitive, so
Alpha
,alpha
, andALPHA
are treated the same.Comments and Whitespace
- Empty lines are allowed and ignored during processing.
- Any line that starts with
#
is treated as a comment.
-
Add new lines for new entries.
NoteSpecify general, followed by specific elements. Entries are processed sequentially, starting from the top.
This example excludes all features with version trial, regardless of the vendor license or component.
General Example*:*;trial:* exclude
Another example includes the MATLAB features simulink (version 2022a) and simscape (version 2023b), across all components.
Specific Examplematlab:simulink;2022a,simscape;2023b:* include
-
Save the changes.
-
Open the
license.exclude
configuration file located at/var/opt/openit/etc
. Notice the written instructions for proper configuration.Use the following format for each entry:
license.exclude format<vendor_license>:<feature<;version><:component>> <use>
where
<use>
is eitherinclude
orexclude
, depending on the purpose of the entry.The
vendor_license
,feature
(in the formatfeature;version
), andcomponent
fields can be a single string or a comma-separated list.Multiple Entries
To specify more than one value for a field, separate them with commas. For example:
Multiple Vendor Licensealpha,beta,gamma:*:*
If a vendor license name itself contains a comma, you must escape it using a backslash (
\
). For example, a vendor license namedalpha,beta,gamma:msc
should be written as:Vendor License Name with Commaalpha\,beta\,gamma:msc:*:*
Globbing Support
You can use globbing patterns with
*
and?
for flexible matching. These patterns are useful for partial name matches.Case Insensitivity
All entries are case-insensitive, so
Alpha
,alpha
, andALPHA
are treated the same.Comments and Whitespace
- Empty lines are allowed and ignored during processing.
- Any line that starts with
#
is treated as a comment.
-
Add new lines for new entries.
NoteSpecify general, followed by specific elements. Entries are processed sequentially, starting from the top.
This example excludes all features with version trial, regardless of the vendor license or component.
General Example*:*;trial:* exclude
Another example excludes all versions of the Compiler feature under Synopsys for any component.
Specific Examplesynopsys:Compiler;*:* exclude
-
Save the changes.