Reprise License Manager's (RLM) Shared License Usage Measurements Configuration
Introduction
Configure rlm-shared-licenses.map to ensure accurate license usage measurements for RLM environments that use user and host, or user-only license sharing.
Apply the configurations shown in the Open iT Core Server.
Configuring rlm-shared-licenses.map
The rlm-shared-licenses.map file defines how RLM handles licenses for sharing. Depending on whether you want to share licenses across both user and host, or by user-only, you must add the features to either the MAP: UH or MAP: U section. Use the instructions below to configure each mapping type.
Configuring User Host License Sharing (MAP: UH)
- Windows
- Unix
-
Open
rlm-shared-licenses.mapin 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\*>The UH must not be changed.
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 Optimizing 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\*\WIN-HOST01;rlmThis example will correct the license usage measurements for all features under RLMFeature87 on host WIN-HOST01;rlm.
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.
-
Open
rlm-shared-licenses.mapin 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\*>The UH must not be changed.
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 Optimizing 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\*\host01;rlmThis example will correct the license usage measurements for all features under RLMFeature87 on the host host01;rlm.
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.
Configuring User License Sharing (MAP: U)
- Windows
- Unix
-
Open
rlm-shared-licenses.mapin 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 license sharing under MAP: U:
Mapping SyntaxMAP: U
<FeatureName\DaemonName\my.hostname;rlm>
<FeatureName\*>The U must not be changed.
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 Optimizing 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: U
RLMFeature87\RLMDaemon\*This example will correct the license usage measurements for all features under RLMFeature87 and RLMDaemon.
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.
-
Open
rlm-shared-licenses.mapin 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 license sharing under MAP: U:
Mapping SyntaxMAP: U
<FeatureName\DaemonName\my.hostname;rlm>
<FeatureName\*>The U must not be changed.
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 Optimizing 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: U
RLMFeature87\RLMDaemon\*This example will correct the license usage measurements for all features under RLMFeature87 and RLMDaemon.
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.
This mapping may affect the following data types:
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:
For historical reports: