# Configuring Handle Remove

# Introduction

Configure handle-remove.map to remove handles from data processing. This will ensure that unnecessary handles do not waste processing time, allowing for faster data processing.

Apply the configurations shown in the Open iT server.

# Configuring `handle-remove.map`

Open handle-remove.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 handle name(s) with the following syntax:
Mapping Syntax
```
MAP: handle_remove  
HandleName1
HandleName2
HandleNameN
```
The handle_remove 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 Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Application' and 'application', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: handle_remove   
Firefox
Notepad
Calculator
```
This example removes Firefox, Notepad and Calculator from the data processing.

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 handle-remove.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 handle name(s) with the following syntax:
Mapping Syntax
```
MAP: handle_remove  
HandleName1
HandleName2
HandleNameN
```
The handle_remove 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 Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Application' and 'application', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: handle_remove
OpenWorks
RationalPurify
```
This example removes OpenWorks and RationalPurify from the data processing.

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.

Freeze

# Next Steps?

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

Data Generation

# Configuring Handle Remove

# Introduction

# Configuring handle-remove.map

# Next Steps?

# Configuring `handle-remove.map`