JRE 1.8.0_65/66 certified with Oracle e-business Suite

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 Codelin E is 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 is certified with EBS upon release

Our standard policy is the 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 is considered certifie D with the e-business Suite on the same day, they ' re released by our Java team.

Need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users ' de Sktops.

What's new in this release?

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

• CPU Release is JRE 1.8.0_65
• PSU Release is JRE 1.8.0_66

Oracle recommends, Oracle E-business Suite customers use the CPU release (JRE 1.8.0_65) and only upgrade to the PSU re  Lease (JRE 1.8.0_66) if they require a specific bug fix. For further information and bug fix details Seejava CPU and PSU releases explained.

There currently no known issues in Oracle e-business Suite that require the PSU release but it's certified for custom ERS, need to use it.

This JRE update is a CPU release. If you were running on the JRE 8 stream, it was strongly recommended to upgrade to this latest and therefore most secure ver Sion 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 is the official patch requirements documented?

All patches required for ensuring full compatibility of the e-business Suite with JRE 8 is documented in these Notes:

For EBS 11i:

• Deploying Sun JRE (Native plug-in) for Windows clients in Oracle e-business Suite Release 11i (Note 290807.1)

For EBS 12.0, 12.1, 12.2

• Deploying Sun JRE (Native plug-in) for Windows clients in Oracle e-business Suite Release (Note 393931.1)

Known Issues

IE performance Issue: Launching JRE 1.8.0_65 or 1.8.0_66 through Internet Explorer would have a delay of about seconds befre the applet starts To load. Java Console would 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 the this blog for updates.

EBS + Discoverer 11g Users

This JRE release are certified for discoverer 11g in e-business Suite environments with the following minimum requirements:

• Discoverer (11g) 11.1.1.6 plus Patch 13877486 and later
• Reference:how to Find Oracle BI Discoverer 10g and 11g certification information (Document 233047.1)

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 D  Ates 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-Available for Java SE Deployment technology. It is the more important than ever for the stay current with new JRE versions.

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

• You can continue-do-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:
• All Java SE Downloads on MOS (Note 1439822.1)

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

• You can continue-do-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:
• All Java SE Downloads on MOS (Note 1439822.1)

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

• You can continue-do-until the end of Java SE 8 Deployment Technology Premier support in March 2019
• You can obtain JRE 8 updates from the Java SE download site or from My Oracle support. See:
• All Java SE Downloads on MOS (Note 1439822.1)

Would EBS users is forced to upgrade to JRE 8 for Windows desktop clients?

No.

This upgrade was highly recommended but remains optional while Java 6 and 7 were covered by Extended support. Updates would be delivered via My Oracle support, where can continue to receive critical bug fixes and security fixes a s well as general maintenance for JRE 6 and 7 desktop clients. Note that there is 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 this 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 are an Update available.

Enabling the JRE auto-update feature on desktops with JRE 6 installed would have no effect.

With the release of the January Critical patch Updates, the Java auto-update mechanism would automatically Update JRE 7 PLU G-ins to JRE 8.

Enabling the JRE auto-update feature on desktops with JRE 8 installed would apply JRE 8 updates.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 are recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Wi Ndows desktops for reasons unrelated to the e-business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 would be invoked instead of earlier JRE releases if both is 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 does 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:

• Oracle e-business Suite release Notes release for Apple Macintosh OS X (Note 1533334.1)

Would EBS users is 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 a certified with the E-business Suite. EBS customers should continue to run EBS servers on JDK 6 or 7.

References

• 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 (MetaLink Note 389422.1)
• Upgrading JRE Plugin with Oracle applications R12 (MetaLink Note 393931.1)

Related articles

• Mismanaged Session Cookie Issue Fixed for EBS in JRE 1.6.0_23
• Roundup:oracle Jinitiator 1.3 desupported for EBS Customers in July 2009

The preceding is intended to outline we have general product direction.   It is the intended for information purposes only, and may isn't being incorporated into any contract. It is a commitment to deliver any material, code, or functionality, and should not being 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.

JRE 1.8.0_65/66 certified with Oracle e-business Suite