#
Configuring Host Rename
#
Introduction
Configure host-rename.map
to rename hostnames. The new hostname will be visible in both the License Monitor and historical reports.
Apply the configurations shown in the Open iT server.
#
Configuring host-rename.map
Open
host-rename.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 hostnames with the following syntax:
Mapping SyntaxMAP: New_Hostname Hostname1 Hostname2
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 'Hostname' and 'hostname', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: MNL-WIN MNL001WIN MNL002WIN
This example renames MNL001WIN and MNL002WIN to MNL-WIN.
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
host-rename.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 hostnames with the following syntax:
Mapping SyntaxMAP: New_Hostname Hostname1 Hostname2
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 'Hostname' and 'hostname', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: MNL-WIN MNL001WIN MNL002WIN
This example renames MNL001WIN and MNL002WIN to MNL-WIN.
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
- (47) Host License Use v2.0
- (49) Host User License Use
- (93) OLAP Raw Hourly
- (103) OLAP featureset ppu
FlexLog2
- (50) Host User License Use Logfile
- (75) License Logfile Events
- (83) Host License Use Logfile
- (84) Individual License Use Logfile
Licenseevents
Licenseevents2
Webappbrowseractivity
- (122) Web App Browser Activity
Webappbrowserlog
- (120) Web App Browser Log
Freeze
- (62) License Optimizer Use
- (64) License Optimizer Events
- (92) License Optimizer Actions
- (97) OLAP Freeze Raw Hourly
Winapp
Recorder
- (56) UsageAnalyzer Break
- (57) UsageAnalyzer Work
- (58) UsageAnalyzer Events
Autodesk
Dongle
- (119) Dongle Data Usage
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: