# Package Mapping

# Introduction

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

Apply the configurations shown in the Open iT server.

# Configuring `package-mapping`

Open package-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.
Specify packages to combine with the following syntax:
Mapping Syntax
```
MAP: <Combined_Package_Name>      
<PackageName_1>       
<PackageName_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 'Package' and 'package', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: CombinedPackage   
Package028
Package114
```
This example combines the usage of Package028 and Package114 and will be gathered through CombinedPackage.

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 package-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.
Specify packages to combine with the following syntax:
Mapping Syntax
```
MAP: <Combined_Package_Name>     
<PackageName_1>       
<PackageName_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 'Package' and 'package', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: CombinedPackage 
Package028
Package114
```
This example combines the usage of Package028 and Package114 and will be gathered through CombinedPackage.

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.

Licpoll2

FlexLog2

# 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

# Package Mapping

# Introduction

# Configuring package-mapping

# Next Steps?

# Configuring `package-mapping`