Dassault Systemes License Server (DSLS) Project Path to Project Name Mapping

Introduction

Configure project_name.map to set the DSLS Project Path to Project Name.

warning

Apply the configurations shown in the Open iT Core Server.

Open project_name.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 DSLS project path with the following syntax:
Mapping Syntax
```
MAP: <ProjectName>   
<ProjectPath1>
<ProjectPath2>
```
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 'Application' and 'application', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: Project1   
C:\application1*
C:\application5*
```
This example maps all project paths starting with C:\application1 and C:\application5 to Project1.

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.

Open project_name.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 DSLS project path with the following syntax:
Mapping Syntax
```
MAP: <ProjectName>  
<ProjectPath1>
<ProjectPath2>
```
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 'Application' and 'application', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: Project1   
/var/app1*
/var/app5
```
This example maps all project paths starting with /var/app1 and /var/app5 to Project1.

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.

This mapping may affect the following data type:

Licpoll2

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:

For historical reports: