Running JRE7 alongside JRE6 for Oracle Forms

Nov 19, 2013 / By Vasu Balla

Tags: , ,

DBAs working in a managed services environment often run into situations where some customers are still running JRE6 while others have upgraded to latest JRE7. When JRE7 is installed on a Windows desktop, it becomes the default JRE and gets invoked when users access Oracle forms. This creates all kinds of issues for users who try to access Oracle forms from customers who are still on JRE6.

This blog describes a way to access Oracle E-Business Suite (EBS) forms running on JRE7 and, at the same time, other EBS forms running on JRE6. This method has been tested on Windows 7 64bit running on laptops and desktops.  The reason this method only works on the 64bit flavor of Windows is that it comes with both 32bit and 64bit versions of Internet Explorer. We will configure the 32bit version of Internet Explorer to use JRE6 and the 64bit version to use JRE7. This is done by installing the 64bit version of JRE7 . You can download 64bit JRE7 from the Java download page. Just look for Windows x64, which I’ve highlighted in the image below.

JRE7-64bit-download

After you download and install JRE7 64bit, now launch 64bit Internet Explorer by just typing “internet explorer” into the run prompt (as shown below) and click on “Internet Explorer (64-bit)”

iexplorer-64bit

You can quickly verify which version of JRE is running by accessing this java.com url. You will notice that this link shows JRE7 when you access it via Internet Explorer 64bit and the default Internet Explorer will show JRE6.

You may be  concerned that this setup is not supported, but don’t worry. 64bit Internet Explorer & 64bit JRE are certified with Oracle E-Business Suite. You can refer to My Oracle Support Note 285218.1
I would like to hear about any issues you may have experienced with JRE. Please post them in the comments section!

3 Responses to “Running JRE7 alongside JRE6 for Oracle Forms”

  • Hi. You can configure E-Business suite to run with 1.6+ instead of a specific version of JRE which cuts down on the possible warning/error messages that clients will receive. Using 11i as an example put a version of JRE here $COMMON_TOP/util/jinitiator/ and call it j2se16+.exe then update the apps context variables below:

    Run autoconfig and then no more JRE error messages. It should work for any JRE application. I can email you more detail and how to do it without autoconfig if you wish. It has been a huge troubleshooting time saver here. Oracle regards this as a custom development, but my 11i app has been serving java forms users with it for 9+ months now with no issues. I have no source to credit as I developed it myself. Thanks Ciaran

    • Sorry the code block was missing:

      s_jinit_ver_comma to 1.6+
      s_sun_plugin_ver to 1.6+
      s_jinit_ver_dot to 1.6+
      s_sun_clsid to 8AD9C840-044E-11D1-B3E9-00805F499D93
      s_jinit_clsid to 8AD9C840-044E-11D1-B3E9-00805F499D93

  • Vasu Balla says:

    Hi Ciaran, Thanks for your comment. you are right about configuring with java 1.6+ to get it working with all kind of JREs. But my post is more about dealing with JRE conflicts when you are accessing different Customers environments who are configured with different versions ( JRE6 & JRE7 ) of JREs. The assumptions is if you access Customer with JRE6 with JRE7 on your desktop, you will end up with forms issues.

Leave a Reply

  • (will not be published)

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>