Skip to main content

Shared License Usage Measurements Configuration

Introduction​

Use the shared-licenses.map file to configure license sharing rules for supported license managers and features. During processing, Open iT automatically applies the configured rules to the corresponding license manager-specific mapping files.

Supported License Managers and Feature

License Managers​

  • CodeMeter
  • Reprise License Manager (RLM)

Features​

  • Carmaker

The following sections describe how to configure license sharing rules and apply the changes.

warning

Apply the configurations in the Open iT Core Server.

Configuring shared-licenses.map​

The shared-licenses.map file defines how a license manager handles licenses for sharing. Depending on whether you want to share licenses across both user and host, or by user-only, you must add the features to either the MAP: UH or MAP: U section. Use the instructions below to configure each mapping type.

Configuring User Host License Sharing (MAP: UH)​

Step 1: Open the Configuration directory​

  1. Go to the Configuration directory.

    By default, this is located at: C:\Program Files\OpeniT\Configuration.

Step 2: Configure the shared-licenses.map file​

  1. Locate the shared-licenses.map file and open it using your preferred text editor.

    The file contains additional instructions and examples for configuring license sharing rules.

  2. Add or update the feature mappings for user license sharing under MAP: UH.

    Mapping Syntax
    MAP: UH
    MyProduct;Daemon\DaemonName\FeatureName
    MyProduct;Daemon\*\*

    The value UH identifies user host license sharing and 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 Optimizing 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 for Codemeter
    MAP: UH
    *;codemeter*\*\*

    This example applies user host license sharing to all CodeMeter features on all hosts.

    Example for RLM
    MAP: UH
    WIN-HOST01;rlm\*\RLMFeature01

    This example applies user host license sharing to RLMFeature01 for all RLM daemons on the host WIN-HOST01;rlm.

    Example for Carmaker
    MAP: UH
    *;carmaker\*\*

    This example applies user host license sharing to all CarMaker features on all hosts.

    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.

Configuring User License Sharing (MAP: U)​

Step 1: Open the Configuration directory​

  1. Go to the Configuration directory.

    By default, this is located at: C:\Program Files\OpeniT\Configuration.

Step 2: Configure the shared-licenses.map file​

  1. Locate the shared-licenses.map file and open it using your preferred text editor.

    The file contains additional instructions and examples for configuring license sharing rules.

  2. Add or update the feature mappings for user license sharing under MAP: U.

    Mapping Syntax
    MAP: U
    MyProduct;Daemon\DaemonName\FeatureName
    MyProduct;Daemon\*\*

    The value U identifies user license sharing and 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 Optimizing 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 for Codemeter
    MAP: U
    *;codemeter*\*\*

    This example applies user license sharing to all CodeMeter features.

    Example for RLM
    MAP: U
    *;rlm\RLMDaemon\RLMFeature01
    *;rlm\RLMDaemon\RLMFeature02

    This example applies user license sharing to RLMFeature01 and RLMFeature02 under RLMDaemon.

    Example for Carmaker
    MAP: U
    *;carmaker\*\*

    This example applies user license sharing to all Carmaker features.

    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.

This mapping may affect the following data types:

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