#Vendor License Mapping
#Introduction
Vendor license mapping involves creating a new virtual vendor license alongside the existing ones while ensuring that the correct concurrency is calculated. This process is particularly useful when multiple raw vendor license names correspond to a single vendor license. The new virtual vendor license name should be visible in both the License Monitor and historical reports.
Apply the configurations shown in the Open iT server.
#Configuring product-mapping
Open
product-mapping
in the Configuration directory, which is by default inC:\Program Files\OpeniT\Core\Configuration
.Notice that it contains instructions on how to edit the file.
Specify products to combine with the following syntax:
Mapping SyntaxEmpty 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 'Vendor License' and 'vendor license', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleThis example combines the usage of Product032 and Product052 and will be gathered through CombinedProduct.
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.
#Advanced Mapping
This mapping file allows excluding specific products to match general rules for mapping inclusion. It almost has the same behavior as regular mapping except for the following points:
- It uses ADVMAP as keyword.
- It uses a + (plus sign) for inclusions.
- It uses a - (minus sign) for exclusions.
These prefixes are intended for advanced mapping only. These will not work for regular mapping setups.
#Configuration
This example triggers the processing to include all products starting with anything and ending with licsrv, and exclude the specific product server01_legacy;licsrv.
The ADVMAP keyword is required to indicate that the entry is for advance mapping. It is recommended to start the entries with the most general match rule followed with the most specific match rules since entries are evaluated from bottom to top.
Licpoll2
- (45) Total License Use v2.0
- (46) Individual License Use v2.0
- (47) Host License Use v2.0
- (49) Host User License Use
- (71) Usergroup License Use v2.0
- (72) Hostgroup License Use v2.0
- (93) OLAP Raw Hourly
- (94) OLAP User Concurrency
- (95) Usergroup License Use v3.0
- (102) OLAP Total Use
- (124) License Model User Concurrency
- (125) License Model Total Use
FlexLog2
- (50) Host User License Use Logfile
- (51) Total License Use Logfile
- (75) License Logfile Events
- (76) Total Queued Logfile
- (77) Individual Queued Logfile
- (83) Host License Use Logfile
- (84) Individual License Use Logfile
- (85) Usergroup License Use Logfile
- (86) Hostgroup License Use Logfile
Licenseevents
- (89) Total License Use Licenseevents
- (90) Individual License Use Licenseevents
- (91) Usergroup License Use Licenseevents
- (108) Host License Use Licenseevents
- (109) Hostgroup License Use Licenseevents
Licenseevents2
#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: