Wednesday, March 23, 2011

FMW 11g – Upgrading Sun JDK

Recently I upgraded a Fusion Middleware Environment from 11.1.1.2 to 11.1.1.3.  As part of this, java had to be upgraded since the version I was on, 1.6.0_16 is not certified for 11.1.1.3.

I checked the Fusion documentation, WebLogic documentation and about the only thing I could find was:

Upgrading Sun JDK in the Oracle Home Directory

Basically it says to install the new JDK version in the same location as the existing JDK.  Well, that wouldn’t be a problem, other than in my infinite wisdom I installed it under the directory name jdk1.6.0_16.    Putting a new version, 1.6.0_22 in that directory could be confusing and not a best practice.  If I had my time back I would have named the directory jdk1.6 and this wouldn’t be an issue.

So how do I fix it?   I searched all the weblogic domain configuration files, startup scripts and console but could only find references to the JDK directory in two files.
  1. One reference in $WLS_HOME/common/bin/commEnv.sh

    JAVA_HOME="/var/u01/app/oracle/product/jdk1.6"

  2. Two references in $WEBLOGIC_DOMAIN_HOME/bin/setDomainEnv.sh

  3. SUN_JAVA_HOME="/var/u01/app/oracle/product/jdk1.6"             JAVA_HOME="/var/u01/app/oracle/product/jdk1.6"
    Note: If you have multiple weblogic domains you will need to change each domains setDomainEnv.sh file.
I bounced the domains and checked the start logs to verify that the new java home was being used.    For example, if I grep  the AdminServer log for my domain:

grep  jdk1.6 /u01/app/oracle/product/fmw11g/user_projects/domains/SOAdomain/servers/AdminServer/logs/AdminServer.log


now shows references to the new JDK home.  Some lines, but not all:

java.runtime.version = 1.6.0_22-b04
java.version = 1.6.0_22



You can grep it for your old version as well to make sure it isn’t being referenced.


Regards,
Sukhwinder Singh

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.

There was an error in this gadget