You might know that JDeveloper is supported on 64 bit versions of Java and Windows since release 18.104.22.168. Fusion Middleware is supported on JDK7 both 11g and 12c versions since May 2012. So I decided to try to install an 64 bit JDK7, 64 bit JDeveloper on Windows 7 64 bit.
Since most of my JDeveloper work is aimed at SOA Suite, BPM and non-ADF Java, I choose the JDeveloper 11g IDE. On the JDK site I started with JDK7u6. However a security thingie got in the way and I switch to JDK7u7. I’m assuming you have a PC/laptop/VirtualMachine running a 64 bit version of Windows7.
Install JDK7 update 7
The latest JDeveloper support/certification info
- 64 bit JDK supported for Windows as of JDeveloper 22.214.171.124.0
- For JDK 6, update 24 or later is recommended
- For JDK 7, update 3 or later is recommended
However due to the security vulnerabilities in all earlier JDK 7 versions (on all OSes and their browsers) it is recommended to install only JDK7 update 7 and up.
Download JDK 7 for Windows 7 64bit. To install JDK7 on Windows7 double click the downloaded file.
Install JDeveloper 126.96.36.199
Since we have chosen a 64 bit JDK ourselves we downloading the
from OTN Developer Tools
Before installing we check whether the correct JDK version will be used (from the command prompt (cmd)):
java version "1.7.0_07"
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
And then to install JDeveloper from the command prompt (cmd):
C:\Users\deltalounge\Downloads>java -jar jdevstudio11116install.jar
Then a GUI starts and the most important screens are:
Install SOA Suite, BPM and AIA extensions
Follow the guidance of these post to install JDeveloper extensions
And you are ready to go.
Trying to keep up with Java versions that are supported for JDeveloper and SOA Suite, like in JDeveloper now supports 64 bit Windows and Java. Redstack pointed me to the OFM supported systems configurations that show that Fusion Middleware is supported on JDK7. The XLS showing certification with OS etc can be found:
Installing WebLogic Server on Ubuntu and JRockit 64 bits. This installation will later be used to install Oracle Service Bus.
Download the WebLogic Server installation files from OTN or E-Delivery.
Make sure the JAVA_HOME refers to the proper Java installation:
$ JAVA_HOME=/oracle/jrockit-jdk1.6.0_24 export JAVA_HOME
$ PATH=$JAVA_HOME/bin:$PATH; export PATH
Check that the proper Java version will be used:
$ java -version
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64, compiled mode)
If you are installing WebLogic Server on a 64-bit platform using a .jar installation program use the downloaded wlsversionnumber_generic.jar . Start the installation using the following command. Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK.
$ java -d64 -jar wls1035_generic.jar
- Welcome screen – Click
- Choose Middleware Home Directory – Create a new Middleware Home and enter the directory of your choice
- Register for Security Updates
- Choose Install Type – Choose Custom to be able to select the JDK of choice
- Choose Products and Components – No changes needed
- JDK Selection – Pick the JRockit JDK previously installed
- Choose Product Installation Directories – No changes needed
- Confirm Product Installation Directories
- Installer is running
- Installation complete
An overview of the WebLogic Server installation screen can be viewed in the gallery:
This post describes how to change the JDK for an Oracle Application Server 10.1.3.x installation. To check which JDK versions are supported with Application Server releases, check Metalink note 258833.1.
- Stop all running Application Server processess.
- Rename the current JDK directory:
mv jdk jdk.old
- Install or copy the JDK version you need into $ORACLE_HOME/jdk
- Start the Application Server processess.
You can check the JDK version:
$ /jdk/bin>./java -version
AIX 5L specials
If your systems are running AIX 5L there is some patching to be done. Assuming you’re using JDK 1.5 you have to apply patch 5261515.
After upgrading to a IBM JDK it is very well possible to run into the JAVAX.NET.SSL.SSLKEYEXCEPTION:RSA PREMASTER SECRET ERROR. In that case you have to modify the $ORACLE_HOM/jdk/jre/lib/security/java.security to
and create a symbolic link (or copy the jar) from the directory $ORACLE_HOME/jre/lib/ext/ibmjsseprovider2.jar to $ORACLE_HOME/jdk/jre/lib/ibmjsseprovider2.jar as described in Metalink note 746423.1.