Switching JDKs for JDeveloper/WLS Explained

The recent documentation update included a change of the required JDK for JDeveloper/WLS: instead of the bundled 32-bit JDK 1.6.0_24 the Developers Guide now advises to use the 64-bit version.

If you have worked with the 32-bit JDK so far, you may wonder how to make the switch.

The JDK that's being used by JDeveloper and integrated WLS is configured during installation time in a number of config files. jdev.conf and commEnv.cmd/sh are two examples.  Instead of trying to identify all those places both in the middleware homes and the WLS domains, the safest approach is to "start over" with a clean new install of JDeveloper/WLS and recreate the domain for the integrated WebLogic Server.

During the install of JDeveloper, you'll be asked to choose between "Complete" and "Custom" install type.  Choose "Custom" as this gives you the option of configuring JDeveloper/WLS with a JDK other than the one that's included with the installer.  Of course, this means that you should actually install the 64 bit JDK prior to running the JDeveloper installer.  You can find the 64-bit JDK (e.g., version 1.6.0_24) here.

Choose Custom Install to use an already installed 64-bit JDK

Choose Custom Install to use an already installed 64-bit JDK

In the JDK Section dialog, be sure to uncheck the bundled JDK and use the "Browse..." button to add the 64-bit JDK you want to use.

Changing the JDK to be used by JDeveloper/WLS

Changing the JDK to be used by JDeveloper/WLS

Then proceed with all the default options.

You can verify that JDeveloper is using the proper JDK by checking the jdev.conf file in %MW_HOME%/jdeveloper/jdev/bin.  You can also use the Help -> About dialog; the JDK is shown in the Properties tab.  Look for java.version and java.vm.name.

When you start the integrated WebLogic Server, it will display the Java version number it uses in the Console log pane:

 starting weblogic with Java version:

 java version "1.6.0_31"

 Java(TM) SE Runtime Environment (build 1.6.0_31-b05)

 Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode

 If you have a standalone WLS configured, it already uses a 64-bit version of the JRockit JVM, so there is no change required for it.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.

Search

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