Java JRE 1.6.0_51 Certified with Oracle E-Business Suite

[Jun. 20, 2013 Update: corrected link to Java 6 downloads via My Oracle Support]

The latest Java Runtime Environment 1.6.0_51 (a.k.a. JRE 6u51-b11) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12 for Windows-based desktop clients.  

All JRE 6 and 7 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, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 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 1.6 or JRE 7 releases to your EBS users' desktops.

What's new in Java 1.6.0_51?

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions.

32-bit JREs are certified on:

  • Windows XP Service Pack 3 (SP3)
  • Windows Vista Service Pack 1 (SP1) and Service Pack 2 (SP2)
  • Windows 7 and Windows 7 Service Pack 1 (SP1)

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.

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

The latest updates to that page (as of Sept. 19, 2012) state (emphasis added):

Java SE 6 End of Public Updates Notice

After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

What does this mean for Oracle E-Business Suite users?

EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

In other words, nothing changes for EBS users after February 2013. 

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

  1. EBS 11i Extended Support ends November 2013
  2. EBS 12.0 Extended Support ends January 2015
  3. EBS 12.1 Extended Support ends December 2018

How can EBS customers obtain Java 6 updates after the public end-of-life?

EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?

No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

Coexistence of JRE 6 and JRE 7 on Windows desktops

The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

Applying Updates to JRE 6 and JRE 7 to Windows desktops

Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

What do Mac users need?

Mac users running Mac OS 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

EBS 12 certified with Mac OS X 10.7 and 10.8 with Safari 6 and JRE 7

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

JDK 7 is certified with E-Business Suite 12.  See:

Java (JDK) 7 Certified for E-Business Suite 12 Servers

References

Related Articles
Comments:

Can you indicate us, please, a valid download link for Java Runtime Environment 1.6.0_51?
(jre-6u51-windows-i586.exe)

I know that this version is not available for free download. But I can not use the latest version of JRE 1.7.
And not because it has a lot of security vulnerabilities.
But because JRE 1.7 is not detected by my application named StarOffice.

If I want to use StarOffice I need JRE 1.6.

I do not want to use LibreOffice - which works fine with JRE 1.7.

I reported, last year, this "incompatibility" problem, to Oracle. But it was useless: the problem is still unsolved. It seems that ORACLE are no longer willing to support SUN StarOffice.

Those who paid for their StarOffice copies, now are required to pay for ORACLE support - every time they want to download the latest version of JRE 1.6.

Is it correct?

Posted by guest on June 19, 2013 at 01:59 PM PDT #

I went to the links posted for the download and release notes, and do not see JRE 1.6.0_51 on either page. They are still showing JRE 1.6.0_45 as the latest release. When will that be updated?

Posted by guest on June 20, 2013 at 05:27 AM PDT #

I am a Oracle E-Business Suite user .can i use JRE 7 for my applications.In JRE 6 ,Java Runtime Environment 1.6.0 32 very effective for us .Is there any advantage by using JRE 7 from JRE 6.

Posted by abinaya on June 20, 2013 at 07:06 AM PDT #

Hi, Guest,

I'm part of the E-Business Suite division. I'm afraid that I don't have any visibility into StarOffice licencing and support provisions.

You might wish to contact either Oracle Support or your Oracle account manager for help with StarOffice policy questions. Failing that, try posting your question to a StarOffice OTN forum or blog (this blog is dedicated to E-Business Suite-related topics).

Regards,
Steven

Posted by Steven Chan on June 20, 2013 at 09:59 AM PDT #

Hi, Guest,

This update is the first that's no longer publicly available, but it's still available for E-Business Suite customers. See the section entitled "Implications of Java 6 End of Public Updates for EBS Users" in the article.

I've updated the article's intro with links to the latest Java 6 download Note on My Oracle Support.

Regards,
Steven

Posted by Steven Chan on June 20, 2013 at 10:10 AM PDT #

Hi, Abinaya,

