Sentinel Vendor License Identification with SMT Versions
Introduction
Configure sentinel-products.map to identify which Sentinel vendor licenses contain features with SMT Versions. The Feature Version "SMT" is the sum of all feature versions.
Apply the configurations shown in the Open iT Core Server.
Configuring sentinel-products.map
- Windows
- Unix
-
Open
sentinel-products.mapin 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 Sentinel vendor licenses with the following syntax:
Mapping SyntaxMAP: <SENTINEL_VENDORLICENSE>
*;sentinelEmpty 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 'VendorLicense' and 'vendorlicense', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: SentinelVendorLicense1
*;sentinelYou 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
sentinel-products.mapin 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 Sentinel vendor licenses with the following syntax:
Mapping SyntaxMAP: <SENTINEL_VENDORLICENSE>
*;sentinelEmpty 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 'VendorLicense' and 'vendorlicense', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: SentinelVendorLicense1
*;sentinelYou 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 types:
Licpoll2
- (45) Total License Use v2.0
- (46) Individual License Use v2.0
- (47) Host License Use v2.0
- (49) Host User License Use
- (60) Total License Queued
- (61) Individual License Queued
- (71) Usergroup License Use v2.0
- (72) Hostgroup License Use v2.0
- (93) OLAP Raw Hourly
- (94) OLAP User Concurrency
- (102) OLAP Total Use
- (103) OLAP Featureset PPU
- (111) Total License Use Appversion
- (113) Usergroup License Use Appversion
- (114) Total PPU License Use
- (115) Hostgroup License Use v3.0
- (124) License Model User Concurrency
- (125) License Model Total Usage
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:
For historical reports: