By Steven Chan - EBS-Oracle on Mar 04, 2013
All JRE 6 and 7 releases are certified with EBS upon release
Our standard policy is that all E-Business Suite customers can
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
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_43?
See the 1.6.0_43 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.
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 will change 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):
- EBS 11i Extended Support ends November 2013
- EBS 12.0 Extended Support ends January 2015
- 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:
- All Java SE Downloads on MOS (Note 1439822.1)
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:
- Information Center: Installation & Configuration for Oracle Java SE (Note 1412103.2)
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.
- Recommended Browsers for Oracle Applications 11i (Metalink Note 285218.1)
- Upgrading Sun JRE (Native Plug-in) with Oracle Applications 11i for Windows Clients (Metalink Note 290807.1)
- Recommended Browsers for Oracle Applications 12 (MetaLink Note 389422.1)
- Upgrading JRE Plugin with Oracle Applications R12 (MetaLink Note 393931.1)