Advanced Configuration

FlexNet Manager Suite 2022 R1 (On-Premises)

This topic is not required for normal operation of imports of IBM PVU license consumption results from ILMT. These advanced configuration options are for those who want to override the automated processes, and manage the required data manually. Because this requirement is so rare, the configuration options are not available through the web interface for FlexNet Manager Suite, and modifying the settings requires direct intervention in the compliance database.

Two settings are available to modify the behavior of FlexNet Manager Suite when importing from ILMT:

• AutoCreatePVULicenses is a Boolean (values 0 or 1, default value 1).
  • When AutoCreatePVULicenses = 1, if an application imported from ILMT is matched by an existing application record (either one from the Application Recognition Library or one created earlier within your enterprise), but this application is not yet linked to an IBM PVU license, a new license record is created in FlexNet Manager Suite and linked to the application. The individual devices recorded in ILMT as having this application installed are also imported and listed on the Consumption tab of the new license properties. Because sub-capacity points are not being calculated by FlexNet Manager Suite, the points consumption is also imported from ILMT and recorded on this license record. Automatic creation of the license is highly desirable because, in FlexNet Manager Suite, consumption can only be recorded a license; and application bundles are also recorded against licenses (keeping in mind that a given application may be licensed on its own, or as part of a bundle, so that the license is the logical home for bundling information, recorded in a multi-product license). It is best practice to leave this default value in place.
  • When AutoCreatePVULicenses = 0, missing licenses are not created during an import from ILMT. (However, if an IBM PVU license for the application already existed prior to the import, and sub-capacity points are not being calculated by FlexNet Manager Suite, this setting does not prevent the update of consumption figures or consuming devices on the pre-existing license.) Since the missing license is not automatically created, there is nowhere to record related consumption results or consuming devices, nor to record any bundling information. This results in data loss from the import. However, if the ILMT import revealed bundling relationships, these are stored internally in the database (although nowhere visible through the web interface). If, subsequently, you manually create a license for the primary product, and a second and separate license for the supplementary product, this second license automatically defaults to zero consumption because the linked application is known to be a supplementary product in a bundle within ILMT, where it consumes zero points.
• ImportILMTBundle is a Boolean (values 0 or 1, default value 1). This setting only has meaning when AutoCreatePVULicenses = 1, and its value is ignored when AutoCreatePVULicenses = 0. Therefore, when AutoCreatePVULicenses = 1, and:
  • When ImportILMTBundle = 1, and the import from ILMT shows applications in a bundle relationship, the created license is a multi-product license, and both applications are linked to it (the one for which ILMT consumed points is primary, and the one(s) for which ILMT consumed zero points are supplementary). If the import from ILMT does not include any bundling information, a single-product license is created. It is best practice to leave this default value in place.
  • When ImportILMTBundle = 0, created licenses are always single-product licenses, and any bundling information from ILMT is discarded. This results in data loss from the import.

To change preference values:

1. On your database server, in SQL Server Management Studio, open your compliance database.
2. To prevent import of bundling data from ILMT, run the following SQL command to set ImportILMTBundle to zero (false):

   update ComplianceTenantSetting set SettingValue = 0 where SettingNameID = 181;

   Remember that, for this setting to have any effect, AutoCreatePVULicenses must be set to 1 (the default).
3. To prevent the creation of missing IBM PVU licenses during imports from ILMT, run the following SQL command to set AutoCreatePVULicenses to zero (false):

   update ComplianceTenantSetting set SettingValue = 0 where SettingNameID = 90;