For a discussion about Java 7's benefits, see:

Why should I upgrade to Java 7?
http://java.com/en/download/faq/why_upgrade.xml

EBS users may use either JRE 6 or 7 for their desktop clients connecting to E-Business Suite environments. You can deploy whichever version meets your overall JRE requirements across your enterprise.

Regards,
Steven

Posted by Steven Chan on June 20, 2013 at 10:14 AM PDT #

Hello Steven,
Our EBS R12.1.3 application works well with 32 bit java 7, but whenever oracle releases Java 7 updates our desktop users are prompted that "Your Java version is insecure" with three options Update, Block and Later.
Is there a way we can avoid these prompts?
As most of times our Windows desktop users select either Update or Block option and then forms donot work properly for them.
Thanks,
Tony

Posted by guest on June 24, 2013 at 02:54 PM PDT #

Great.
Java 7 just introduced so many incompatibilities that many software simply don't work, and regression against all the new "features" is pretty too difficult.

I'll just ask all my suppliers (e.g., a small firm called Cisco) to upgrade their software to support Java 7 or, better, to drop Java at all.

thank you for your support sofar.

mtg

Posted by mtg on June 25, 2013 at 04:10 AM PDT #

For myself, and for all those who still use StarOffice 9, or Oracle Open Office 3: I found a solution for the "non-detected Java 1.7" problem.

I downloaded and installed - in a virtual environment - OpenOffice 3.4.1. Then I copied, in a newly created folder, the files named "sunjavaplugin.dll" and "javavendors.xml".

And then I replaced the "outdated" SO 9 files, with the "new" ones.

The paths to the files which need to be replaced are the followings:

C:\Program Files\Sun\StarOffice 9\URE\bin
C:\Program Files\Sun\StarOffice 9\URE\misc

I hope that it is not necessary to replace other files, too.

Now, I can install the latest version of JRE (1.7.0.XX). AND I can still use StarOffice 9.

For those who do not want to install OO 3.4.1, I uploaded the "updated" files, here:

http://www.mediafire.com/download/2e08yo3n29506n2/File_replacements_for_SO_9_and_OOO_3.zip

Despite the fact that I like more StarOffice, I must confess that I remained impressed by the latest version of [Apache] OpenOffice. So impressed that I already installed it on one of my older systems. You might like it, too. So, try it a little, in your spare time.

Now I no longer need Java 1.6.0.XX - which, by the way, is not at all available for free download.-

Posted by Wolfram on June 25, 2013 at 11:41 AM PDT #

Hi, MTG,

I appreciate your frustration.

Please note that this blog is staff by Oracle E-Business Suite specialists, so we don't really have much to say about Java 7's backwards compatibility.

I'll pass your comments along to the Java team, but you might wish to let them know through a Java community or forum where those developers hang out.

Regards,
Steven

Posted by Steven Chan on June 25, 2013 at 02:41 PM PDT #

Tony,

Oracle's JRE 7 releases recently had security updates, hence the prompts you have mentioned are appropriate. However, all JRE 7 updates recently were certified with EBS R12 and 11i at the time of release of such updates. If you have any specific instance of a particular version not working fine after choosing to block or update, please let us know the details through an SR. Our support folks will take it forward appropriately. I also strongly encourage you to go through the appendices in our JRE note in detail for known issues and work arounds for those.

Hope this helps.

Regards,
Prasad

Posted by Prasad Akkiraju on June 27, 2013 at 01:04 AM PDT #

Where is 1.6.0_51? I need that, and can't find it.

Posted by guest on November 05, 2013 at 08:13 AM PST #

Hello, Guest,

As stated in the article above:

"Java 6 is now available only via My Oracle Support for E-Business Suite users. You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

All Java SE Downloads on MOS (Note 1439822.1)"

Regards,
Steven

Posted by Steven Chan on November 05, 2013 at 10:04 AM PST #

is there a way to download Java 1.6 at this point?

