# Vendor License Mapping

# Introduction

Vendor license mapping involves creating a new virtual vendor license alongside the existing ones while ensuring that the correct concurrency is calculated. This process is particularly useful when multiple raw vendor license names correspond to a single vendor license. The new virtual vendor license name should be visible in both the License Monitor and historical reports.

# Configuring product-mapping

  1. Open product-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:

    MAP: <Combined_Product_Name>     
    <ProductName_1>       
    <ProductName_2>

    Empty lines are allowed — any line beginning with # as the first non-white character is considered a comment. Globbing is also supported.

    Example
    MAP: CombinedProduct    
    Product032
    Product052

    This example combines the usage of Product032 and Product052 and will be gathered through CombinedProduct.

  3. Save the changes.

# Advanced Mapping

This mapping file allows excluding specific products to match general rules for mapping inclusion. It almost has the same behavior as regular mapping except for the following points:

  • It uses ADVMAP as keyword.
  • It uses a + (plus sign) for inclusions.
  • It uses a - (minus sign) for exclusions.

# Configuration

Example
ADVMAP: Product_Combined
+*;licsrv
-server01_legacy;licsrv

This example triggers the processing to include all products starting with anything and ending with licsrv, and exclude the specific product server01_legacy;licsrv.

The ADVMAP keyword is required to indicate that the entry is for advance mapping. It is recommended to start the entries with the most general match rule followed with the most specific match rules since entries are evaluated from bottom to top.

  1. Open product-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:

    MAP: <Combined_Product_Name>      
    <ProductName_1>       
    <ProductName_2>

    Empty lines are allowed — any line beginning with # as the first non-white character is considered a comment. Globbing is also supported.

    Example
    MAP: CombinedProduct   
    Product032
    Product052

    This example combines the usage of Product032 and Product052 and will be gathered through CombinedProduct.

  3. Save the changes.

# Advanced Mapping

This mapping file allows excluding specific products to match general rules for mapping inclusion. It almost has the same behavior as regular mapping except for the following points:

  • It uses ADVMAP as keyword.
  • It uses a + (plus sign) for inclusions.
  • It uses a - (minus sign) for exclusions.

# Configuration

Example
ADVMAP: Product_Combined
+*;licsrv
-server01_legacy;licsrv

This example triggers the processing to include all products starting with anything and ending with licsrv, and exclude the specific product server01_legacy;licsrv.

The ADVMAP keyword is required to indicate that the entry is for advance mapping. It is recommended to start the entries with the most general match rule followed with the most specific match rules since entries are evaluated from bottom to top.

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