#
Excluding Vendor Licenses from Data Processing
#
Introduction
Configure product-remove.map
to eliminate specific vendor licenses from the data processing. This will ensure that unnecessary vendor licenses do not waste processing time, allowing for faster data processing.
Apply the configurations shown in the Open iT server.
#
Configuring product-remove.map
Open
product-remove.map
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 the vendor license/s to remove with the following syntax:
Mapping SyntaxMAP: product_remove VendorLicenseName1 VendorLicenseName2 VendorLicenseNameN
The product_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 'VendorLicense' and 'vendorlicense', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: product_remove VendorLicense372 VendorLicense118 VendorLicense112 VendorLicenset928
This example excludes VendorLicense372, VendorLicense118, VendorLicense112 and VendorLicense928 from 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
product-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 the vendor license/s to remove with the following syntax:
Mapping SyntaxMAP: product_remove VendorLicenseName1 VendorLicenseName2 VendorLicenseNameN
The product_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 'VendorLicense' and 'vendorlicense', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: product_remove VendorLicense372 VendorLicense118 VendorLicense112 VendorLicenset928
This example excludes VendorLicense372, VendorLicense118, VendorLicense112 and VendorLicense928 from 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.
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
- (85) 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 historical reports: