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 codeline are 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 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.

What‘s new in this release?

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

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

Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_65) and only upgrade to the PSU release (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 are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it.

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

All patches required for ensuring full compatibility of the E-Business Suite with JRE 8 are documented in these Notes:

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users 

This JRE release is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:

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 dates 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 Support is not available for Java SE Deployment Technology.  It is more important than ever for you to stay current with new JRE versions.

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

  • You can continue to do so 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:

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

  • You can continue to do so 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:

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

  • You can continue to do so 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:

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

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are 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 and 7 desktop clients. Note that there are 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 that 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 is an update available.

Enabling the JRE Auto-Update feature on desktops with JRE 6 installed will have no effect.

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

Enabling the JRE Auto-Update feature on desktops with JRE 8 installed will apply JRE 8 updates.

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?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) desktops.  For details, see:

Will EBS users be 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 certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

References

Related Articles

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

时间: 2024-11-08 09:29:06

JRE 1.8.0_65/66 Certified with Oracle E-Business Suite的相关文章

Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 (文档 ID 393931.1)

In This Document Section 1: Overview Section 2: Pre-Upgrade Steps Section 3: Upgrade and Configuration Section 4: Post-installation Steps Section 5: Known Issues Section 6: Appendices This document covers the procedure to upgrade the version of the J

Oracle's Business Intelligence Applications Configuration Manager 基本概念

Oracle's Business Intelligence Applications Configuration Manager :BIACM Once the BIAPPS installation is completed, the newly introduced web-based JAVA applications, BI Configuration Manager (BIACM) and Functional Set-up Manager (FSM), are available

Oracle BIEE (Business Intelligence) 11g 11.1.1.6.0 学习(1)安装

ORACLE 出品的产品绝对都可以称得上装X神器:安装文件一定要大(小水管不让你下个三天三夜那都不叫oracle),系统内存必须得大.硬盘空间必须足够多.安装时间必须足够长.各种配置必须足够复杂.学习曲线必须足够陡峭...最重要的是 产品价格必须足够高!只卖贵的,不卖对的:) 硬件条件: 1.内存起码4G(少于这个数,就建议别玩了) 2.如果在虚拟机里玩,硬盘建议至少留60G左右 软件环境: 1.WINDOWS 2008 R2 2.ORACLE DATABASE 11G R2 (以上软件环境针对

Oracle发布OSS suite新版本,适应开放的新环境

运营支撑系统(OSS)市场正在面临一些重大的变化,原因在于开放的软件定义网络(SDN)和网络功能虚拟化(NFV)技术对OSS专有模型施加了压力,包括Oracle在内的一些较大的OSS供应商已经开始采取措施应对这种变化. 现有的OSS通常比较传统而私有化,它需要做一些改变才能适应这个开放的新环境.上周,Oracle发布了OSS suite新版本来适应虚拟化环境.该版本新增的功能包括:动态地提供运营商级的以太网电路.目录导出功能(允许服务信息复制数据和自动化创建服务).改良的多订单处理程序(针对需要

Oracle BIEE (Business Intelligence) 11g 11.1.1.6.0 学习(2)RPD资料档案库创建

BI创建(数据)分析.仪表盘.报表前,都需要对数据进行建模,在oracle biee里称为创建"资料档案库"-该文件后缀为RPD,所以一般也称为创建RPD文件. 步骤: 1.从windows开始菜单里,找到"BI 管理",如下图: 2.点击工具栏第一个按钮"创建"一个(脱机/离线的)RPD文件,这里我们命名为Scott.rpd,同时注意记好密码,比如Admin123 3.选择数据源(即创建到数据库的连接) 注1:上图中的数据源名称,其实就是ora

Oracle BIEE (Business Intelligence) 11g 11.1.1.6.0 学习(3)创建一个简单的分析

1.如果BIEE安装在本机,直接登录http://localhost:9704/analytics/ 点击右上方导航菜单中的"新建->分析" 2.选择上节创建的RPD文件中的SCOTT主题区域 3.这里会看到如下界面,左侧的树对应的是RPD文件中最左侧[表示]层中的模型-可以把它当成"表"来看,随便在"表"的字段名上双击,就可以添加到右侧的"所选列"区域,先参照下图,随便选几列过过瘾 4.切换到[结果]视图,一切顺利的话

Using Load-Balancers with Oracle E-Business Suite Release 12 (Doc ID 380489.1)

  Using Load-Balancers with Oracle E-Business Suite Release 12 (Doc ID 380489.1) Modified: 12-Jun-2013 Type: WHITE PAPER   Using Load-Balancers with Oracle E-Business Suite Release 12 Last Updated:  May 17, 2013 The most current version of this docum

Oracle 学习之 11g Clone 安装

如果你需要安装的数据库服务器比较多,使用图形化方式安装数据库软件的速度还是很慢,而且也比较麻烦.Oracle 11g 提供了Clone安装的方法. 步骤如下: 使用正常方法在服务器A上安装好Oracle. 将A机器上的$ORACLE_HOME打包,db_home1.zip . 将B机器的环境准备好,如建立用户.建立用户.修改内核参数,修改环境变量等等. 将zip包copy到B服务器,解压到任意目录. 执行Clone命令 A机器上打包 [[email protected] oracle]# zip

【翻译自mos文章】在RHEL7 or OEL7上安装oracle 11.2.0.4 db时的要求

在RHEL7 or OEL7上安装oracle 11.2.0.4 db时的要求 来源于: Requirements for Installing Oracle 11.2.0.4 RDBMS on RHEL7 or OL7 64-bit (x86-64) (文档 ID 1962100.1) 适用于: Oracle Database - Standard Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2] Oracle Database - E