#
Setting the Number of Available Licenses of Features
#
Introduction
Configure available-licenses.map
to set the number of licenses of features. The configured available license will be visible in both the License Monitor and historical reports.
Apply the configurations shown in the Open iT server.
#
Configuring available-licenses.map
Open
available-licenses.map
in the Configuration directory, which is by default inC:\Program Files\OpeniT\Core\Configuration
.Notice that it contains instructions on how to edit the file.
Specify the feature and the number of licenses with the following syntax:
Mapping SyntaxMAP: NumberOfLicenses Feature1\Version\Product2 Feature2\Version\Product2 Feature3\Version\Product2
The version and product name can be used to map features more specifically, but they are not required in the mapping configuration.
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.
In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Feature' and 'feature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: 25 MATLAB\v10.8 MAP: 20 MATLAB\v10.0
This example sets 25 as the available licenses for MATLAB version 10.8 and 20 for MATLAB version 10.0.
You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.
The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.
Open
available-licenses.map
in the etc directory, which is by default in/var/opt/openit/etc
.Notice that it contains instructions on how to edit the file.
Specify the feature and the number of licenses with the following syntax:
Mapping SyntaxMAP: NumberOfLicenses Feature1\Version\Product2 Feature2\Version\Product2 Feature3\Version\Product2
The version and product name can be used to map features more specifically, but they are not required in the mapping configuration.
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.
In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Feature' and 'feature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: 25 MATLAB\v10.8 MAP: 20 MATLAB\v10.0
This example sets 25 as the available licenses for MATLAB version 10.8 and 20 for MATLAB version 10.0.
You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.
The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.
The available-licenses.map
does not apply to features with multiple expiration dates.
Licpoll2
- (93) OLAP Raw Hourly
- (102) OLAP Total Use
- (124) License Model User Concurrency
- (125) License Model Total Use
- (143) Normalized License Total Concurrency
Licenseevents
Licusage
#
Next Steps?
Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the real-time and historical reports.
For real-time reports:
Generating License Status Data
For historical reports: