X

The Latest Technology Stack News Directly from EBS Development

JRE 1.8.0_71/72 Certified with Oracle E-Business Suite

Steven Chan
Senior Director

Java logo

Java Runtime Environment 1.8.0_71 (a.k.a. JRE 8u71-b15) and JRE 1.8.0_72 (8u66-b15) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows desktop clients.

All JRE 6, 7, and 8 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 JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new 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 6, 7, or 8 releases to your EBS users' desktops.

What's new in this release?

Oracle now releases a Critical Patch update (CPU) at the same time as the corresponding Patch Set Update (PSU) release for Java SE 8.

  • CPU Release:  JRE 1.8.0_71
  • PSU Release:  JRE 1.8.0_72

Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_71) and only upgrade to the PSU release (1.8.0_72) if they require a specific bug fix.  For further information and bug fix details see Java CPU and PSU Releases Explained. Internet Explorer users are advised to upgrade to the JRE 1.8.0_72 rather than JRE 1.8.0_71 due to a known performance issue.

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 8 are documented in these Notes:

For EBS 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:

Implications of Java 6 and 7 End of Public Updates for EBS Users

The Oracle Java SE Support Roadmap and Oracle Lifetime Support Policy for Oracle Fusion Middleware documents explain the dates and policies governing Oracle's Java Support.  The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology in these documents.

Starting with Java 7, Extended Support is not available for Java SE Deployment Technology.  It is more important than ever for you to stay current with new JRE versions.

If you are currently running JRE 6 on your EBS desktops:

  • You can continue to do so until the end of Java SE 6 Deployment Technology Extended Support in June 2017
  • You can obtain JRE 6 updates from My Oracle Support.  See:

If you are currently running JRE 7 on your EBS desktops:

  • You can continue to do so until the end of Java SE 7 Deployment Technology Premier Support in July 2016
  • You can obtain JRE 7 updates from My Oracle Support.  See:

If you are currently running JRE 8 on your EBS desktops:

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

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are 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 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

Impact of enabling JRE Auto-Update

Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

Enabling the JRE Auto-Update feature on desktops with JRE 6 installed will have no effect.

With the release of the January Critical patch Updates, the Java Auto-Update Mechanism will automatically update JRE 7 plug-ins to JRE 8.

Enabling the JRE Auto-Update feature on desktops with JRE 8 installed will apply JRE 8 updates.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 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 8 will be invoked instead of earlier JRE releases 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.

What do Mac users need?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) desktops.  For details, see:

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

No.

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

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

Known Iusses

Internet Explorer Performance Issue

Launching JRE 1.8.0_71 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_72.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles

Join the discussion

Comments ( 6 )
  • guest Thursday, January 21, 2016

    Dear Mr Chan,

    Sorry for asking a what might seem a silly question. I am a System Engineer in a EBS system (we are 3 systme engineers in total).

    I would like to ask you about NPAPI (plugin support) end of support from browsers. Are EBS forms affected ? Does EBS use the oracle forms applet technology? Are there any alternatives.

    Sorry if my terminology is not precise. I am asking in order to have an expert's opinion before assessing the urgency for the need for a major system update.

    Many Thanks in advance

    What triggered my question was the following:

    Google Blocks Java Plugin in Chrome

    =====================================

    Beginning with the September 2015 release of Google Chrome, Google has disabled the use of the NPAPI and therefore the Oracle Java Plugin can no longer be used with Chrome. Customers previously using Chrome to run their Oracle Forms applications should consider using other browsers, such as Microsoft Internet Explorer, Mozilla Firefox, or Apple Safari (on MAC).

    Refer to the following for more information on Oracle's position and guidance regarding this change:

    https://java.com/en/download/faq/chrome.xml

    Although future Oracle Forms versions plan to continue using Java on the client tier, alternative client deployment options are planned to be offered in newer Forms releases. These new options are planned to allow administrators to choose between continuing to deploy through a browser (with the Java Plugin where supported) or by excluding the browser/plugin combination and running natively on the desktop with Java alone. The option to avoid using a browser and plugin component of a Java installation will help to mitigate concerns of various browser and plugin issues.

    For more information, refer to the Oracle Forms / Java Plugin FAQ

    ========================================================================


  • Steven Chan Thursday, January 21, 2016

    We are actively reviewing options for future updates to Java and EBS to address Forms compatibility. We will do everything possible to ensure that our customers can continue to run all parts of the E-Business Suite.

    EBS uses Oracle Forms. Forms is based on Java. Java can only run in browsers that support NPAPI.

    Google first announced their decision to disable NPAPI in 2013 for Chrome. This means that Forms-based content can no longer run in Chrome. They began phasing it out in 2014. We noted this in our first certification announcement for Chrome with the E-Business Suite.

    Chrome users can continue to run EBS HTML-based products (OA Framework).

    The Oracle Java team has published formal guidance here:

    " https://java.com/en/download/faq/chrome.xml

    Internet Explorer, Firefox ESR, and Safari will continue to support NPAPI - and Java and Forms. We recommend that customers who need to use Forms-based products in the E-Business Suite use those browsers instead of Chrome.

    Regards,

    Steven


  • guest Friday, January 22, 2016

    Hello,

    Do you know when/if the Internet Explorer forms delay issue will be corrected in the CPU java release? Right now the Internet Explorer forms delay fix is only available in the PSU java release. Most of our users update java automatically. Since we use Internet Explorer as our EBS default browser, those users receive the incorrect java update. Java 8 Update 72 is recommended for EBS Internet Explorer users.

    Thanks


  • Steven Chan Friday, January 22, 2016

    Hello, Guest,

    I'm in the E-Business Suite and my insights into the Java division's roadmap are very limited. I'd recommend logging a Service Request against Java if you need an authoritative reply to this one.

    Regards,

    Steven


  • guest Thursday, January 28, 2016

    https://blogs.oracle.com/java-platform-group/entry/moving_to_a_plugin_free

    Java plugin is dead, how does this affect EBS users? Please write a new blog article about this as guidance.


  • Steven Chan Thursday, January 28, 2016

    Hello, Guest,

    We are actively reviewing options for future updates to Java and EBS to address Forms compatibility. We will do everything possible to ensure that our customers can continue to run all parts of the E-Business Suite.

    EBS uses Oracle Forms. Forms is based on Java. Java can only run in browsers that support NPAPI.

    Google first announced their decision to disable NPAPI in 2013 for Chrome. This means that Forms-based content can no longer run in Chrome. They began phasing it out in 2014. We noted this in our first certification announcement for Chrome with the E-Business Suite.

    Chrome users can continue to run EBS HTML-based products (OA Framework).

    The Oracle Java team has published formal guidance here:

    " https://java.com/en/download/faq/chrome.xml

    Internet Explorer, Firefox ESR, and Safari will continue to support NPAPI - and Java and Forms. We recommend that customers who need to use Forms-based products in the E-Business Suite use those browsers instead of Chrome.

    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