# Feature Mapping

# Introduction

Analyzing the combined usage of combined features can provide valuable insights for creating reports or addressing potential licensing requirements. It is essential to establish a feature mapping configuration to generate comprehensive reports on combined features. Both the License Monitor and historical reports display the combined usage of features for easy viewing and analysis.

# Configuring feature-mapping

  1. Open feature-mapping 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 products to combine with the following syntax:

    Mapping Syntax
    MAP: <Combined_Feature_Name>  
    <FeatureName_1>       
    <FeatureName_2>

    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: CombinedFeature 
    Feature032
    Feature052

    This example combines the usage of Feature032 and Feature052 and will be gathered through CombinedFeature.

    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 feature-mapping 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 products to combine with the following syntax:

    Mapping Syntax
    MAP: <Combined_Feature_Name>      
    <FeatureName_1>       
    <FeatureName_2>

    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: CombinedFeature    
    Feature032
    Feature052

    This example combines the usage of Feature032 and Feature052 and will be gathered through CombinedFeature.

    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.

Licpoll2

FlexLog2

Licenseevents

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