# Feature Renaming

# Introduction

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

If there is Analysis Server, use the Feature Labelling.

Apply the configurations shown in the Open iT server.

# 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. 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.
Example
```
MAP: RenameFeature025
Feature025\*\*\*
```
This example renames all of the Feature025 features to RenameFeature025.

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 feature-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 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. 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.
Example
```
MAP: RenameFeature025
Feature025\*\*\*
```
This example renames all of the Feature025 features to RenameFeature025.

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

FlexLog2

Licenseevents

(89) Total License Use Licenseevents
(90) Individual License Use Licenseevents
(91) Usergroup License Use Licenseevents
(108) Host License Use Licenseevents
(109) Hostgroup License Use Licenseevents

Licenseevents2

(104) License Logfile Events v2.0
(107) Denied License Use Licenseevents

# 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:

Data Generation

# Feature Renaming

# Introduction

# Configuring feature-rename.map

# Next Steps?

# Configuring `feature-rename.map`