X

The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

JRE 1.8.0_261 Certified with EBS Releases 12.2 and 12.1

Tahir Ahmad, and contributing authors: Elke Phelps and Tim Mervyn

(17-JUL-2020 Update:  The JRE 1.8.0_261 update is available with Patch 31311324)

We are pleased to announce that the Java Runtime Environment (JRE) 1.8.0_261 (8u261) on the JRE 8 codeline is now certified with Oracle E-Business Suite Releases 12.1 and 12.2.  This update is available with Patch 31311324

This article answers some questions you may have on the subject.

Is it a requirement to use Java Web Start with this JRE update?

While it is not a prerequisite to use Java Web Start for this latest Java CPU, please take another note of our previous guidance about moving to Java Web Start right away, and particularly ahead of September 2020.
 
You should uptake this latest Java CPU regardless of whether you are currently using Java Web Start or Java Plug-in on your client tier.

Note:  September 2020 is an important deadline for you if you are still using the Java Plug-in. Oracle Java team's plans to continue shipping the components required to launch Java applets on Internet Explorer 11 using Java Plug-in, and Oracle E-Business Suite Support team's ability to help customers still using Java Plugin are confirmed only through September 2020. Beyond this date, it will be increasingly complicated to receive any new fixes for Oracle E-Business Suite issues specific to Java Plug-in.

How do I get support adopting this latest Java CPU?

If you are using Java Web Start and require assistance with applying this CPU, you can log a service request for assistance from the Java Support organization.

For those of you still in transition to Java Web Start, refer to the following in our recently published My Oracle Support note, FAQ: Essentials of Java Usage in Oracle E-Business Suite (MOS Note 2510500.1):

Where are the JRE 8 requirements for EBS documented?

Full requirements for using Oracle E-Business Suite Releases 12.2 and 12.1 with JRE 8 are listed in the following documents:

Are there special considerations for running JRE 8 on Mac?

JRE 8 can be used with Oracle E-Business Suite 12.2 and 12.1 on Mac. To see a list of browsers and JRE versions certified on different macOS versions, refer to:

References

Related Articles

Join the discussion

Comments ( 5 )
  • Abe Friday, July 17, 2020
    Hello,
    There are two version of JRE 1.8.0_261, 1.8_261b12 and 1.8_261b33. The readme for both does not provide any details.
    Is there a recommendation for which version to use with EBS 12.1 and 12.2?
  • Tahir Ahmad [Oracle Development] Monday, July 20, 2020
    Hello Abe,

    Thank you for question.

    We recommend EBS customers to almost always take the latest public CPU for JRE 8 on the client tier. At this point in time, this is available via Patch 31311324 (corresponds to JRE 1.8_261b12), and we have updated it in the blog article above.

    JRE 1.8_261b33 is a Bundled Patch Release (BPR).

    The contents of these are documented in Java 8 Update Release Notes:
    https://www.oracle.com/java/technologies/javase/8u-relnotes.html

    The long answer, which should help customers understand if they ever need to deviate from the CPU, is explained in My Oracle Support Note 2510500.1, "FAQ: Essentials of Java Usage in Oracle E-Business Suite".
    https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=2510500.1&id=2510500.1

    Please refer to the answer to question 14 in the above document: "How should Oracle E-Business Suite customers determine which JRE update to use on the client tier at any given point in time?"
  • Larry Baugh Thursday, July 30, 2020
    Hi Tahir,

    Thank you as always for the great information on the blog!

    Regarding the Sep 2020 Plugin support issue, I'm trying to answer a "what does this actually mean for us?" question as part of justifying the move to Java Web Start. Are we saying that we could potentially lose the capability for launching the EBS forms if we do not uptake the Java Web Start? For example, if some IE 11 update is pushed out that disables the NPAPI capability, we'd be dead in the water? Is that the biggest risk?

    Thanks!
    Larry
  • Tahir Ahmad [Oracle Development] Tuesday, August 4, 2020
    Hi Larry, Thank you for your question.

    I will respond in 2 parts due to character limitation with the comments:

    Part 1:
    From Java team's perspective, Java Plug-in has effectively been in Sustaining Support since April 2019, and the 18 month extension for EBS customers is expiring in September 2020.

    EBS customers who have not yet finished moving to Java Web Start, should strongly consider the following factors when trying to answer questions such as "what does this actually mean for us?" or "what if we are not done moving to Java Web Start by September 2020?". I am sure there are additional considerations as well, and given that different customers will assess risks differently for their respective organizations, the following is simply my humble attempt to provide a set of factors to consider:

    1. Customers should compare the obvious implications of staying on a product that has been effectively in Sustaining Support since April 2019 (Java 8 Plugin) vs the obvious benefits of immediately moving to a product that is already announced to be in premier or extended support until at least 2030 (Java 8 Web Start). These dates are covered in Oracle Lifetime Support Policy for Oracle Fusion Middleware:
    https://www.oracle.com/us/assets/lifetime-support-middleware-069163.pdf

    2. My Oracle Support Knowledge Document 2511148.1 (requires login), explains this in more detail. It points out that escalations on SR's related to Java Plugin are not allowed, possible inability for Oracle to resolve issues related to Java Plugin due to technical reasons and the likelihood of significant delays in issue resolution. It also explains the contingency on Microsoft continuing to support underlying API's to launch Applets on Internet Explorer, which is the issue you also mention in your comment above.
    https://support.oracle.com/epmos/faces/DocumentDisplay?id=2511148.1
  • Tahir Ahmad [Oracle Development] Tuesday, August 4, 2020
    Larry - here's the continuation of my response

    Part 2:
    3. EBS Customers should strongly consider that if they still choose to stay on Java Plug-in, they may not get enough notice if Microsoft or Java team decide to, or have to, remove the API's that support Java Plugin.

    In addition to the above knowledge document, this is also stated in Java SE Support Roadmap document as follows:
    "The Java Plugin (Java Applets) remains updated in Java 8, but may be removed at any time in a future release"
    https://www.oracle.com/java/technologies/java-se-support-roadmap.html

    The following blog article from Java PM team also explains the same:
    "Oracle has no plans to remove the components required to launch Applets in Internet Explorer 11 from Java SE 8 but may do so with little or no warning."
    https://blogs.oracle.com/java-platform-group/java-client-roadmap-updates

    4. One important implication, if Microsoft or Java team were to remove support of the underlying API's, is that impacted customers could end up possibly having to stay on an IE version or a Java version that does not have the latest security fixes.

    5. To sum all of this up, since March 2019, EBS guidance has been for customers to move to Java Web Start immediately. Customers should note that moving to Java Web Start following EBS My Oracle Support Knowledge Document 2188898.1 does NOT take away the ability of individual end users to still keep using Java Plugin on IE 11 subject to considerations I have tried to explain above. This is explained in Section 5 (Configuring and Enabling Java Web Start) of the the aforementioned document.

    Hope this helps. Please feel free to let us know if you have any additional questions.

    Regards,
    Tahir
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.

Recent Content