I have a RHEL7 server with Oracle Java 8 and Weblogic 12 installed.
Java 8 was installed using an rpm from RedHat. Weblogic was installed using the installation package and instructions from Oracle (there was no rpm available from Redhat). During the Weblogic installation I supplied a symlink path as JAVA_HOME
, /usr/lib/jvm/java-oracle
.
When weblogic was installed, the symlink chain was:
/usr/lib/jvm/java-oracle
--> /etc/alternatives/java_sdk_oracle
--> /usr/lib/jvm/java-1.8.0-oracle-1.8.0.141-1jpp.1.el7_3.x86_64
.
I tried patching the Java 8 installation from update 141 to update 161 by installing a newer rpm from RedHat. After that Weblogic wouldn't start.
After some research I found that the Weblogic installation script had resolved the symlinks and hardcoded the target, /usr/lib/jvm/java-1.8.0-oracle-1.8.0.141-1jpp.1.el7_3.x86_64
into several configuration files under the weblogic installation directory.
The Java 8 update 161 installation removed update 141.
So it seems Java 8 and Weblogic have different opinions on how to locate Java.
Possible solutions:
Modify the configuration files in the Weblogic installation after patching Java.
Uninstall/reinstall Weblogic after patching Java.
Don't patch java.
other
Neither of the three first solutions seem very good.
What is the preferred way/best practice with regards to upgrading/patching java for Weblogic 12 on a Redhat server? Is there a better way?