JRE 1.7.0_91 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_91 (a.k.a. JRE 7u91-b15) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i, 12.1, and 12.2 for Windows-based 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.

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?

What's new in this release?

This JRE update 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.

For further information and bug fix details see Java CPU and PSU Releases Explained.

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:

JRE 7 End of Public Updates

The JRE 7u79 release was the last JRE 7 update available to the general public.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 7 updates to the end of Java SE 7 Premier Support to the end of July 2016.

How can EBS customers obtain Java 7 updates after the public end-of-life?

EBS customers can download Java 7 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

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

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.

Java Auto-Update Mechanism

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

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?

Mac users running Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

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
Comments:

Based on reading the note " Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 ( Doc ID 393931.1 )", since we use non-static versioning , it would not be required to update jre on the server side. Clients can download higher versions of jre when available and there would not be any issues. This is also exxplained in steven chan's blog and comments there in over here https://blogs.oracle.com/stevenChan/entry/jre_8_ebs

So the question I have is
(a) Is there any reason why someone would upgrade their web tier jre to higher version.
I dont see any reason and in fact it may be an good thing not to upgrade because now my clients can use any jre version from 1.6.0.27 to the latest one that is available .

Posted by Kumar on December 16, 2015 at 03:52 AM PST #

Kumar,

The latest JRE releases contain the latest fixes for security, speed, and stability. You should always keep your JRE clients patched to the latest levels for maximum security.

Regards,
Steven

Posted by Steven Chan on January 07, 2016 at 02:22 PM PST #

Hi Steven
Thanks for your comments. I agree with you as far as clients are concerned. But my point is there is no point in updating the server side java (like jre upgrade on server side). In the old model, it was mandatory to update the server side jre with whatever you want the users to use. But in the non-static versioning case,this is no longer true.
Can you please confirm.

Thanks

Kumar

Posted by guest on January 07, 2016 at 08:42 PM PST #

Hi, Kumar,

I think it depends upon how well-managed your end-user desktops are.

If all of your end-user desktops are always running the latest JRE release, then it doesn't really matter what you've staged on your EBS server.

If your desktops are not well-managed, then some of them may be running a very old or outdated JRE release. Configuring your EBS server to specify the minimum version needed will ensure that the users running older JRE releases will get whatever you stage on your system.

I would generally recommend that you keep your EBS server up-to-date with each new JRE release. It's a simple administration step with significant upside: this step protects your EBS environment and user community from vulnerabilities that might exist in older JRE releases, regardless of how much attention you pay to your end-user desktops.

Regards,
Steven

Posted by Steven Chan on January 12, 2016 at 09:43 AM 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