Excluding already licensed Oracle Java products from automatic creation of license requirements
Overview
Copies of Java products that are shipped with applications for restricted use must not be licensed separately.
You can use a dedicated feature to prevent the system from creating effective license requirements in such cases. You simply need to specify a list of binary directory path fragments for Java Product copies that are bundled with third-party applications in order for them to be excluded.
How to enable exclusions for the automatic creation of license requirements
The system allows to specify software binary path fragments that will be used as patterns to find fingerprints that need to be assigned to a dedicated software product with a "free of charge" license model.
To define path fragments which will be used for preventing the creation of effective license requirements:
- Navigate to Settings in the Oracle Compliance application.
- Click the Edit button.
- In the Excluded Licensed Java Products grid under Java Products Settings, add the path fragments using the following format: /mypath/mypath/, where mypath/mypath/ stays for the directory path fragment of a Java application. You can find this path for each Java application in the Path to Binary column of the Java Products navigation item grid.
You can add either the whole path or a part of it. For example, if you enter a top level path fragment like /opt/, the system will filter Java applications with paths like "/opt/java1.4/bin/java", "/opt/hpservices/jre/opt/java1.4/jre/bin/PA_RISC/java", and others that contain /opt/.
Add as many path fragments as necessary.
- Save the changes.
If there are any Java products that match the specified path fragments, the Excluded Licensed Java Products link on the Settings preview will display the number of found records.
Click the link to open the list of filtered Java products.
For installations where the Java path matches one of the specified white list patterns, a second fingerprint with the "[licensed copy]" suffix in the application name will be created. This fingerprint will be linked to the corresponding device while the original fingerprint will not have any device linked.
Next LIS update will assign the licensed copy fingerprints to a dedicated software product Java Runtime Environment (OEM) with the Oracle | Java SE - Licensed OEM license model. This license model requires 0 usage rights, and therefore the license requirements for such fingerprints will be created with a quantity of zero.