#
Configuring Reprise License Manager's (RLM) Shared License Usage Measurements
#
Introduction
Configure rlm-shared-licenses.map
to correct license usage measurements for RLM with user and host license sharing.
Apply the configurations shown in the Open iT server.
#
Configuring rlm-shared-licenses.map
Open
rlm-shared-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.
Add the features with user host license sharing under MAP: UH:
Mapping SyntaxMAP: UH FeatureName\DaemonName\my.hostname;rlm FeatureName\*
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: UH RLMFeature87\*
This example will correct the license usage measurements for all features under RLMFeature87.
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
rlm-shared-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.
Add the features with user host license sharing under MAP: UH:
Mapping SyntaxMAP: UH FeatureName\DaemonName\my.hostname;rlm FeatureName\*
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: UH RLMFeature87\*
This example will correct the license usage measurements for all features under RLMFeature87.
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.
Licpoll2
- (45) Total License Use v2.0
- (46) Individual License Use v2.0
- (47) Host License Use v2.0
- (49) Host User License Use
- (60) Total License Queued
- (61) Individual License Queued
- (71) Usergroup License Use v2.0
- (72) Hostgroup License Use v2.0
- (93) OLAP Raw Hourly
- (94) OLAP User Concurrency
- (102) OLAP Total Use
- (103) OLAP Featureset PPU
- (110) License Application Version
- (111) Total License Use Appversion
- (113) Usergroup License Use Appversion
- (114) Total PPU License Use
- (115) Hostgroup License Use v3.0
#
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: