# Package Renaming

# Introduction

This feature allows administrators to convert cryptic package names into easily understandable, readable names. The new package name will be visible in the License Monitor and historical reports.

Apply the configurations shown in the Open iT server.

# Configuring `package-rename.map`

Open package-rename.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 product/s to rename with the following syntax:
Mapping Syntax
```
MAP: NewPackageName 
OldPackageName
```
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: Package635
Package325
```
This example renames all of the Package325 packages to Package635.

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-rename.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 product/s to rename with the following syntax:
Mapping Syntax
```
MAP: NewPackageName 
OldPackageName
```
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: Package635
Package325
```
This example renames all of the Package325 packages to Package635.

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.

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

# Introduction

# Configuring package-rename.map

# Next Steps?

# Configuring `package-rename.map`