Java JRE 1.7.0_25 Certified with Oracle E-Business Suite

Java logoJava Runtime Environment 7u25 (a.k.a. JRE 7u25-b16) and later updates on the JRE 7 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 needed to enable EBS environments for JRE 7?

EBS customers should ensure that they are running JRE 7u17, at minimum, on Windows desktop clients.

Of the compatibility issues identified with JRE 7, the most critical is an issue that prevents E-Business Suite Forms-based products from launching on Windows desktops that are running JRE 7. 

Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers. 

These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite.  These patches may be applied immediately to all E-Business Suite environments. All other Forms prerequisites documented in the Notes above should also be applied. 

Where are the official patch requirements documented?

All patches required for ensuring full compatibility of the E-Business Suite with JRE 7 are documented in these Notes:

For EBS 11i:

For EBS 12

Prerequisites for 32-bit and 64-bit JRE certifications

JRE 1.70_25 32-bit + EBS 11.5.10.2

JRE 1.70_25 32-bit + EBS 12.0 & 12.1

JRE 1.7.0_25 64-bit + EBS 11.5.10.2

JRE 1.70_25 64-bit + EBS 12.0 & 12.1

EBS + Discoverer 11g Users

JRE 1.7.0_25 is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:

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 on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

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:

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:

References

Related Articles
Comments:

Steven,

We're on R12.1.3 and a few months ago we applied the necessary patches to enable our environment to support both Java JRE 6 and JRE 7 on client desktops. Our goal was to slowly migrate end users to JRE 7 as they get new computers or have a need to get their computers re-imaged.

Our IT Security team brought to our attention that there is a new zero-day vulnerability that affects Java 6 which doesn't exist in Java 7 and wants our users to be upgraded to Java 7 right away. This isn't a problem and our internal helpdesk is working to get this done.

The problem we're having is with the JRE executable that is available on the server to be downloaded to the client desktop in the event that the client does not have Java installed when they connect to Forms. As you know, when this happens the JRE executable that is available for download on the server is downloaded and installed on the client desktop after which Forms launches.

Given that JRE versions change fairly quickly it becomes difficult to keep the JRE available on the server up to date. Our DBA informs me that to change the JRE version available for download from the server requires running adpatch which we don't do unless we have a scheduled maintenance outage.

If we don't keep the JRE available on the server updated, we run the risk of the client ending up with an older version that might have vulnerabilities. We have that problem currently in PROD. The JRE on the server is a really old version of Java 6 and client desktops are ending up with that version. We're currently in the process of updating the server JRE version to 7.25 but once the next version comes out we're out of date again.

What is the best practice in this situation? How do we balance the need to keep our client desktops on the latest Java JRE version to address vulnerability issues and the need to keep our system up (i.e. not take an outage just to update the JRE available for download from the server)? We prefer not to enable auto-update of the JRE on client desktops so that the internal Oracle support team gets a chance to test the latest update before it gets rolled out to the masses.

We looked to see if there was a way to disable the automatic download of the JRE from the server (when launching forms) and perhaps display a message to the end user to install Java but we didn't find anything. Our DBA renamed the JRE executable on the server to see what that would do when the client desktop doesn't have Java installed. When the user tries to launch Forms nothing happens which is expected but doesn't tell the end user that something needs to be done.

I'm looking for recommendations / best practice for this issue since I'm sure we're not the only ones facing this issue.

I look forward to your reply.

Thanks,

Abe

Posted by guest on August 30, 2013 at 09:26 AM PDT #

Hello, Abe,

This is a useful summary for all of our readers debating their Java management processes. Thanks for taking the time to lay this out. You're not the only ones facing this issue.

The easiest method is to enable auto-update on your end-users's desktops. That would ensure that they always have the latest JRE release installed, regardless of the version that you've staged internally on the EBS application tier server.

This works nicely from a version control perspective, too. The later version of JRE will be invoked by default when accessing EBS.

If your internal Oracle support team would like to test the latest update before it gets rolled out, they can download the early access versions here:

http://www.oracle.com/technetwork/java/javase/downloads/ea-jsp-142245.html

Regards,
Steven

Posted by Steven Chan on September 05, 2013 at 09:36 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