#
Renaming Application Name for Collected URLs/ Page Titles
#
Introduction
Configure webdata-to-app.map
to map an application name for collected URLs and/or page titles to make reports more readable.
Apply the configurations shown in the Open iT server.
#
Configuring webdata-to-app.map
Open the
webdata-to-app.map
in the Configuration directory, which is by default inC:\Program Files\OpeniT\Core\Configuration
.Use the following format to map a URL or a web page title substring:
Mapping SyntaxMAP: <application name> *<URL substring>*\*<Title substring>\*
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.
The entries in the URL and title are case-sensitive. Also, note that leading and trailing spaces are removed from entries.
On the example, any URL with autodesk and autodesk360 on it and any page title with A360 on it will be mapped to Autodesk.
ExampleMAP: Autodesk # https://a360.autodesk.com/drive/ *autodesk*\*A360* *autodesk360*\*A360*
All the titles that contain LinkedIn with camel case, linkedin with small case, linkedIn with capital letter ‘I’, and Linkedin with capital letter ‘L’ with any URL will be mapped to LinkedIn.
ExampleMAP: LinkedIn *\*LinkedIn\* *\*linkedin\* *\*linkedIn\* *\*Linkedin\*
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 the
webdata-to-app.map
in the etc directory, which is by default in/var/opt/openit/etc
.Use the following format to map a URL or a web page title substring:
Mapping SyntaxMAP: <application name> *<URL substring>*\*<Title substring>\*
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.
The entries in the URL and title are case-sensitive. Also, note that leading and trailing spaces are removed from entries.
On the example, any URL with autodesk and autodesk360 on it and any page title with A360 on it will be mapped to Autodesk.
ExampleMAP: Autodesk # https://a360.autodesk.com/drive/ *autodesk*\*A360* *autodesk360*\*A360*
All the titles that contain LinkedIn with camel case, linkedin with small case, linkedIn with capital letter ‘I’, and Linkedin with capital letter ‘L’ with any URL will be mapped to LinkedIn.
ExampleMAP: LinkedIn *\*LinkedIn\* *\*linkedin\* *\*linkedIn\* *\*Linkedin\*
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.
Webappbrowserlog
- (120) Web App Browser Log
- (123) Web App Total Use
#
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: