# Setting the Number of Available Bentley Licenses

# Introduction

Configure bentley-available-licenses.map to set the number of licenses of Bentley features. The configured available license will be visible in the historical reports.

Apply the configurations shown in the Open iT server.

# Configuring `bentley-available-licenses.map`

Open bentley-available-licenses.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.
Specify the feature to rename with the following syntax:
```
MAP: NumberOfLicenses
Feature1\FeatureVersion1\Product1
Feature2\FeatureVersion2\Product2
Feature3\FeatureVersion3\Product3
```
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 'BentleyFeature' and 'bentleyfeature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: 25
MicroStation\*\Bentley*
```
This example sets 25 as the available licenses of all MicroStation features with any version and Product starting with Bentley.

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.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Open bentley-available-licenses.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.
Specify the feature to rename with the following syntax:
```
MAP: NumberOfLicenses
Feature1\FeatureVersion1\Product1
Feature2\FeatureVersion2\Product2
Feature3\FeatureVersion3\Product3
```
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 'BentleyFeature' and 'bentleyfeature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: 25
MicroStation\*\Bentley*
```
This example sets 25 as the available licenses of all MicroStation features with any version and Product starting with Bentley.

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.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Licusage

(126) License Peak Usage Distinct Host

# Next Steps?

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the historical reports.

Data Generation

# Setting the Number of Available Bentley Licenses

# Introduction

# Configuring bentley-available-licenses.map

# Next Steps?

# Configuring `bentley-available-licenses.map`