Oracle Java Scanning

IT Asset Management (Cloud)

Using either a User license type or an Oracle Processor license type, Oracle Java may be licensed in either of two ways:

• It may consume from its own license
• It may be covered by a license for a 'parent' application, such as Oracle SQL Developer, so that it does not consume from its own license.

To configure the latter case, you:

• Set the Import detailed evidence check box on the General tab of the application properties
• Ensure that only file evidence is attached to the application for recognition (with no installer evidence or WMI evidence attached)
• Declare the file path(s) on target devices where that file evidence is installed in the Exemption by file path listing, in the Exemptions section of the Use Rights & Rules tab of the linked license
• Set the Enable collection of Oracle Java audit data check box on this page, as described below
• Set the Include Oracle Java check box (on the Inventory tab of the IT Asset Management Settings General page), which allows the uploaded data to be incorporated into the OracleGLASEvidence.zip archive, ready for submission when an audit is required. You may also control data obfuscation in the audit archive (see System Settings: Inventory Tab).

Once enabled, the FlexNet Inventory Agent can collect the appropriate inventory using either:

• The FlexNet Inventory Agent installed locally on the device where the Oracle Java is running
• The zero footprint inventory collection method, where the main part of the FlexNet Inventory Agent (ndtrack) is temporarily downloaded from a nearby inventory beacon, executed, and subsequently removed.

(You can learn more about methods of collecting FlexNet inventory in Gathering FlexNet Inventory.)

Tip: IT Asset Management is verified by Oracle for collection and reporting of inventory for Oracle Java.

In normal operation, both the previously-mentioned check boxes should be selected, and left 'on' forever. However, it is possible that, while rolling out this functionality, you want to turn on the data collection now for testing and inspection; and only include the results in the audit archive when you have adequate agent coverage of the relevant servers, and have configured all the required licenses.

Tip: This data collection requires FlexNet Inventory Agent version 18.4.0 or later. Earlier versions of the FlexNet Inventory Agent simply ignore the setting, and so may continue to be used in other environments where Oracle Java is not in play.

To authorize collection of Oracle Java inventory:

1. Ensure that the FlexNet Inventory Agent installed on the appropriate Oracle server(s) has been updated to version 18.4.0 or later. For zero footprint inventory collection, the simplest path is to upgrade the appropriate inventory beacon(s) to version 18.4.0 or later, as this also updates the embedded version of the FlexNet Inventory Agent.
2. Go to the Inventory Settings page.
3. Scroll down and ensure that the Oracle audit data scanning section of the page is expanded (if necessary, click the expansion button on the far right of the section heading).
4. Select the Enable collection of Oracle Java audit data check box.
5. Scroll to the bottom of the page, and click Save to commit your change.
6. Wait a day or two.
   This allows for the new setting to be distributed to each inventory beacon as a beacon policy update (by default, these updates are requested and delivered each morning); and thereafter each installed FlexNet Inventory Agent receives the new setting when it requests a device policy update from its preferred inventory beacon. Then there must be sufficient time for inventory collection and upload, followed by the nightly inventory import and license consumption calculations.
7. When inventory data is reliably uploading for the appropriate devices, remember to also visit the IT Asset Management Settings General page and select the Include Oracle Java check box, so that the inventory data is available for audit on demand.
8. Look for newly uploaded evidence for Oracle Java.

   The Oracle Java audit data can be reviewed and verified in the generated archive.

   The detailed information about all your installed instances of Oracle Java is also available in the Oracle Java Worksheet report. See Oracle Java Worksheet Report.

9. Before sending over the audit data CSV files to Oracle, check that the data is correct. In particular, make sure the Machine Type and Environment Type fields are filled in correctly. Also check the Part of other product field; this field is determined by the Java installation’s associated license and by the configuration for the Exemption by file path listing.
   Attention: The following columns are filled in with N by default by the system; therefore, you should double-check whether the values are correct or need to be adjusted:

   Field	Description
   BCL	Set this field to Y if the installation is under the Binary Code License (BCL) development license grant; otherwise, set it to N.
   BLRA	Set this field to Y if the installation is under the Binary License and Redistribution Agreement (BLRA); otherwise, set it to N.
   NFTC	Set this field to Y if the installation is under the No-Fee Terms and Conditions (NFTC) license agreement; otherwise, set it to N.
   Support required	Set this field to Y if the installation is under the Oracle Technology Network (OTN) license agreement; otherwise, set it to N.
   Used with OCI	Set this field to Y if the installation is included in an OCI subscription; otherwise, set it to N.