Sun JRE 1.6.0_32 Certified with Oracle E-Business Suite

Java logo

[Apr. 30, 2012 Update: Clarified certification information for JRE 7, added more details about Java 7 plans]

I'm pleased to let you know that the latest Java Runtime Environment 1.6.0_32 (a.k.a. JRE 6u32-b05) is now certified with Oracle E-Business Suite Release 11i and 12.  

What's new in Java 1.6.0_32?

See the 1.6.0_32 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions.  64-bit JREs are certified only on 64-bit versions of Windows 7 and Windows 7 Service Pack 1 (SP1).

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

All JRE releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline.  We test all new JRE releases in parallel with the JRE development process, so all JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What about Java 7?

We're working on our Java 7 certification for the E-Business Suite right now.  Our first set of certifications will cover JRE 7 for Windows desktops.  This will be followed by JDK 7 certifications for server-based components.  

These certifications haven't been completed yet.  You should remain on Java 6 for both desktop-based and server-based components until we announce those certifications.

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.    

References

Related Articles
Comments:

Offhand, if we have Java 1.6.0_26 on our EBS 12.0.6 Forms server, can our EBS users have a higher JRE version on their clients, such as 1.6.0_31? We're running into Web ADI journal upload issues from clients in such scenarios (client has higher version, or higher update to be precise, of JRE 1.6).

The problem we're running into is that JRE 1.6, since about update 20, only seems to replace the previous update instead of allowing 2 versions on the client. In the "old days" of JRE 1.6, it was easy to have 2 versions installed on 1 client, for instance, 1.6.0_02 and 1.6.0_09.

Posted by JerseyEric on April 30, 2012 at 05:34 PM PDT #

Hi,

Your users should be able to connect to your 12.0.6 instance running JRE 1.6.0_31 from the desktop and there should be no requirement to have 1.6.0_26 installed. This should also not affect WebADI upload. Please feel free to log an SR with support and let us know the number so that we can follow up on the issue if required.

A little background:
For a number of years now Java has adopted a non-static version model whereby it will try and use the latest version of the plug-in that is available on the desktop client. This means that the version you have as default within your EBS environment now simply denotes the 'minimum' version that must be used to access the system.

Another enhancement to this model was that when you install a new version of JRE it will by default install in the same directory, thus replacing the old version. Default is usually "C:\Program Files\Java\jre6". You can still install multiple versions by changing the directory on install but this is a pretty pointless practice as JRE will always want to run on the latest (and therefore most secure) version available on the desktop and will not specifically use the earlier versions anyway.

Regards,
Tim.

Posted by Tim Mervyn on May 01, 2012 at 09:45 AM PDT #

Has anyone reported the issue with the latest 1.7 release. Aparently the company string in this version was changed from Sun to Oracle and this causes forms to think that you are running jinitiator even though you are running 1.7.0.4. Funny but true.

Posted by greg on May 17, 2012 at 10:54 AM PDT #

Hi,

Some of the users we have who use EBS have inadvertently upgraded to JRE 7. When launching forms sessions, they get this error:

FRM-92095: Oracle JInitiator version too low. Please install version 1.1.8.2 or higher.

I'm currently on JRE 6 Update 31. If I choose the update option, it says the latest version is JRE 6 Update 32.

Will the "update" option in the Java control panel only show JRE 7 once JRE 7 has been certified to work with EBS?

Presumably if users get a new computer and just stick on JRE 7, and then try EBS, they'll get the error I mention above, but if they're already on JRE 6 and choose the +update+ option, there is no risk that they'll end up on JRE 7, unless JRE 7 has been certified with EBS?

Thanks

Posted by Jim on May 24, 2012 at 04:51 AM PDT #

Hi,

As you mention, JRE 7 is not yet certfied for EBS and further information within this area will of course be documented once certified. The error you are seeing is one of the issues we have fixed as part of this certification process and will be one of the patch requirements for users who wish to use JRE7 once our certification is completed.

