Configure Appropriate Licenses
Naturally, you require appropriate license records of type IBM PVU or IBM VPC for all relevant IBM software. Less self-evident is that the license(s) must be operational (that is, have consumption recorded against them) before you can configure them to meet IBM's special requirements for high-frequency scanning. This makes it convenient to have the license(s) in place before you collect your first (or next) inventory from the computers running the relevant IBM software. In this way, the initial inventory collection and license reconciliation can immediately make your IBM sub-capacity license(s) operational, showing consumption against the linked application(s), and enabling the special configuration required for sub-capacity licensing.
- Region 1: North America and South America
- Region 2: Europe and Africa
- Region 3: Asia and Australia.
- Ensure that you have set up enterprise groups based on location that can roll up into the appropriate IBM regions. (If you do not use locations for other purposes, it may be sufficient to set up just the top three, one per region.) For details, see Configuring Regions for IBM.
- Assign the inventory devices consuming PVU points or VPC entitlements to an appropriate enterprise group (location), as noted at the end of Configuring Regions for IBM.
- Best practice is to create just one IBM sub-capacity license worldwide
for each product (or bundle). This allows for the correct tracking of
points/entitlements across regions, and for correct totalling of the
liability for the license. Tip: If you have strong reasons for maintaining multiple licenses per product (such as a history of mergers and acquisitions leading to separate reporting to IBM for different entities), use a different kind of enterprise group, such as corporate units, to separate purchases and licenses into the appropriate corporate structure. Overlay the same system of locations described here so that device consumption is correctly rolled up into regions for each of your corporate divisions.
One additional factor to consider is whether to create single product or multi-product licenses (the latter are used to track software bundles). If your licenses were created automatically to match imports from ILMT, bundles are (by default) automatically matched. This is also the case if your purchase includes a SKU that identifies a bundle. A multi-product license shows applications in the Applications tab that list multiple values in the Product column (which is why it is called a multi-product license); and the Use rights & rules tab is also configured differently, showing the use rights for each product, including whether each one is primary or supplementary. Supplementary products can be configured so that they do not consume license entitlements, being covered by the licensed primary product. If you are manually configuring license use rights and restrictions, a useful resource is the License Information Document (LID) for your product. You can search for these LIDs on the IBM’s License Information Document Search page.
To create licenses by processing purchases (summary):
FlexNet Manager Suite (On-Premises)
2023 R1