August 17-20, 2026

KNOWLEDGE BASE

How can we help?

Table of contents

Introduction
Configuring feature-rename.map

Feature Renaming

Key Takeaways

Feature renaming converts cryptic feature names into readable ones that appear in the License Monitor and historical reports, configured in the feature-rename.map file on the Core Server.
Mapping entries are case-insensitive, allow comments and globbing patterns (which run slower than exact matches), and can carry date limits restricting when a rename applies.

License usage reports are only as legible as the feature names inside them — and license managers are notorious for names that mean nothing to anyone outside the vendor. Open iT's feature renaming turns those cryptic identifiers into readable ones that carry through to the License Monitor and historical reports, all driven by a single mapping file, feature-rename.map, on the Core Server. The syntax is compact — mappings, globbing patterns, even date limits — and worth learning before the next report goes out.

Introduction #

This feature allows administrators to convert cryptic feature names into easily understandable names. The new feature name will be visible in the License Monitor and historical reports.

The configuration is done in OpeniT Core Server machine.

Configuring feature-rename.map #

Open feature-rename.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

Notice that it contains instructions on how to edit the file.
Specify the feature to rename with the following syntax:

Mapping Syntax:

MAP: NewFeatureName
OldFeatureName\Daemon\LicenseManager\MyProduct;Daemon

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.

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.

Example:

MAP: RenameFeature025
Feature025\*\*\*

This example renames all Feature025 features to RenameFeature025.

You can also set date limits on specific mapping entries:

Example:

MAP: RenameFeature025 : 2025-01-01 : 2025-02-01
Feature025\*\*\*

The example means that the mapping syntax will only rename Feature025 to RenameFeature025 from 2025-01-01 to 2025-02-01.
Save the changes.

Note: 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.