Java JRE 1.7.0_45 Certified with Oracle E-Business Suite

Java logoJava Runtime Environment 7u45 (a.k.a. JRE 7u45-b18) 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 needed to enable EBS environments for JRE 7?

EBS customers should ensure that they are running JRE 7u17, at minimum, on Windows desktop clients.

Of the compatibility issues identified with JRE 7, the most critical is an issue that prevents E-Business Suite Forms-based products from launching on Windows desktops that are running JRE 7. 

Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers. 

These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite.  These patches may be applied immediately to all E-Business Suite environments. All other Forms prerequisites documented in the Notes above should also be applied. 

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

JRE 1.7.0_45 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 10.7 or 10.8 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
Comments:

We have started rolling out Java 7 to some users, and we noticed it seems there are two update mechanisms - one we can control via the Control Panel UI, and the other seems to be tied to another mechanism. It's causing some of our less tech savvy users to get concerned as this was not the expected/normal update notification that was present previously, and we deploy them through our AD. The exact notification is noted here:
http://p0w3rsh3ll.wordpress.com/2013/06/25/defeat-the-new-oracle-java-runtimejre-1-7-update-notification-mechanism/

Can you describe some guidance on how to proceed with this second mechanism so that our users are not impacted? For example - our users on 7u40 starting yesterday were being prompted on login to EBS to upgrade, which required our helpdesk staff to visit the users who needed help manually.

Posted by Erik Helgestad on October 17, 2013 at 11:25 AM PDT #

Erik,

You can stage a JRE release in your EBS environment. This JRE release will be downloaded to all EBS users. This is standard practice for EBS users. We recommend that you stage the latest JRE release available.

Users can also install JRE independently. This is standard practice for all JRE users. We recommend that you use the latest JRE release available.

I can't answer questions about the native JRE self-update mechanisms (i.e. Auto-Update). You should log a Service Request against Java for assistance with that.

Regards,
Steven

Posted by Steven Chan on October 17, 2013 at 11:49 AM PDT #

Steven, you say that staging the JRE release on the EBS enironment to let the users download and install the latese version is a standard practice. Isn't it true that in order for the to install it they have to be local admins on their PC's. If so, I don't see how this practice could be wide spread. I sure know our company won't allow that. What recommendations does Oracle have for companies that have polocies that users cannot be local admins. Is there a way to work around this so that they don't have to be admins on the PC? Thanks!

Posted by Jody on October 17, 2013 at 01:54 PM PDT #

Hi, Jody,

Software can be deployed by end-users or centrally. The E-Business Suite provides a mechanism to help central deployments. You're right -- this method doesn't meet everyone's desktop management requirements.

Companies that don't permit end-users to be local administrators have other methods for deploying software to those PCs.

JRE is just another piece of software, like a new version of a browser or Microsoft Word. Companies can use the same methods they use for deploying other software for JRE updates, too.

Regards,
Steven

Posted by Steven Chan on October 17, 2013 at 02:17 PM PDT #

We had to upgrade because we were on .25 and firefox "disabled" it. We found with 1.7.0.45, that every time the user logs on they get a popup warning that it's not a certified (or correctly signed) application. In previous versions of Java you could click a "don't tell me again" box, but you can't on .45, so users get this error every time.. Or have I missed something ?

Posted by Jason Lester on October 18, 2013 at 01:15 AM PDT #

Thanks for the information. I'm sure we are not the only company that has to deal with this situation. In my opinion the analogy that it is like any other software update, such as Word and browsers, is somewhat misleading in that most other software products don’t have nearly as many updates released so frequently. It is very difficult for companies like ours to try and keep current with the JRE updates so we will always be lagging behind. Again, I’m sure we are not the only ones facing this problem.

Posted by Jody on October 18, 2013 at 04:29 AM PDT #

When will Oracle be providing signed Java JAR files ? Users who have upgraded to 7_45 are receiving a warning that future versions of Java will not run self-signed or unsigned code

Posted by Michael on October 18, 2013 at 07:25 AM PDT #

I guess the problem is 2 fold. the most visible is that there is no longer the option to say "yeah, I know, stop bugging me about it", and the more long term issue of java signing. I am unsure why Oracle has removed the option to acknowledge the security risk and move on ?
Jason

Posted by Jason Lester on October 18, 2013 at 09:21 AM PDT #

Hello, Jason,

That's useful feedback that should be provided directly to the Java team. This blog is maintained by E-Business Suite staff, not Java staff, so your comment will not be seen by the right people.

I'd recommend logging a Service Request against Java if you'd like to let them know about your concerns formally.

Regards,
Steven

Posted by Steven Chan on October 18, 2013 at 09:39 AM PDT #

Hello, Jody,

Yes, I agree that you're not the only company facing the challenge of centralized software deployment. This problem also exists for browsers such as Firefox and Chrome, both of which receive new versions every six weeks or so. Many companies struggle with this challenge.

There are a variety of tools for deploying software to Windows PCs, including offerings from Microsoft and other third-party vendors. Given the range of offerings already available, Oracle does not offer generic tools for deploying Windows software.

Regards,
Steven

Posted by Steven Chan on October 18, 2013 at 03:32 PM PDT #

Hello, Jason,

No, you haven't missed anything. The options for handling this in the JRE plug-in have changed. The "Security of the Java Platform" link in the following article has references and a roadmap of current and planned changes to Java security, including this particular change:

Sign E-Business Suite JAR Files Now
https://blogs.oracle.com/stevenChan/entry/sign_e_business_suite_jar

Regards,
Steven

Posted by Steven Chan on October 18, 2013 at 03:35 PM PDT #

Hello, Michael,

We have over 150 components in the E-Business Suite technology stack and over 200 EBS products. In addition to compatibility, development infrastructure, versioning, packaging, and release vehicle challenges, shipping massive pre-signed JAR files would remove our ability to issue small, granular patches to you. In other words, you would need to download huge Java files and retest the entire E-Business Suite every time a small Java-related issue is fixed, regardless of whether that issue affects the subset of EBS products or technology stack components that you use.

To eliminate the warnings, see:

Sign E-Business Suite JAR Files Now
https://blogs.oracle.com/stevenChan/entry/sign_e_business_suite_jar

Regards,
Steven

Posted by Steven Chan on October 18, 2013 at 03:44 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today