JRE 1.8.0_65/66 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_65 (a.k.a. JRE 8u65-b17) and JRE 1.8.0_66 (8u66-b17) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 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 is JRE 1.8.0_65
  • PSU Release is JRE 1.8.0_66
Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_65) and only upgrade to the PSU release (JRE 1.8.0_66) 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.

This JRE update is a CPU release. If you are running on the JRE 8 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 8 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 8 are documented in these Notes:

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

IE Performance issue: Launching JRE 1.8.0_65 or 1.8.0_66 through Internet Explorer will have a delay of about 20 seconds befre the applet starts to load. Java Console will come up if enabled. This issue does not affect Firefox, where the applet launches as usual.  A fix for this issue is currently being investigated. Please monitor this blog for updates.

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.

References

Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 


Comments:

IE Performance issue: Launching JRE 1.8.0_65 or 1.8.0_66 through Internet Explorer will have a delay of about 20 seconds befre the applet starts to load

We have IE11 with EBS 12.1.3 and do we expect this issue for all the users when launching forms.

Posted by guest on October 21, 2015 at 04:29 PM PDT #

Hello, Guest,

Yes, we would expect this to be an issue for all IE users when launching Forms. We're investigating a fix for this right now.

Regards,
Steven

Posted by Steven Chan on October 22, 2015 at 09:32 AM PDT #

there are now already expired four days, there is already a solution in sight

Posted by guest on October 26, 2015 at 07:34 AM PDT #

We are upgrading jre of R12.1.3. In step 1 we have applied all prereq patches and system is running fine in prod with jre 6 and 8. In step 2 we only need to run txkSetPlugin to force users to upgrade jre. The question is if we have some issue, can we run txkSetPlugin again with current version parameter to rollback. We are upgrading from 1.6 to 1.8.
Thanks in dvance

Posted by guest on October 26, 2015 at 04:38 PM PDT #

Hi Steven, can you tell me if there is a solution of thid problem now ?

Regards,
Rob Kraan

Posted by Rob Kraan on October 26, 2015 at 09:18 PM PDT #

Hi Steven,

Is there an ETA on the slow performance issue with JRE 1.8.0_66
We're in the process of upgrading Java and are considering to move to the latest level if possible.

Thanks,
Vignesh

Posted by Vignesh on October 27, 2015 at 05:29 AM PDT #

Hi Steven,

MOS NOTE 393931.1 advises on the patches that are required for JRE 1.8 deployment. I have been working on this note and have been planning to apply forms patch 19568561. However, when I look at this today I note that this has now been replaced by the OCT 2015 CPU patch 21845960. Can you advise how this note is updated with this information. I assume it is a recent update given it is the OCT 2015 CPU patch. Which is only recently released.

The MOST note 393931.1 does appear to have a change log detailing this change which can make it very difficult to understand the delta between those patches I identified in September with those added afterwards.

Rgds, Scott Chisholm

Posted by Scott Chisholm on November 05, 2015 at 04:13 AM PST #

Hi, Scott,

I'm not sure that I understand your question. We regularly update our documentation to reflect the latest available releases, and this is reflected in our Change Logs. The latest releases contain fixes for performance, security, and stability, so it's a good idea to establish a regular cycle for keeping your environment updated.

Regards,
Steven

Posted by Steven Chan on November 09, 2015 at 12:14 PM PST #

Hi,

Regarding, 'We are upgrading jre of R12.1.3. In step 1 we have applied all prereq patches and system is running fine in prod with jre 6 and 8. In step 2 we only need to run txkSetPlugin to force users to upgrade jre. The question is if we have some issue, can we run txkSetPlugin again with current version parameter to rollback. We are upgrading from 1.6 to 1.8.'

Once any pre-req patches are in place you can alter the default JRE version by simply running the txkSetPlugin script. This is mentioned under Step 2.1 of the note. However, if you do rollback to JRE 6 your users may also need to uninstall the JRE 8 release from their desktops as Java will always launch against the latest version.

With both still in place, Depending on the Java versions and other settings, Java based forms will continue to run using JRE 8 or JRE 6 may launch on top of JRE 8. Further information is available under 'Coexistence of Different JRE Families on the Desktop Client' within Appendix B of doc 393931.1.

Regards,
Tim

Posted by Tim Mervyn on November 10, 2015 at 04:19 AM PST #

In case you missed it, see:

JRE8u60 Fixes JRE 8 Launch Delays with Internet Explorer
https://blogs.oracle.com/stevenChan/entry/jre8u60_ie_delay_fixed

Regards,
Steven

Posted by Steven Chan on November 18, 2015 at 09:38 AM PST #

Steven,

Knowing Discoverer 11.1.1.7 is a terminal version. How long do you see future Java Release, in particular the JRE, working with Discoverer?

I am not on 11.1.1.7 and am now looking at the feasibility to go to this terminal version knowing Java is a key component to it functioning properly.

Any incite would be appreciated regarding future releases of Java affects on Discoverer 11.1.1.7 (Beyond 8)

Thanks

Posted by Brent on November 26, 2015 at 09:37 AM PST #

Hello, Brent,

My apologies -- I just noticed this comment, as it was posted during our Thanksgiving holidays.

I'm in the E-Business Suite division. I'm afraid that I don't have much visibility into the long-term outlook for JRE compatibility with Discoverer. I would imagine that the JRE team would take pains to avoid deprecating any externally-published APIs that Discoverer needs, but I'd recommend posting a Service Request against both products to confirm that with the real authorities on this.

Regards,
Steven

Posted by Steven Chan on January 05, 2016 at 11:58 AM PST #

Thanks Steven.

One other question.

We are in a scenario where we have locations which will be at JRE 6, While other will be upgraded to JRE 8. If we apply the JRE pre-requisites for Oracle EBS 12.1.3 will that affect those who are still on JRE 6?

Posted by Brent on January 06, 2016 at 08:14 AM PST #

Hello, Brent,

All of the EBS server-side prerequisites for the latest JRE releases are backwards-compatible with older JRE levels on the same codeline, as well as with other JRE codelines.

If I understand your scenario correctly, you'll be patching your EBS 12.1.3 environment with the server-side requirements for JRE 8. This will be compatible with JRE 6 users, too. You may still access the same Oracle E-Business Suite environment simultaneously using different JRE versions, but only by using separate desktop clients. Each desktop client would use a specific JRE version.

You should review Note 393931.1, Appendix B carefully, especially to handle cases where some users might have different JRE releases on the *same* desktop.

Regards,
Steven

Posted by Steven Chan on January 06, 2016 at 12:46 PM PST #

Post a Comment:
Comments are closed for this entry.
About

Search


Categories
Archives
« February 2017
SunMonTueWedThuFriSat
   
4
5
11
12
18
19
20
21
22
23
24
25
26
27
28
    
       
Today