# Excluding Vendor Licenses from Data Processing

# Introduction

Configure product-remove.map to eliminate specific vendor licenses from the data processing. This will ensure that unnecessary vendor licenses do not waste processing time, allowing for faster data processing.

# Configuring product-remove.map

  1. Open product-remove.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 the vendor license/s to remove with the following syntax:

    Mapping Syntax
    MAP: product_remove  
    VendorLicenseName1
    VendorLicenseName2
    VendorLicenseNameN

    The product_remove must not be changed.

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

    Example
    MAP: product_remove    
    VendorLicense372
    VendorLicense118
    VendorLicense112
    VendorLicenset928

    This example excludes VendorLicense372, VendorLicense118, VendorLicense112 and VendorLicense928 from data processing.

    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 product-remove.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 the vendor license/s to remove with the following syntax:

    Mapping Syntax
    MAP: product_remove  
    VendorLicenseName1
    VendorLicenseName2
    VendorLicenseNameN

    The product_remove must not be changed.

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

    Example
    MAP: product_remove    
    VendorLicense372
    VendorLicense118
    VendorLicense112
    VendorLicenset928

    This example excludes VendorLicense372, VendorLicense118, VendorLicense112 and VendorLicense928 from data processing.

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