Oracle JRE Multiple Instances

Learn about Oracle JRE, a widely used software that can have multiple instances on a single endpoint. To support accurate detection and smooth patching of all Oracle JRE installations that were done using TAR.GZ or ZIP or EXE or MSI packages, BigFix uses the Middleware Scanner. This scanner discovers all installed Oracle JRE versions and installation paths, while the patching process updates outdated versions in a single execution.

Note: This workflow applies only to Oracle JRE installations that use tarball packages for non-windows systems and zip, msi, or exe based packages for windows. Upgrades for deb and rpm based package installations continue to use their respective native BigFix Fixlets and do not require the Middleware Scanner.

Scanner Process

For running the scans on every software version, refer to BigFix Scanner for Middleware Application. These results are then used by the Oracle JRE patching tasks to determine which instances require updates.

Note: Before you start patching, it is recommended that you back up all custom configurations, instance files, and environment-specific settings. This helps you restore custom settings if needed after patching.

Patching Process

The Oracle JRE patching task uses the scanner results to identify lower versions and update them to the patch version specified in the task.

Select the applicable computer in the BigFix Console to review the installed versions.
When you take action on the endpoint, the patching task reads the results.xml and identifies all Oracle JRE instances.
All outdated or lower Oracle JRE versions are updated in a single execution, including:
Recommended:
If only one instance is found, that specific instance is patched.

If multiple instances are found, for example, five, the task goes through all five instances and tries to patch them all in a single run.
If the installed version is the same or higher, then patching is skipped.
Note:
- Services must be stopped before patching starts and restarted after patching is complete.
- Registry keys are not updated during patching. Only the necessary folders are copied during patching.

Exit codes and their meanings

When you perform tasks such as patching or extracting files in Oracle JRE, certain exit codes may be returned to show the result of the operation. These codes help identify problems during the installation or update process. The following list shows common exit codes, their meanings, and suggested actions to fix the issues.

Note: Oracle JRE checks its version using Oracle ./java.exe -version or ./java -version. Make sure that all required prerequisites are met before you continue.

Table 1. Exit codes and their meanings
Exit code	Action
Exit Code 0: Success	You can check the locations of patched instances in `middleware/java/vulnerable_paths_OracleJRE_<version>.txt` file.
Exit Code 11: Archive extraction failed	Archive extraction failed (for example, corrupt tar or out of disk space).
Exit Code 12: Source payload missing	The extracted archive did not contain the expected root folder. Ensure the correct file exists at the specified location.
Exit Code 13: Patching of one or more instances failed	Check the local `patch_java_OracleJRE_<version>.log` file.

Note: After a successful execution, run the middleware scanner task again to check the latest versions.