1. Download the latest JRockit version from Oracle and install it.
2. Shutdown all the WebLogic server instances (E.g. OIM, SOA, AdminServer) and Node Manager processes.
3. Update JAVA_HOME variable in the following files:
- User Bash Profile (E.g. "~/.bash_profile")
- $MW_HOME/wlserver_10.3/common/bin/commEnv.sh
- $MW_HOME/user_projects/domains/<domainName>/bin/setDomainEnv.sh
(Also modify BEA_JAVA_HOME variable) - $MW_HOME/utils/bsu/bsu.sh
- $MW_HOME/utils/quickstart/quickstart.sh
- $MW_HOME/utils/uninstall/uninstall.sh
4. Update "javaHome" and "JavaHome" parameters in the node manager properties file.
- $MW_HOME/wlserver_10.3/common/nodemanager/nodemanager.properties
5. Edit OIM design console script to use the new JRockit path.
- $MW_HOME/Oracle_IDM1/designconsole/xlclient.sh
6. Restart the operating system.
7. Validate the new java version is running.
- java -version
- which java
- Check server instances and nodemanager logs to see if correct JRockit version is running
Side Note:
In Unix, you can execute the following command to see if any shell scripts files still reference the old java home path:
# Replace JAVA_HOME with absolute path to java home directory find . -type f -name "*.sh" -exec grep -il JAVA_HOME {} \;
Is there anything wrong with just renaming your existing jrockit folder, creating a new folder with the old name and copying the package there? It seems like modifying all of these config files is a much riskier path.
ReplyDeleteI was able to install the new JDK version using the old JDK path. The Oracle Support documentation in my comment below mentions that as another approach.
DeleteThis post is helpful. I find an Oracle Support documentation that is very useful: "How to Upgrade the JDK Used by Oracle WebLogic Server 11g to a Different Version (Doc ID 1309855.1)".
ReplyDelete