Special Handling of Oracle Java

FlexNet Manager Suite 2023 R1 (On-Premises)

The Oracle Java audit scan collects additional information on the Java installations found on the system being scanned - such as build type (for example, commercial), installation date, presence of the release file, and publisher. A full system scan can be performed to check for Oracle Java, and that special file evidence is collected and submitted as part of your OracleGLASEvidence.zip archive for reporting or as part of an audit response.

For your convenience, the standard FlexNet inventory agent (version 18.4.0 or later) is able to collect the required evidence, along with the additional files that Oracle requires, ready for inclusion in the OracleGLASEvidence.zip archive. This functionality is available in any of:

• The complete FlexNet inventory agent locally installed on a target inventory device
• The lightweight FlexNet Inventory Scanner, where the self-extracting executables are available on the target inventory device
• The zero footprint inventory collection method, where the necessary inventory components are downloaded from an inventory beacon, executed, and subsequently removed from the target inventory device.

(Details of these methods are available in Gathering FlexNet Inventory.)

However, because the full system scan on each inventory device (and resulting data uploads) can be time-consuming, this functionality is disabled by default. There are two stages of control available, both of which default to off (false):

• The Enable collection of Oracle Java audit data check box (located in Discovery & Inventory > Inventory Settings > Oracle audit data scanning) enables the inventory collection process.
• The Include Oracle Java (on the Inventory tab of the System Settings page) allows the uploaded data and files to be incorporated into the OracleGLASEvidence.zip archive.

When the first of these, the Enable collection of Oracle Java audit data check box, is selected:

1. The change is distributed through your inventory beacons as device policy to all managed inventory devices (those receiving device policy through any inventory beacon, and subsequently automatically uploading inventory through the inventory beacon hierarchy).
   Tip: This mechanism automatically updates locally-installed instances of FlexNet inventory agent, and the components on the inventory beacon used for zero footprint inventory collection. However, if you have deployed the lightweight FlexNet Inventory Scanner, ensure that you also update its associated copy of InventorySettings.xml, and if necessary update its command line with the -o PerformOracleJavaAuditScan=true option.
2. Each inventory device saves the downloaded preference in the PerformOracleJavaAuditScan preference in the registry (or pseudo-registry file on UNIX-like platforms).
   Tip: If you have disconnected inventory beacons, or inventory devices that are not managed automatically, you can arrange for your preferred registry tool to set this preference to true to enable this scanning by all locally-installed copies of FlexNet inventory agent.
3. If the FlexNet inventory agent needs to scan for file evidence (as authorized by the IncludeDirectory preference), it checks whether PerformOracleJavaAuditScan is True, and if so, it also scans each of the visited folders for the required Oracle Java evidence. Make sure the IncludeDirectory configuration covers all the folders that have Oracle Java installation or is set to Collect file evidence for all folders.
4. When the FlexNet inventory agent completes its regular (default: daily) inventory collection, including any required file evidence collection, it again checks whether PerformOracleJavaAuditScan is True, and if so, begins a scan in the folders that are specified in the IncludeDirectory preference for any remaining Oracle Java evidence.
5. Additional properties of Oracle Java on the inventory device are saved within the standard archived .ndi file.
6. As always, the inventory (.ndi) files are uploaded through your hierarchy of inventory beacons, and are eventually imported into FlexNet Manager Suite through the standard processes.
7. During import, the evidence for Oracle Java is processed and saved in the compliance database as installer evidence (not a typo – it is collected in the same manner as file evidence, but then presented as installer evidence, based on conversions found in InventorySettings.xml). Like all installer evidence, it can be linked to application records, which can in turn be linked to license records; and when appropriately configured, the nightly license compliance calculations include an assessment of consumption for Oracle Java applications. By default, this presentation of the uploaded data within FlexNet Manager Suite is the only use made of the uploaded data about Oracle Java applications.
8. However, once the Include Oracle Java check box is selected, the relevant uploaded data and files are also incorporated into the OracleGLASEvidence.zip archive (normally compiled after the nightly inventory import and license compliance calculations), ready for submission when an audit is required. This separation of control between the collection of inventory and its inclusion in the GLAS archive means you can collect the inventory, use it to correctly configure your application and license records, and correct any licensing oversights before you then save your corrected state, in case you need to submit it to Oracle in future.