# Renaming Fekete Software IDs

# Introduction

Configure softwareid-to-feature_name.map to rename Fekete software IDs to readable feature names. The new feature names will be visible in both the License Monitor and historical reports.

# Configuring softwareid-to-feature_name.map

  1. Open softwareid-to-feature_name.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.

  2. Specify Fekete software IDs with the following syntax:

    MAP: Feature_Name  
    old_feature_name\*;product

    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 'FeketeFeature' and 'feketefeature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

    Example
    MAP: Piper  
    1\*;fekete

    This example renames all features under 1\ as Piper.

    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.

  3. Save the changes.

  1. Open softwareid-to-feature_name.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.

  2. Specify Fekete software IDs with the following syntax:

    MAP: Feature_Name   
    old_feature_name\*;product

    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 'FeketeFeature' and 'feketefeature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

    Example
    MAP: Piper  
    1\*;fekete

    This example renames all features under 1\ as Piper.

    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.

  3. Save the changes.

Licenseevents2

# 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  

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close