About Updating the JDK Location After Installing an Oracle Fusion Middleware Product

The binaries and other metadata and utility scripts in the Oracle home and Domain home, such as RCU or Configuration Wizard, use a JDK version that was used while installing the software and continue to refer to the same version of the JDK. The JDK path is stored in a variable called JAVA_HOME which is centrally located in .globalEnv.properties file inside the ORACLE_HOME/oui directory.

The utility scripts such as config.sh|cmd, launch.sh, or opatch reside in the ORACLE_HOME, and when you invoke them, they refer to the JAVA_HOME variable located in .globalEnv.properties file. To point these scripts and utilities to the newer version of JDK, you must update the value of the JAVA_HOME variable in the .globalEnv.properties file by following the directions listed in Updating the JDK Location in an Existing Oracle Home.

To make the scripts and files in your Domain home directory point to the newer version of the JDK, you can follow one of the following approaches:

• Specify the path to the newer JDK on the Domain Mode and JDK screen while running the Configuration Wizard.

  For example, consider that you installed Oracle Fusion Middleware Infrastructure with the JDK version 8u191. So while configuring the WebLogic domain with the Configuration Assistant, you can select the path to the newer JDK on the Domain Mode and JDK screen of the Configuration Wizard. Example: /scratch/jdk/jdk1.8.0_211.

• Manually locate the files that have references to the JDK using grep (UNIX) or findstr (Windows) commands and update each reference. See Updating the JDK Location in an Existing Oracle Home.

Note:

If you install the newer version of the JDK in the same location as the existing JDK by overwriting the files, then you don’t need to take any action.

When you upgrade Oracle Identity Manager in an integrated environment, you may encounter the OPSS processing error. The following exception is seen when you run reconfig.sh command to reconfigure the Oracle Identity Manager domain:

SEVERE [93] com.oracle.cie.domain.progress.AbstractProgressGenerator - Error occurred in 
phase {OPSS Processing} execution. 
java.lang.IllegalStateException: SecurityContext: Domain Name: IAMGovernanceDomain 
JDBC URL: opss-audit-DBDS:jdbc:oracle:thin:@//slc03rmj:1521/IDMDB 
JDBC URL: opss-data-source:jdbc:oracle:thin:@//slc03rmj:1521/idmdb 
le.com 
Caused by: java.security.InvalidKeyException: Illegal key size         
at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1039)         
at javax.crypto.Cipher.implInit(Cipher.java:805)         
at javax.crypto.Cipher.chooseProvider(Cipher.java:864)         
at javax.crypto.Cipher.init(Cipher.java:1396)         
at javax.crypto.Cipher.init(Cipher.java:1327)

To resolve this issue:

1. Install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files from the following location: Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 Download.

2. Copy the local_policy.jar and the US_export_policy.jar files to the location JAVA_HOME/jre/lib/security/. If the files already exist in the destination folder, overwrite them.

• Updating the JDK Location in an Existing Oracle Home
  The getProperty.sh|cmd script displays the value of a variable, such as JAVA_HOME, from the .globalEnv.properties file. The setProperty.sh|cmd script is used to set the value of variables, such as OLD_JAVA_HOME or JAVA_HOME that contain the locations of old and new JDKs in the .globalEnv.properties file.
• Updating the JDK Location in an Existing Domain Home
  You must search the references to the current JDK, for example 1.8.0_191 manually, and replace those instances with the location of the new JDK.