Posted by guest on January 13, 2014 at 09:52 AM PST #

Hello, Guest,

Yes. See the section in the article above with the subhead: "How can EBS customers obtain Java 6 updates after the public end-of-life?"

Regards,
Steven

Posted by Steven Chan on January 13, 2014 at 11:45 AM PST #

Hello,
As per schedule Java 1.8 release date - March 18th
1. When will be the EBS 12.1.3 be certified with that?
2. What needs to be done by ebs users to prepare for this upgrade.
3. Will it be mandatory to sign the jar files as per document Enhanced Jar Signing for Oracle E-Business Suite (Doc ID 1591073.1) ?

Thanks,
Tony

Posted by Tony on January 15, 2014 at 11:48 AM PST #

Hello, Tony,

A question for you: is your organization planning to deploy JRE 8 as soon as Java 8 is released? Can you provide more details in a private email to me?

Answers to your questions:

1. We've been working with beta drops of JRE 8 for a while now. Our certification is underway and will be released as quickly as possible after Java 8 itself is released.

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.

2. We'll publish full details as soon as our certification is completed.

3. You might wish to direct that to a Java product manager. We're in EBS Development and cannot comment on the Java security roadmap.

Regards,
Steven

Posted by Steven Chan on January 15, 2014 at 12:13 PM PST #

We are in the process testing Java 6 and 7 compatibility with signed jar files with EBS version 12.1.3. We have upgraded a test EBS instance with Java 7 signed jar files. I have a few questions. The first is I have a machine with only Java 6 v.31 trying to access the test JAVA 7 test instance. In Internet Explorer 8 I get a message that I need to download Java 7, but in Firefox 28 I'm able to access the instance.

1. Is this intended functionality, or is there a way to get Internet Explorer to work as well?

2. We have another Oracle forms based application(FAMIS) that require Java 6. If we have both Java 6 and 7 installed, the application always defaults to Java 7 even if I disable Java 6. Is there a way to fix this scenario?

Thanks,
Joe

Posted by guest on March 21, 2014 at 07:33 AM PDT #

Hi Joe,

1. EBS changed to an open mimetype (meaning there is no version control) with the release of JRE 6u10. Therefore Firefox will attempt to launch with whatever JRE is installed on the desktop.
IE versioning is still controlled through the CLSID. By default it will only launch on a version of JRE equal to or higher than the version called from EBS which is why you get the message. Lowering the version called from EBS should allow IE to launch, otherwise use the "Dynamic CLSID". See '3. Different Users run different JRE Releases from Multiple JRE Streams' under 'Forms Launch Issues' within document 393931.1

2. In the correct circumstances you can run both JRE 6 & 7 from the same desktop, see 'Coexistence of JRE 7 and JRE 6 on the Desktop Client' from 'Appendix B' of the same note. However I am not familiar with FAMIS or how it calls the JRE version so the above may not be applicable.
Another possible alternative is to set different applications to use different JRE releases through a Deployment Rule Set, http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/security/deployment_rules.html

Regards,
Tim.

Posted by Tim Mervyn on March 24, 2014 at 09:53 AM PDT #

Hi Tim,

Thanks for the response. We have tried to implement the 'Forms Launch Issues' within document 393931.1, Number 3.2. section "4a) Sun JDK Plugin Parameters" and replace the sun_plugin_classid value as follows:
sun_plugin_classid=clsid:8AD9C840-044E-11D1-B3E9-00805F499D93

I'm trying to test using IE 8 and the latest Java 6 version, but the java applet will not launch at all when I click on a responsibility to run. We're on EBS version 12.1.3. Do you have any ideas?

Thanks,
Joe

Posted by Joe on March 26, 2014 at 09:54 AM PDT #

Hi, Joe,

I'm sorry to hear that you've encountered an issue with this.

We can provide general conceptual guidance here, but I'm afraid that this blog isn't the best place to get technical support for specific issues like the one that you're working through.

Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on March 27, 2014 at 10:10 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
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today