Cloud Pak licenses consist of multiple products that consume licenses by the number of products on each device. In non-production environments, the ratio of consumption of Cloud Pak licenses is typically half of what they are in a production environment. You can manage the consumption of CloudPak non-production licenses in different ways depending on your FlexNet Manager Suite version.
In FlexNet Manager Suite 2020 R2, allocations and overrides are possible at a license level for devices. The best practice for handling non-production environments on a Cloud Pak license is to create a separate test/dev version of the license, and then use allocations to control which license an install consumes from.
In FlexNet Manager Suite 2021 R1, you can perform per-product allocation and apply overrides on a product level. Instead of only allocating a device to the license, a prompt allows you to select which of the license’s products the allocation should apply to.
To perform per-product allocation and apply overrides on a product level:
Navigate to the License Compliance tab and locate the All Licenses option.
Locate the license that you would like to apply the overrides to.
Open the IBM VPC license.
NOTE: To perform per-product allocation and apply overrides on a product level, FlexNet Manager Suite must be in the 2021 R1 or a newer iteration.
Navigate to the Consumption tab.
Search for an inventory device using the Search bar.
Select the device. Then select the appropriate product and product conversion ratio below.
Select the blue Add Devices button.
Navigate to the overridden metric value column and fill in the value in the open text box. If you don't see this column, you can add it from the column picker by selecting the icon.
In the example below, vm2 has an overridden metric value of 10. This step is for overriding the value on a per-product basis. The overridden metric value is set on a per-product basis.
In the example below, both vms have 1 core, but the metric value for IBM App Connect on vm2 has been overridden to 10. This increases the metric of the host for IBM App Connect to 11 while retaining the value of 2 for IBM MQ on the same host.