Preface: Gathering FlexNet Inventory
Optimizing your software licenses requires that you can balance your purchased license entitlements against consumption of those entitlements. Consumption is calculated by examining hardware and software inventory — details about your computing devices as well as the applications installed (or used) on them.
- Inventory collected by third-party tools can be imported through adapters that normalize the data for use in FlexNet Manager Suite. There are several adapters supplied as standard (for example, see the FlexNet Manager Suite Inventory Adapters and Connectors Reference PDF file, available through the title page of online help), and it is also possible to build custom adapters to import data from other third-party tools (see The Inventory Adapter Studio chapter in the same PDF file).
- Some systems provide APIs that FlexNet Manager Suite can interrogate for inventory information.
- FlexNet Manager Suite also has a "native" ability to collect general-purpose inventory information, collectively called "FlexNet inventory" to distinguish it from inventory gathered through the other sources.
- In the specialized Kubernetes environment, FlexNet Manager Suite supports two independent, specialized agent for collecting inventory from Kubernetes environments. There is also a special tool to use "static analysis" (that is, to complete the process without interfering with any product containers) collecting software inventory from container images.
This document covers the various agents that are available for FlexNet Manager Suite, known as the FlexNet inventory agent (covered in Part 1), and the Flexera Kubernetes inventory agent and lightweight Kubernetes agent (covered in Part 2). The specialized script called imgtrack, built to run against the images that can instantiate containers and analyse the software that is available in the resulting containers, is covered in part 3.
FlexNet Manager Suite (On-Premises)
2022 R1