Java JRE 1.7.0_40 Certified with Oracle E-Business Suite

Java logoJava Runtime Environment 7u40 (a.k.a. JRE 7u40-b43) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12 for Windows-based desktop clients.

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

Prerequisites for 32-bit and 64-bit JRE certifications

JRE 1.70_40 32-bit + EBS 11.5.10.2

JRE 1.70_40 32-bit + EBS 12.0 & 12.1

JRE 1.7.0_40 64-bit + EBS 11.5.10.2

JRE 1.70_40 64-bit + EBS 12.0 & 12.1

EBS + Discoverer 11g Users

JRE 1.7.0_40 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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

  1. EBS 11i Extended Support ends November 2013
  2. EBS 12.0 Extended Support ends January 2015
  3. EBS 12.1 Extended Support ends December 2018

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:

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

No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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. 

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?

No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

JDK 7 is certified with E-Business Suite 12.  See:

References

Related Articles
Comments:

https://mail.mozilla.org/pipermail/enterprise/2013-September/003596.html

Firefox ESR 24.0 released, please finish certifying ESR 24.0 soon.

Posted by guest on September 17, 2013 at 03:12 PM PDT #

Hello, Guest,

Yes, we've been working with betas of Firefox ESR 24 for a while. That will be certified with the E-Business Suite soon.

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.

Regards,
Steven

Posted by Steven Chan on September 18, 2013 at 08:59 AM PDT #

We are experiencing an issue with Java 1.7.0_40 in our test environment. We are prompted to accept a security warning for NonForms. Clicking the "Accept" option only works for that session. New sessions prompt for the warning every time. We think we have narrowed down the issue. This is a cloned instance and the certificate issuer is still listed as our Production database.

Is there a fix for this in a cloned test instance?

Thank you for your time,
Judy Zimmerman
Academy School District 20
Colorado Springs, CO 80920

Posted by guest on September 25, 2013 at 09:41 AM PDT #

Hi, Judy,

I'm sorry to hear that you've encountered an issue with this.

We can provide general conceptual guidance here, but I'm afraid that this blog isn't the best place to get technical support for specific issues like the one that you're working through.

Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on September 27, 2013 at 10:26 AM PDT #

Hi,
I have a problem with hebrew
it appears left to right instead of right to left

Can you pleas3e advise?

Thanks

Amit

Posted by Amit on October 15, 2013 at 06:44 AM PDT #

Hi, Amit,

I'm sorry to hear that you've encountered an issue with this.

We can provide general conceptual guidance here, but I'm afraid that this blog isn't the best place to get technical support for specific issues like the one that you're working through.

Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Regards,
Steven

Posted by Steven Chan on October 15, 2013 at 09:13 AM PDT #

Steven,

The issue with signing .jar files for JRE 7.21+ seems to be a really big deal (Judy Zimmerman comment). Wouldn't you need a unique certficate from a CA for each and every EBS environment? This seems like a difficult requirement to justify for Sandbox/Non-Prod environments; is this really true?

Posted by Dan Dunlap on October 16, 2013 at 01:54 PM PDT #

Hi Steven,
We are having an issue with the 7u45 security update released today.

Our users get a security warning every time they log into Oracle applications: "Running applications by UNKNOWN publishers will be blocked in a future release because it is potentially unsafe and a security risk". This caused our support desk to be flooded with calls.

Our applications are running on an internal network so we are using a self-signed certificate. Will we be required to obtain a certificate from a CA for each EBS environment even though it is running on our internal network?

It is my understanding that when 7u51 is released in January 2014 that our EBS environments will be blocked unless they are signed with a valid certificate from a CA. Is that correct?

It was great to see you at OpenWorld.

Regards,
Dawna

Posted by Dawna Roberts on October 16, 2013 at 04:15 PM PDT #

Hi Steven

We have the same problem as Dawna after the 7u45 update.

Please advise on the road forward.

Thanks
Pieter

Posted by Pieter Viljoen on October 17, 2013 at 01:17 AM PDT #

Hi Dan, Dawna and Peiter,

As these questions are all in the same area of Java security I shall try to cover all your queries within this response.

Trying to access Java content that has been signed with a self-signed certificate has been blocked in the last few JRE 7 releases but only if using JRE's 'Very High' security setting (the default is 'High'). This will become the default behaviour in a later release of JRE.

Signing Jar files needs to be done using a 'code signing certificate' from a trusted CA either official (e.g. verisign, thawte etc.) or an in-house authority. You only need one such certificate, you are then the publisher and can use that same certificate across as many Oracle E-Business Suite environments as you wish.

I won't go into the full details here, but once you have set this up on one environment you simply copy certain files across to your other environments (e.g $APPL_TOP/admin/adsign.txt, adkeystore.dat etc.) and regenerate your jar files. That environment will then also be signed with the official certificate.

To reiterate you only need ONE code signing certificate.

Further details on this and other set up steps and information will be released in a new enhanced jar signing document that will be released very soon.

Regards,
Tim.

Posted by Tim Mervyn on October 17, 2013 at 12:52 PM PDT #

Hi Tim,

is there a specific note on signing the jar file, that you recommend ?
Is it difficult? Will our java staff be familiar, or is there anything special for EBS that is needed? Even if I use a CA, what can I expect will be needed?

Thanks,
Cindi

Posted by Cindi Stein on October 17, 2013 at 03:09 PM PDT #

Hi, Cindi,

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 02:26 PM PDT #

Maybe this helps with signed jar files and trusted certificates?

http://eriksekeris.blogspot.nl/2013/11/oracle-forms-using-jacob-and-java-7.html

Posted by guest on November 18, 2013 at 12:08 PM PST #

Hello, Guest,

The linked article describes a process for manually extracting and then trusting a self-signed certification. This must be done by every EBS end-user.

The linked article may meet that author's requirements, but it is unlikely to meet the requirements of the vast majority of our E-Business Suite customers.

It is much more efficient for this to be done centrally by an EBS system administrator. We strongly recommend that all sysadmins simply sign their JAR files with a code-signing certificate.

Regards,
Steven

Posted by Steven Chan on November 19, 2013 at 09:33 AM PST #

Hi Steven,

How shall i know do i have to follow inhouse certificate signing or official CA signing as mention in oracle support note id 1591073.1??

Thanks
Kaushik

Posted by Kaushik on November 22, 2013 at 06:00 AM PST #

Kaushik,

Customers should start signing JAR files now. Please refer to the following blog article:
Sign E-Business Suite JAR Files Now
https://blogs.oracle.com/stevenChan/entry/sign_e_business_suite_jar

Thanks,
Elke

Posted by Elke Phelps (Oracle Development) on November 22, 2013 at 02:44 PM PST #

Hi Steven, Elke,

Can we run JRE 7 64-Bit on Solaris 10 for R12.1.3?

Thanks,
Matt

Posted by Matt Pullen on February 13, 2014 at 11:03 AM PST #

hi Matt -
If you're referring to the client side JRE, there is no issue in running the 64-bit JRE 7 for Windows (following the MOS Note 393931.1) hosted on a Solaris 10 server for use on Windows clients.
For the server side Java on Solaris or any other server platform, support in 12.1 is only for 32-bit Java (see MOS Note 1467892.1's Section 2: Upgrading to Latest JDK 7.0 on Application Tier Nodes).
Regards,
John

Posted by John Abraham on February 17, 2014 at 01:10 PM PST #

i need to download for academic purposes

Posted by guest on May 04, 2015 at 12:20 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« July 2015
SunMonTueWedThuFriSat
   
1
3
4
5
7
8
9
11
12
18
19
21
23
25
26
27
29
30
31
 
       
Today