Editing Inventory Agent Common Settings

The Common Settings section lets you specify configuration options that apply for all agent configurations. Specifically, these settings are where you control the following options for all agents:

•

Inventory Extensions Versions

•

Oracle Audit Data Scanning

•

Container Scanning

•

Frequent Hardware Scanning for IBM Sub-capacity License Calculations

•

Inventory from VMware vCenter or Oracle VM Manager Servers

•

Inventory from IBM PVU Groups

•

Encryption

Important:These configuration settings can only be edited in the agent’s Default Configuration. They cannot be changed from within a different agent configuration.

To configure Common Settings:

Go to Agent Configurations (Data Collection > IT Visibility Inventory Tasks > Agent Configurations).

The Agent Configurations screen appears.

Click the Default agent configuration tile to edit its configuration.

The default agent configuration appears.

Open Inventory Agent Options and click Edit at the far right of the Common Settings section.

The Common Settings section expands.

Edit settings for Inventory Extensions Versions. Choose to use either the most recent version of the Inventory extensions or to use the currently approved version:

•

Use latest version (currently n)

•

Use approved version (currently n)

To download the currently selected version of the Inventory extensions version, click Download Selected.

To alter the current approved version of the Inventory extensions, click Manage Versions. For details on approving and archiving Inventory extensions versions, see Managing Inventory Extensions Versions.

To enable scanning of Oracle audit data, select the following checkboxes:

•

Enable collection of Oracle Fusion Middleware audit data

For additional information about collecting Oracle Fusion Middleware inventory, see Scanning Oracle Fusion Middleware Inventory Reference for Inventory Agent Options.

•

Enable collection of Oracle Java audit data

•

Enable collection of Oracle EBS audit data

Note:Collection of Oracle E-Business Suite (EBS) audit data requires inventory agent version 22.0.0 or later and InventorySettings.xml version 75 or later. For information about how to control the version of the agent to be deployed, see Editing Inventory Agent Options. For information about how to control the version of the InventorySettings.xml file that is used by the inventory agent, see Managing Inventory Extensions Versions.

To enable detection when running an inventory agent inside of a Docker container, select Enable detection.

Edit IBM Reporting and Archiving Settings.

•

Edit settings for Frequent hardware scanning for IBM sub-capacity license calculations.

Setting	Description
Enable Scanning	Select this checkbox to enable frequent scanning for IBM sub-capacity license calculations. When you enable scanning, the agents using this configuration will perform scans based on the interval you specify in the Perform Extra Inventory Scanning Every setting.
Perform Extra Inventory Scanning Every	Specifies the frequency at which agents based on this configuration will perform extra inventory scanning. Choose from 30 Minutes, 1 Hour, 2 Hour, or 4 Hour. When you specify a setting other than the recommended 30 minute interval, Flexera One asks you to confirm you want to use the new value.

Setting

Description

Enable Scanning

Select this checkbox to enable frequent scanning for IBM sub-capacity license calculations. When you enable scanning, the agents using this configuration will perform scans based on the interval you specify in the Perform Extra Inventory Scanning Every setting.

Perform Extra Inventory Scanning Every

Specifies the frequency at which agents based on this configuration will perform extra inventory scanning. Choose from 30 Minutes, 1 Hour, 2 Hour, or 4 Hour.

When you specify a setting other than the recommended 30 minute interval, Flexera One asks you to confirm you want to use the new value.

These frequent-scanning settings also change compliance properties for relevant licenses—invalidating consumption figures until the next full reconciliation.

•

Edit settings for Inventory from VMware vCenter or Oracle VM Manager Servers. You can add or remove groups for which the agents based on this configuration will perform IBM PVU inventory scans.

•

To add a group, click Select. This button shows a slide-out for VMware vCentres and Oracle VM Manager Servers. Click the checkboxes for the groups you want to add; then click Select.

•

To remove an existing group, click the X in the group name.

These settings enable IBM PVU inventory scans for the selected Oracle VM Manager and VMware vCenter groups.

•

Edit settings for Inventory from IBM PVU groups. You can add or remove IBM PVU inventory groups for which the agents based on this configuration will perform IBM PVU inventory scans.

•

To add a group, click Select. This button shows a slide-out for IBM Inventory Groups. Click the checkboxes for the groups you want to add; then click Select.

•

To remove an existing group, click the X in the group name.

•

To create a new inventory group, click Create a New Inventory Group.

These settings enable IBM PVU inventory scans for the selected IBM PVU inventory groups.

Edit the setting for Encryption.

Select the Enable Encryption checkbox to activate encryption of inventory files being collected by agents based on this configuration. This option encrypts the inventory data on the machine hosting the agent and helps prevent inventory files from being viewed or modified by malicious actors. The AES 256-bit encryption of inventory files collected by the agent (as well as from the beacon through remote execution) includes the following files:

•

NDI, MMI, disco.gz, and swacc files generated by the Flexera Agent

•

NDI, disco.gz, activity, and bstat files generated by the Flexera Beacon

Note:To use this encryption capability, all of the agents and beacons in your environment must be upgraded to at least version 21.0.

Click Save.

Your changes are saved to a database, over-writing the previous settings. At the next request for any updated beacon policy (inventory beacons check for updates by default every 15 minutes), the latest settings are deployed, along with any new update packages. Thereafter, when an inventory device checks for updated policy (which happens daily at a random time between 5 a.m. and 6 a.m. local time for operational agents), affected platforms receive the changed policy and download any new upgrade packages required. Once Inventory Agent has both the policy update and the required package available, it waits for any of its current processes to complete, and then launches an installation of the specified package, which results in its version being either upgraded or downgraded. On successful completion of the process, Inventory Agent resumes normal processing to ensure that it meets the requirements specified in its device policy. Its next uploaded inventory reports the newly-installed version of itself.

These process cycles suggest that, for scenarios that require a series of changes to these settings, you should leave an interval of at least 48 hours between changes.

Note:For policy-based upgrades, the method of originally deploying Inventory Agent, whether by the Adopted method or by Agent third-party deployment, is not relevant. If it uploads to a connected inventory beacon, it is controlled by policy, and managed from this page. If you have a disconnected inventory beacon, or if you have separately deployed core components rather than the full Inventory Agent, you must manage their upgrades separately. For more information, see Gathering FlexNet Inventory.