The JRE update mechanism is not dependent on whether EBS is certified with the versions available or not, the certification will not change this. If you have both JRE 6 and JRE 7 installed on your desktop they will both show up in the Java Control Panel. However if you run the automatic update it will look for a later JRE 7 version. As long as your users only have JRE 6 installed on their desktops the update facility will currently only look for later JRE6 versions and will not force an upgrade to JRE 7.

Please also note that if you are running a 64-bit stack which was recently certified for EBS (64-bit IE8/9, 64-bit JRE on Windows 7 64-bit) the 64-bit JRE does not currently include an automatic update facility so the above assumes you are running a 32-bit stack.

Regards,
Tim.

Posted by Tim Mervyn on May 24, 2012 at 10:13 AM PDT #

Hi Tim - thanks for your answer, that's really helpful.

Can I just confirm - once JRE7 has been certified, will it be possible to use it without getting the "FRM-92095" error, or will we also need to apply a patch, as I wasn't sure if that's what you meant when you say:

"...and will be one of the patch requirements for users who wish to use JRE7 once our certification is completed."

Thanks again

Posted by Jim on May 25, 2012 at 12:10 AM PDT #

Hi,

Part of the fix for the FRM-92095 error is on the EBS side. Therefore once certified you will still need to apply this patch fix and possibly others as pre-requisites to successfully run EBS with JRE 7.

Regards,
Tim.

Posted by Tim Mervyn on May 25, 2012 at 02:33 AM PDT #

Hi Steeven,

Currently all our desktops has JRE 6 to access EBS 11i and we are good. We have some users who need both JRE 6 & JRE 7 and both these versions can co-exists on the windows desktop. So my question is, if the user have both these versions on his desktop then which version of jre will be used to access the EBS 11i?

We can control the auto update to JRE 7 if we have only JRE 6 is installed but this is not the case here.

Please help

Thanks,
-Mukarram

Posted by Mukarram on June 21, 2012 at 09:00 PM PDT #

Hi, Mukarram,

Please refer to "Appendix B: Static vs Non-Static Versioning and Set Up Options" in Note 290807.1 for a detailed discussion of this for 11i environments.

In general, the non-static versioning model is used. This means that the latest installed version of JRE will be used, regardless of what's specified in the EBS server-level configuration files.

Regards,
Steven

Posted by Steven Chan on June 22, 2012 at 09:55 AM PDT #

Hi
FYI the following error message still occurs with the latest Java version 7 "Oracle Jinitiator version too low. Please install version 1.1.8.2 or higher."

The error stopped when I uninstalled version 7 and went back to Java version 6.0.31

Thought this feedback would be of benefit.

Regards
Hugh

Posted by Hugh on July 24, 2012 at 04:33 PM PDT #

Hi, Hugh,

Thanks for the data point. We'll be publishing information about interoperability patches and configuration steps for JRE 1.7 as soon as we complete our certification for E-Business Suite clients.

Stay tuned.

Regards,
Steven

Posted by Steven Chan on July 25, 2012 at 09:09 AM PDT #

I installed java7 and the following error message still occurs with the latest Java version 7 "Oracle Jinitiator version too low. Please install version 1.1.8.2 or higher."

what should i do now

Posted by AJAY KUMAR on July 30, 2012 at 07:06 AM PDT #

Ajay,

JRE 7 isn't certified with EBS yet. For now, you should uninstall JRE 7 and revert back to JRE 6. See this article for details:

URGENT BULLETIN: All E-Business Suite End-Users Must Manually Apply JRE 6 Updates
https://blogs.oracle.com/stevenChan/entry/bulletin_disable_jre_auto_update

Regards,
Steven

Posted by Steven Chan on July 30, 2012 at 09:40 AM PDT #

give me instructions, how do I install Java 1.6? There are some programs that require it, to run.

Posted by chuckkish65 on August 31, 2012 at 09:55 AM PDT #

Hello, Guest,

Installation instructions are available here:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Regards,
Steven

Posted by Steven Chan on August 31, 2012 at 10:56 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

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