X

The Latest Technology Stack News Directly from EBS Development

JRE 1.7.0_71 and 1.7.0_72 Certified with Oracle E-Business Suite

Steven Chan
Senior Director

Java logo

Java Runtime Environment 1.7.0_71 (a.k.a. JRE 7u71-b14) and 1.7.0_72 (7u72-b14) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.  

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

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 this release?

Starting with JRE 1.7.0_71 Oracle will release a Critical Patch update (CPU) at the same time as the corresponding Patch Set Update (PSU) release for Java SE 7. It is recommended that Oracle E-Business Suite customers use the CPU release (JRE 1.7.0_71) and only upgrade to the PSU release (JRE 1.7.0_72) if they require a specific bug fix.  For further information and bug fix details see Java CPU and PSU Releases Explained. There are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it. JRE 1.7.0_71  (7u71) is a CPU release. If you are running on the JRE 7 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 7 Plug-in.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

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.0, 12.1, 12.2 EBS + Discoverer 11g Users

This JRE release 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 until the end of Java SE 6 Extended Support in June 2017.

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:

Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

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

This upgrade is highly recommended but remains optional while Java 6 is covered by Extended Support. 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. 

Java 6 is covered by Extended Support until June 2017.  All E-Business Suite customers must upgrade to JRE 7 by June 2017.

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 X 10.9 can run JRE 7 plug-ins.  See this article:

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

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. 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 JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.  

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

References

 

Related Articles

Join the discussion

Comments ( 14 )
  • K Kempf Monday, October 20, 2014

    We'd like to go live on R12.2 with JRE 7.X (it was 67, now 71 is out) and stay there for a while. As a manufacturer, 75% of our corporate machines are locked down via Windows policy to the point where they cannot install software, much less connect to the internet. Between code signing, changing browser compatibility, Java SE updates and Java nag screens when launching professional forms, this is quickly becoming an administrative issue in our organization. Now I see Java SE7 has an April 2015 EOL which appears to only compound the confusion. I'm curious what your take is on how to manage non-stop Java SE updates in an enterprise environment.


  • guest Monday, October 20, 2014

    What about jre 1.8? It's downloading now and gets applied when users agree to upgrade to latest version.


  • Steven Chan Monday, October 20, 2014

    Hi, Kevin,

    I don't think I have any surprising insights about managing Java-related administration and maintenance in enterprise environments. Java is an operating system, just like Windows or Linux. As with all operating systems, Java requires regular maintenance. As security threats increase, so do the defensive requirements. The Java team has been criticized in the past for having inadequate defenses to security issues. Now they're being criticized for addressing those concerns. Apparently, it's hard to keep everyone happy when you have millions of users.

    It's a tough call, but you've got to weigh the risk of a security issue vs. the maintenance overhead. Every enterprise has their own threshold. Some lock their desktops and servers down and never upgrade them. Others apply every upgrade as soon as they're available.

    By the way, I'll be writing an article about the impacts of Java 7's EOL on EBS users soon (sneak preview: just like Java 6's EOL, EBS users will continue to get access to Java 7 after it's publicly EOL).

    I've been enjoying your blog articles about your experiences with EBS 12.2. Please don't hesitate to let me know if you need help with your upgrade.

    Regards,

    Steven


  • Steven Chan Tuesday, October 21, 2014

    Hello, Guest,

    As of today, the JRE Autoupdate tool will only automatically upgrade a given JRE 1.7 release to a later release on the 1.7 codeline.

    We are in the final stages of certifying JRE 8 with the E-Business Suite now. EBS users should avoid installing JRE 8 on their desktops until we release that certification.

    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.

    Regards,

    Steven


  • Anna María Tuesday, October 28, 2014

    Hi Steven,

    Any new info on certification of JRE 1.8 with EBS?

    We have problems with users where Java 1.8u25 has been pushed to many users.

    Our minor testing show no problems with general usage in forms (we are on 12.1.3 RPC1), do you recommend downgrading to the latest 1.7 Java ?

    regards,

    Anna María


  • Steven Chan Tuesday, October 28, 2014

    Hi, Anna Maria,

    We're in the final stages of certifying EBS with JRE 8 right now. At least one server-side patch is needed. We recommend that you keep your EBS users on JRE 1.6 or 1.7 until we release this certification.

    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.

    Regards,

    Steven


  • Thomas Birk Thursday, October 30, 2014

    Subscribing to notifications ...


  • Steven Chan Thursday, October 30, 2014

    Thomas,

    If you want to be informed about new articles posted on this blog, you can subscribe by clicking the "Subscribe by Email" link in the upper-right sidebar menu.

    Regards,

    Steven


  • Cyndie Winrow Tuesday, November 4, 2014

    Hi Steven -

    We're increasingly finding some of our customers are getting upgraded to Java 8 unintentionally, and then of course can't use eBS until we get 8 uninstalled and throttle back to Java 7 ... is a certification for Java 8 with eBS in the works and coming soon? Thanks!


  • Steven Chan Wednesday, November 5, 2014

    Hi, Cyndie,

    Yes, this certification is underway and imminent. Watch this blog for news soon.

    Regards,

    Steven


  • guest Friday, November 14, 2014

    Hi Steven,

    Our EBS users have a variety of versions of Java. As a result the EBS minimum version of Java is 6u7. Users with more recent versions of Java get the warning "Unavailable version of java requested" twice when they login. Is there a way to tell EBS to accept any version of Java? I have an open SR. Support suggested using a Deployment Ruleset. I'm not sure if that will work with older versions of Java. What is the best way to allow users with any version of Java to login without receiving the warning message?

    Thanks - Jeff


  • Steven Chan Friday, November 14, 2014

    Hi, Jeff,

    I'd like to help, but blog comments aren't ideal for this. What is your Service Request number? I'll ensure that the Support engineer assigned to your SR gets Development guidance, as appropriate.

    Regards,

    Steven


  • guest Monday, November 17, 2014

    Is this new release is compatible with all editions of Salesforce.


  • Steven Chan Monday, November 17, 2014

    Hello, Guest,

    This blog focusses on E-Business Suite-related topics. We don't have any visibility into Salesforce issues. You should follow up with that third-party vendor directly for assistance.

    Regards,

    Steven


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha
Oracle

Integrated Cloud Applications & Platform Services