Switching JVM Versions with WebLogic

Just a quick post to talk about a trick to make it easier to switch JVM versions when working with WebLogic and other tools.  When running WebLogic on platforms other than Windows and Linux, or when using a 64-bit JVM it is necessary to install the JDK before installing WebLogic.  I recommend that you put the JVM you are going to use in the Middleware home.  For example if installing the Hot Spot JVM you may get a directory called <MW_HOME>/jdk1.6.0_24.  To make it easy to switch JVMs I recommend that you create a symbolic link to the actual JDK (ln –s jdk1.6.0_24 jdk1.6).  When installing WebLogic make sure that you point at the symbolic link.  Then when you get an updated version of the JDK (say build 25) then you can just change the link to point to the later version.

Note this approach needs a little more work to behave properly with multiple types of JDK (say JRockit and Hot Spot) and I will cover this in a later post.

Comments:

We have struggled to switch between JRockit and HotSpot, would love to understand what "little more work" involves :-)

Posted by guest on February 03, 2012 at 02:45 AM MST #

When using JRockit you need to make sure that the JDK providor in the startup scripts is set to be "Oracle" rather than "Sun". This will make sure that the JRockit flags are set rather than the Sun flags.

Posted by Antony on March 13, 2012 at 07:57 AM MDT #

Post a Comment:
Comments are closed for this entry.
About

Musings on Fusion Middleware and SOA Picture of Antony Antony works with customers across the US and Canada in implementing SOA and other Fusion Middleware solutions. Antony is the co-author of the SOA Suite 11g Developers Cookbook, the SOA Suite 11g Developers Guide and the SOA Suite Developers Guide.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today