The FlexNet Inventory Agent

IT Asset Management (Cloud)

After an introductory matrix comparing the results you may expect from various inventory sources, the remainder of this part is solely concerned with the collection of FlexNet inventory using the FlexNet Inventory Agent.

Tip: This does not include collection of inventory from servers in Kubernetes clusters. For that functionality, see part II, covering Two FlexNet Kubernetes Agents.

Learning about FlexNet inventory gathering involves understanding different configurations of the code elements that gather the inventory. As well, where these code elements are deployed influences both the capabilities and the management requirements of the system. In fact, even the methods of deployment can have some influence.

For these reasons, the first chapter in this part summarizes these factors to arrive at a standard nomenclature, used consistently throughout this document. There is also an overview of some key scenarios to help you choose which combination of code elements, deployment location, and deployment method you need.

The following chapters each treat just one of the resulting "cases". Comparable details are provided for each of the cases. The concept here is to simplify your reading. Instead of needing to tease out from mixed documentation which data point applies to your case, you need read only the one chapter that applies to your case. It contains the relevant data points exclusively for that case. (Since there is considerable overlap between the cases, this makes the document overall rather repetitive. Fortunately, you do not need to read it all. It is a reference work, not a narrative.) Notice further that each case's Details chapter includes topics for:

• The Normal Operation expected for the case — this may help you make your final choice about the method(s) of gathering FlexNet inventory that you will use in your enterprise
• The System Requirements specific to this case
• The Accounts and Privileges required for the case
• The Implementation used for this case (for example, how to deploy the code entities for the case, if deployment is in fact required)
• Troubleshooting comments applicable to the case.

Those chapters are followed by one that covers material that is common to all cases. You may choose topics from the Common: Details chapter selectively, if they apply to your environment.

To complete the part, there are chapters of reference material covering the command lines for key code elements, and a significant number of preference settings that can control the behavior of those code elements.

But first, we need a clear understanding and nomenclature, covered in the first chapter.