Monday Aug 24, 2015

JRE 1.8.0_60 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_60 (a.k.a. JRE 8u60-b27) 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.

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

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

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:

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. 


Friday Aug 07, 2015

Windows 10 Certified with Oracle E-Business Suite

Windows 10 logoMicrosoft Windows 10 (32-bit and 64-bit) is certified as a desktop client operating system for end-users accessing Oracle E-Business Suite 11.5.10.2, 12.1, and 12.2 with the following components.

EBS 12.1 and 12.2

  • Browsers
  • Microsoft Internet Explorer 11
  • Mozilla Firefox ESR 38
  • Chrome 44 and higher (HTML/OA Framework modules only)
  • Java client plug-ins
  • JRE 1.8.0_51 and higher
  • JRE 1.7.0_85 and higher

EBS 11.5.10.2

  • Browsers
  • Microsoft Internet Explorer 11
  • Mozilla Firefox ESR 38
  • Java client plug-ins
  • JRE 1.8.0_51 and higher
  • JRE 1.7.0_85 and higher
Later JRE 7 and 8 releases on Windows 10

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops.  This applies to Windows 10 desktops, too, for the JRE releases list above.

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 7 or 8 releases to your EBS users' Windows 10 desktops.

Pending certifications 

Desktop Client/Server Products

The certification of our various Client/Server products, for example JDeveloper OA Extensions, Forms Developer and Workflow Builder against Windows 10 are in progress. For a full list of products see  Recommended Set Up for Client/Server Products with Oracle E-Business Suite 11i & R12 (Note 277535.1). The certification matrix within this document will be updated as these are completed.

Microsoft Edge Browser

The certification of Microsoft Edge on Windows 10 with Oracle E-Business Suite 12.1 and 12.2 is currently in progress. There are no plans to certify this browser for Oracle E-Business Suite 11i.

Oracle E-Business Suite R12 has two interfaces: a web-based (OA Framework/HTML) model for modules like iProcurement and iStore, and Oracle Forms/Java based model for our professional services modules like Oracle Financials. Microsoft Edge does not support Java and will therefore only be certified for E-Business Suite customers running web-based (HTML / OA Framework) EBS products. Running Java-based EBS products with Edge will not feasible.

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.   

References

Related Articles


Wednesday Jul 29, 2015

Transportable Database 12c Certified for EBS 12.2 Database Migration

Database migration across platforms of the same "endian" (byte ordering) formats using the Transportable Database (TDB) process is now certified for Oracle E-Business Suite Release 12.2 with Oracle Database 12c Release 1 (12.1.0).

The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using SQL*Plus (connected as SYSDBA):

SQL> select platform_name, endian_format from v$transportable_platform;

The following is a list of relevant platforms certified for Oracle E-Business Suite Release 12 (12.2) with Oracle Database 12c Release 1 on the database tier:

Big Endian Platforms
Little Endian Platforms
Oracle Solaris on SPARC
Linux x86-64
HP-UX Itanium
Oracle Solaris on x86-64
IBM AIX on POWER Systems
Microsoft Windows x641
IBM: Linux on z Systems

1 Note: Microsoft Windows x64 is not yet certified and will be announced separately at a later date.

Using Transportable Database is the fastest method for migration between platforms of the same endian format. A requirement of this migration process is that the source and target database versions must match (including patch set version), so database upgrades as part of the migration cannot be done.

For migration between platforms of different endian formats, users must use alternative migration methods such as export/import (datapump).

References

Related Articles


Friday Jul 24, 2015

Quarterly EBS Upgrade Recommendations: July 2015 Edition

We've previously provided advice on the general priorities for applying EBS updates and creating a comprehensive maintenance strategy.   

Here are our latest upgrade recommendations for E-Business Suite updates and technology stack components.  These quarterly recommendations are based upon the latest updates to Oracle's product strategies, latest support timelines, and newly-certified releases

You can research these yourself using this Note:

Upgrade Recommendations for July 2015

  1. EBS 11i users should upgrade to 12.1.3 or 12.2.  Before upgrading, 11i users should be on the minimum 11i patching baseline.

  2. EBS 12.0 users should upgrade to 12.1.3 or 12.2.  Before upgrading, 12.0 users should be on the minimum 12.0 patching baseline.

  3. EBS 12.1 users should upgrade to 12.1.3 RPC3 or 12.2.

  4. EBS 12.2 users should upgrade to EBS 12.2.4, Database 11.2.0.4 or 12.1.0.2, the March 2015 AD/TXK tools, StartCD 49, and FMW 11.1.1.7.

  5. Users staying on EBS 11i and 12.1 should upgrade to Database 11.2.0.4 or 12.1.0.2.

  6. EBS 11i and 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 3 11.1.2.3.0.

  7. Oracle Internet Directory 10g users should upgrade to Oracle Internet Directory 11g 11.1.1.9.

  8. Oracle Discoverer users should migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11g 11.1.1.7.

  9. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.7 or upgrade to Portal 11g 11.1.1.6.

  10. All Windows desktop users should migrate from older Java releases (including JInitiator) to JRE 1.6.0_101 or later 1.6 updates or JRE 1.7.0_85 or later 1.7 updates or JRE 1.8.0_51 or later 1.8 updates.

  11. All EBS 11i, 12.0, 12.1, and 12.2 users must sign their environment's JAR files now.

  12. All Firefox users should upgrade to Firefox Extended Support Release 38.

  13. All EBS 11i, 12.0, 12.1, 12.2 users should apply the July 2015 Critical Patch Update.

  14. Windows XP and Office 2003 users should upgrade to later versions.

  15. All EBS customers on Exalogic and Exadata should follow the latest recommendations.

  16. All EBS customers should switch from Secure Socket Layer (SSL) to Transport Layer Security (TLS).

Related Articles

Wednesday Jul 22, 2015

Can You Use IE 11 Enterprise Mode or Compatibility View With EBS?

Microsoft IE LogoMicrosoft Internet Explorer 11 offers two options for enabling backwards-compatibility:

You should not use either of these with Oracle E-Business Suite.  These two modes have no benefit for EBS end-users. 

These two methods are not needed for EBS compatibility.  You should ensure that you have applied all of the latest EBS server-side patches to avoid any compatibility issues:

Related Articles

Wednesday Jul 15, 2015

JRE 1.8.0_51 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_51 (a.k.a. JRE 8u51-b16) 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?

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.

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 8 are documented in these Notes:

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

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:

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. 


JRE 1.7.0_85 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_85 (a.k.a. JRE 7u85-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

Java JRE 1.6.0_101 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_101 (a.k.a. JRE 6u101-b14) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12.x 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?

New EBS installation scripts

This JRE release is the first with a 3-digit Java version. Installing this in your EBS 11i and 12.x environments will require new installation scripts.  See the documentation listed in the 'References' section for more detail.

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 Deploying JRE documentation for your EBS release for details.

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:

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?

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here: 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.

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

Thursday May 28, 2015

11gR2 Transportable Database Certified for EBS 12.2 Database Migration

Database migration across platforms of the same "endian" (byte ordering) formats using the Transportable Database (TDB) process is now certified for Oracle E-Business Suite Release 12.2 with Oracle Database 11g Release 2 (11.2.0).

The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba):

    SQL> select platform_name, endian_format from v$transportable_platform;

Here's a list of relevant platforms certified for the EBS R12 (12.2) with 11gR2 on the database tier:

 Big Endian Platforms
 Little Endian Platforms
 Oracle Solaris on SPARC  Linux x86-64
 HP-UX Itanium  Oracle Solaris on x86-64
 IBM AIX on POWER Systems  MS Windows x64
 IBM: Linux on System z

Using Transportable Database is the fastest method for migration between platforms of the same endian format. A requirement of this migration process is that the source and target Database versions must match (including patch set version), so database upgrades as part of the migration cannot be done.

For migration between platforms of different endian formats, users must use alternative migration methods such as export/import (datapump).

References

Related Articles

Tuesday May 19, 2015

Firefox ESR 38 Certified with EBS 12.2 and 11i

Firefox ESR logo

Mozilla Firefox 38 Extended Support Release (ESR) is certified as a Windows-based client browser for Oracle E-Business Suite 11i and 12.2.

The certification with EBS 12.1 is pending; see below.

What is Mozilla Firefox ESR?

Mozilla offers an Extended Support Release based on an official release of Firefox for organizations that are unable to mass-deploy new consumer-oriented versions of Firefox every six weeks.  From the Mozilla ESR FAQ:

What does the Mozilla Firefox ESR life cycle look like?

Releases will be maintained for approximately one year, with point releases containing security updates coinciding with regular Firefox releases. The ESR will also have a two cycle (12 week) overlap between the time of a new release and the end-of-life of the previous release to permit testing and certification prior to deploying a new version.

Maintenance of each ESR, through point releases, is limited to high-risk/high-impact security vulnerabilities and in rare cases may also include off-schedule releases that address live security vulnerabilities. Backports of any functional enhancements and/or stability fixes are not in scope.

At the end of the support period for an ESR version:

  • the release will reach its end-of-life
  • no further updates will be offered for that version
  • an update to the next version will be offered through the application update service

E-Business Suite to be certified with Firefox Extended Support Releases

New personal versions of Firefox are released roughly every six weeks.  It is impractical for us to certify these new personal versions of Firefox with the Oracle E-Business Suite because a given Firefox release is generally obsolete by the time we complete the certification.

From Firefox 10 and onwards, Oracle E-Business Suite is certified only with selected Firefox Extended Support Release versions. Oracle has no current plans to certify new Firefox personal releases with the E-Business Suite.

EBS patching policy for Firefox compatibility issues

Mozilla stresses their goal of ensuring that Firefox personal versions will continue to offer the same level of application compatibility as Firefox Extended Support Releases. 

Oracle E-Business Suite Development will issue new E-Business Suite patches or workarounds that can be reproduced with Firefox Extended Support Releases.  If you report compatibility issues with Firefox personal releases that cannot be reproduced with Firefox Extended Support Releases, your options are:

  1. Deploy a certified Firefox Extended Support Release version instead of the Firefox personal version
  2. Report the incompatibility between Firefox ESR and Firefox personal to Mozilla
  3. Use Internet Explorer (on Windows) or Safari (on Mac OS X) until Mozilla resolves the issue
EBS Compatibility with Firefox ESR security updates

Mozilla may release new updates to Firefox ESR versions to address high-risk/high-impact security issues.  These updates are considered to be certified with the E-Business Suite on the day that they're released.  You do not need to wait for a certification from Oracle before deploying these new Firefox ESR security updates.

Certified desktop operating systems
  • Windows 8.1 (32-bit and 64-bit)
  • Windows 7 SP1 (32-bit and 64-bit)
  • Windows Vista SP2

References

Pending Certification

The certification of Firefox ESR 38 with Oracle E-Business Suite 12.1 is still in progress. An interoperability patch is required for this certification; this patch is being prepared. 

EBS 12.1 users should remain on Firefox ESR 31 for now. This certification will be announced in a separate blog article.

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog.


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. 


Wednesday Apr 22, 2015

Quarterly EBS Upgrade Recommendations: April 2015 Edition

We've previously provided advice on the general priorities for applying EBS updates and creating a comprehensive maintenance strategy.   

Here are our latest upgrade recommendations for E-Business Suite updates and technology stack components.  These quarterly recommendations are based upon the latest updates to Oracle's product strategies, latest support timelines, and newly-certified releases

You can research these yourself using this Note:

Upgrade Recommendations for April 2015

  1. EBS 11i users should upgrade to 12.1.3 or 12.2.  Before upgrading, 11i users should be on the minimum 11i patching baseline.

  2. EBS 12.0 users should upgrade to 12.1.3 or 12.2.  Before upgrading, 12.0 users should be on the minimum 12.0 patching baseline.

  3. EBS 12.1 users should upgrade to 12.1.3 RPC3 or 12.2.

  4. EBS 12.2 users should upgrade to 12.2.4, the March 2015 AD/TXK tools, StartCD 49, and FMW 11.1.1.7.

  5. Users staying on EBS 11i and 12.1 should upgrade to Database 11.2.0.4 or 12.1.0.2.

  6. Users upgrading to EBS 12.2 should upgrade to Database 11.2.0.4.

  7. EBS 11i and 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 2 11.1.2.2.0.

  8. Oracle Internet Directory 10g users should upgrade to Oracle Internet Directory 11g 11.1.1.7.

  9. Oracle Discoverer users should migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11g 11.1.1.7.

  10. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.7 or upgrade to Portal 11g 11.1.1.6.

  11. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_95 or later 1.6 updates or JRE 1.7.0_79 or later 1.7 updates or JRE 1.8.0_45 or later 1.8 updates.

  12. All EBS 11i, 12.0, 12.1, and 12.2 users must sign their environment's JAR files now.

  13. All Firefox users should upgrade to Firefox Extended Support Release 31.

  14. All EBS 11i, 12.0, 12.1, 12.2 users should apply the April 2015 Critical Patch Update.

  15. Windows XP and Office 2003 users should upgrade to later versions.

  16. All EBS customers on Exalogic and Exadata should follow the latest recommendations.

  17. All EBS customers should switch from Secure Socket Layer (SSL) to Transport Layer Security (TLS).

Related Articles

Thursday Apr 16, 2015

JRE 1.8.0_45 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_45 (a.k.a. JRE 8u40-b14) 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.

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

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

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:

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. 


JRE 1.7.0_79 and 1.7.0_80 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_79 (a.k.a. JRE 7u79-b15) and 1.7.0_80 (7u80-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?

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

  • CPU Release is JRE 1.7.0_79
  • PSU Release is JRE 1.7.0_80

Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.7.0_79) and only upgrade to the PSU release (JRE 1.7.0_80) if they require a specific bug fix.  For further information and bug fix details see Java 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 7 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 7 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 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:

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.

JRE 7 End of Public Updates

This is 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

Java JRE 1.6.0_95 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_95 (a.k.a. JRE 6u95-b12) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12.x 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 in this Java release?

This JRE update is a CPU release. If you are running on the JRE 6 stream, it is strongly recommended that you upgrade to this latest version of the JRE 6 Plug-in.

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

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.

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 Deploying JRE documentation for your EBS release for details.

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.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

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:

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:

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

Tuesday Apr 14, 2015

EBS OA Extensions for JDeveloper Certified with Windows 8.1

Jdeveloper logoWhen you create extensions to Oracle E-Business Suite OA Framework pages, you must use the version of Oracle JDeveloper shipped by the Oracle E-Business Suite product team. 

The version of Oracle JDeveloper is specific to the Oracle E-Business Suite Applications Technology patch level, so there is a new version of Oracle JDeveloper with each new release of the Oracle E-Business Suite Applications Technology patchset. These patchsets must be certified for the desktop operating system that is used to develop the OA Framework extensions. 

The latest updates of the OA Extensions for JDeveloper are certified with Windows 8.1.  There are updates for EBS 12.2.4, 12.2.3, 12.1.3, and 11.5.10.2.

For details, see:

Pending Certifications

The certification of the following Desktop Client tools on Windows 8.1 is still pending:

  • BI Publisher Desktop Tools (formally XML Publisher)
  • Discoverer Administrator/Desktop
  • Sales for Handhelds (Outlook Sync Client)
  • Warehouse Builder Client

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.   

Related Articles

Wednesday Mar 04, 2015

JRE 1.8.0_40 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_40 (a.k.a. JRE 8u40-b25) 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.

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

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

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:

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) and 10.9 (Mavericks) 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. 


Tuesday Feb 10, 2015

EBS 12.2 Certified on Microsoft Windows Server 2012 R2

Microsoft Windows Server logoOracle E-Business Suite Release 12.2 (12.2.3 and higher) is now certified on Microsoft Windows Server 2012 R2. For details, see:

The following editions of Microsoft Windows Server 2012 R2 are certified with Oracle E-Business Suite Release 12.2:

  • Microsoft Windows Server 2012 R2 Standard
  • Microsoft Windows Server 2012 R2 Datacenter

The above operating systems running as guests on Windows Server 2012 Hyper-V are also certified for Oracle E-Business Suite Release 12.2.

Users should also review the Microsoft Windows Server Catalog for information regarding hardware certified or supported with these operating system versions.

Unlike our certification of EBS 12.1.3 on Windows Server 2012 R2, E-Business Suite 12.2 can be installed directly on the platform with the use of the latest startCD (version 49 or higher) with Rapid Install.

Related Articles

Friday Feb 06, 2015

Internet Explorer 11 Certified with E-Business Suite 11.5.10.2

Microsoft IE logoMicrosoft Internet Explorer 11 is now certified as a desktop client browser for Oracle E-Business Suite Release 11.5.10.2.  This follows our previous certification of IE11 with EBS 12.1 and IE11 with EBS 12.0 and 12.2.  The certified desktop operating systems are:

  • Windows 7 Service Pack 1 (32-bit or 64-bit)
  • Windows 8.1 Update 1 (32-bit or 64-bit)

Certified IE 11 Modes

Internet Explorer 11 can be used in "Desktop Mode" on Windows 8.1.  Running IE 11 from the "Modern" (Metro) Start Screen is not certified.

Due to display issues with certain FWK pages when using IE9 or IE10 we previously recommended running E-Business Suite using the browsers 'compatibility mode'.  These display issues have now been fixed for IE11-- you can now access your E-Business Suite 11.5.10.2 environments without using 'compatibility mode' in IE 11.

IE 11 includes an "Enterprise Mode" which can be used to emulated Internet Explorer 8 behaviour and provide compatibility with earlier browser standards.  You should not use "Enterprise Mode" with Oracle E-Business Suite.  EBS compatibility with IE 11 requires server-side patches. Enabling "Enterprise Mode" in IE 11 is not needed and will not resolve all compatibility issues.

JRE 6, 7, and 8 are certified with EBS

Java Runtime Environment (JRE) Versions 6, 7, and 8 are certified with EBS. 

There appears to be some inaccurate information lying about on the web that claims that JRE 1.7 is not certified with the E-Business Suite. 

This is incorrect. 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

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

"JInitiator version too low" errors

Some non-Oracle staff are claiming that "JInitiator version too low" errors confirm this incompatibility and lack of certification.

In fact, if you're getting a "JInitiator version too low" error, it means that you've missed applying the Forms patch required to enable JRE 1.7 compatibility. Simply apply that patch and your EBS environment is ready for JRE 1.7 clients.

References

Related Articles


Wednesday Jan 21, 2015

JRE 1.8.0_31 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_31 (a.k.a. JRE 8u31-b13) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 12.0, 12.1, and 12.2 for Windows and Mac OS X 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.

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

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

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:

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 this 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) and 10.9 (Mavericks) desktops.  For details, see:

The certification of JRE 8 for Mac OS X 10.10 (Yosemite) desktops is planned.  

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates.

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. 


JRE 1.7.0_75 and 1.7.0_76 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_75 (a.k.a. JRE 7u75-b13) and 1.7.0_76 (7u76-b13) 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, 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 7.

  • CPU Release is JRE 1.7.0_75
  • PSU Release is JRE 1.7.0_76

It is recommended that Oracle E-Business Suite customers use the CPU release (JRE 1.7.0_75) and only upgrade to the PSU release (JRE 1.7.0_76) if they require a specific bug fix.  For further information and bug fix details see Java 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.

JRE 1.7.0_75  (7u75) 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.

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:

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.

JRE 7 End of Public Updates

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 Extended Support in April 2015.

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 this January 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.9 can run JRE 7 or 8 plug-ins.  See these articles:

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

Java JRE 1.6.0_91 Certified with Oracle E-Business Suite

Java logo

The latest Java Runtime Environment 1.6.0_91 (a.k.a. JRE 6u91-b13) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12.x 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, 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 in this Java release?

JRE 1.6.0_91  (6u91-b13) is a CPU release. If you are running on the JRE 6 stream, it is strongly recommended that you upgrade to this latest version of the JRE 6 Plug-in.

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

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.

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 Deploying JRE documentation for your EBS release for details.

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.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

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:

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:

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.9 can run JRE 7 or 8 plug-ins.  See these articles:

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

Friday Jan 16, 2015

Internet Explorer 11 Certified with E-Business Suite 12.2 and 12.0

Microsoft IE logoMicrosoft Internet Explorer 11 is now certified as a desktop client browser for Oracle E-Business Suite Release 12.2 and 12.0.  This follows our previous certification of IE11 with EBS 12.1.  The certified desktop operating systems are:

  • Windows 7 Service Pack 1 (32-bit or 64-bit)
  • Windows 8.1 Update 1

Certified IE 11 Modes

Internet Explorer 11 can be used in "Desktop Mode" on Windows 8.1.  Running IE 11 from the "Modern" (Metro) Start Screen is not certified.

Due to display issues with certain FWK pages when using IE9 or IE10 we previously recommended running E-Business Suite using the browsers 'compatibility mode'.  These display issues have now been fixed for IE11-- you can now access your E-Business Suite 12.x environments without using 'compatibility mode' in IE 11.

 IE 11 includes an "Enterprise Mode" which can be used to emulated Internet Explorer 8 behaviour and provide compatibility with earlier browser standards.  You should not use "Enterprise Mode" with Oracle E-Business Suite.  EBS compatibility with IE 11 requires server-side patches. Enabling "Enterprise Mode" in IE 11 is not needed and will not resolve all compatibility issues.

EBS 12.2 Prerequisites

  • EBS 12.2.3 or later 12.2 updates
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher

EBS 12.0 Prerequisites

  • EBS 12.0.6
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher
JRE 6, 7, and 8 are certified with EBS

Java Runtime Environment (JRE) Versions 6, 7, and 8 are certified with EBS. 

There appears to be some inaccurate information lying about on the web that claims that JRE 1.7 is not certified with the E-Business Suite. 

This is incorrect. 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

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

"JInitiator version too low" errors

Some non-Oracle staff are claiming that "JInitiator version too low" errors confirm this incompatibility and lack of certification.

In fact, if you're getting a "JInitiator version too low" error, it means that you've missed applying the Forms patch required to enable JRE 1.7 compatibility. Simply apply that patch and your EBS environment is ready for JRE 1.7 clients.

Certifications with EBS 11i still pending

We plan to certify IE 11 with EBS 11i.  This certification us underway now and will be released soon.

If you're running EBS 11i, you must ensure that your mission-critical desktops remain on an earlier certified browsers until this certification is completed.  As of the time this article was published, certified browsers include IE 10 and Firefox ESR 31 for Windows desktops.

You can block automatic updates by using Microsoft's Internet Explorer 11 Blocker Toolkit:

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.    

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.

Friday Jan 09, 2015

EBS 12.1.3 Certified with Microsoft Windows Server 2012 R2

Microsoft Windows Server logoOracle E-Business Suite Release 12 (12.1.3) is now certified with Microsoft Windows Server 2012 R2 on both the application and database tiers through a certified migration of an existing Release 12 installation. Microsoft Windows Server 2012 R2 is a Windows x64 (64-bit) only operating system and is the latest Windows Server version.

Support of the E-Business Suite on this platform is achieved by a two-step process of migrating the Oracle Database first (as documented in the 11gR2 Database Tier Only Platform note), and then migrating the application tier using the process documented in the R12 Rapid Clone note. These steps and all requirements are outlined here:

The operating systems certified on this platform are:

  • Microsoft Windows Server 2012 R2 Standard
  • Microsoft Windows Server 2012 R2 Datacenter

Pending Certifications 

Certification for Rapid Install of Oracle E-Business Suite Release 12.2 on Microsoft Windows Server 2012 R2 is in progress and will be announced separately.

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

Where can I find more information?

Related Articles

Monday Dec 29, 2014

Quarterly EBS Upgrade Recommendations: December 2014 Edition

(16-Jan-2015 Update to recommendation number 5:  Removed 11i from 12.1.0.2 and added to 12.1.0.1.  Removed 12.2 from 12.1.0.1 and added to 12.1.0.2)

We've previously provided advice on the general priorities for applying EBS updates and creating a comprehensive maintenance strategy.   

Here are our latest upgrade recommendations for E-Business Suite updates and technology stack components.  These quarterly recommendations are based upon the latest updates to Oracle's product strategies, latest support timelines, and newly-certified releases

You can research these yourself using this Note:

Upgrade Recommendations for December 2014

  1. EBS 11i users should upgrade to 12.1.3 or 12.2.  Before upgrading, 11i users should be on the minimum 11i patching baseline.

  2. EBS 12.0 users should upgrade to 12.1.3 or 12.2.  Before upgrading, 12.0 users should be on the minimum 12.0 patching baseline.

  3. EBS 12.1 users should upgrade to 12.1.3 RP2 or 12.2.

  4. EBS 12.2 users should upgrade to 12.2.4 or the latest AD/TXK tools and StartCD 49.

  5. Oracle Database 10gR2, 11gR1, and 11gR2 users should upgrade to 12.1.0.1 (11i) or 12.1.0.2 (12.0/12.1, 12.2)

  6. EBS 11i and 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 2 11.1.2.2.0.

  7. Oracle Internet Directory 10g users should upgrade to Oracle Internet Directory 11g 11.1.1.7.

  8. Oracle Discoverer users should migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11g 11.1.1.7.

  9. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.7 or upgrade to Portal 11g 11.1.1.6.

  10. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_85 or later 1.6 updates or JRE 1.7.0_72 or later 1.7 updates or JRE 1.8.0_25 or later 1.8 updates.

  11. All EBS 11i, 12.0, 12.1, and 12.2 users must sign their environment's JAR files now.

  12. All Firefox users should upgrade to Firefox Extended Support Release 31.

  13. All EBS 11i, 12.0, 12.1, 12.2 users should apply the latest Critical Patch Update.

  14. Windows XP and Office 2003 users should upgrade to later versions.

  15. All EBS customers on Exalogic and Exadata should follow the latest recommendations.

Related Articles

Thursday Dec 04, 2014

JRE Support Ends Earlier than JDK Support

One of our Applications Technology Group architects recently drew my attention to an important change in Java support policies that I'd missed: support for client-based Java Runtime Environment (JRE) plug-ins now ends earlier than the support dates for server-based Java Development Kit (JDK) components.

Screenshot from Java Lifetime Support Policy document JDK JRE different dates

These dates are published here:

The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology (Java Web Start & Java Plug-in technologies) 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:

Related Articles

Wednesday Nov 19, 2014

EBS 12.0 & 12.1 DB Migration Using 12cR1 Transportable Tablespaces Now Certified


Database migration across platforms of different "endian" (byte ordering) formats using the Transportable Tablespaces (TTS) process is now certified for Oracle E-Business Suite Release R12 (12.0.6, 12.1.3) with Oracle Database 12c Release 1 (12.1.0). Migration between different platforms of the same "endian" format with 12c can be accomplished using export/import (datapump) utilities. 

This certification requires that the source database be 11gR2 (11.2.0.3 or higher) and the target database be 12cR1 (12.1.0.1 or higher).  

This migration process requires a patch delivered by our EBS Platform Engineering team that is 'Controlled', i.e. it requires a password obtainable through Oracle Support. We released the required patch in this manner to monitor customer issues and to gauge uptake.

The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba):

        SQL> select platform_name, endian_format from v$transportable_platform;

Here's a list of relevant platforms certified for the EBS R12 with 12cR1 on the database tier:

 

Big Endian Platforms
Little Endian Platforms
Oracle Solaris on SPARC
Linux x86-64
HP-UX Itanium
Oracle Solaris on x86-64
IBM AIX on POWER Systems
MS Windows x64

The use of Transportable Tablespaces can greatly speed up the migration of the data portion of the database - it does not affect metadata which must still be migrated using export/import.

We recommend that users initially perform a test migration with export/import on their database with the 'metrics=y' parameter to find out the relative size of data vs metadata in their database and to have a basis to compare any gains in timing. Generally speaking, the larger the relative size of data (as compared to metadata), the more likely it would be that TTS is suitable as a migration process to reduce downtime.

Pending Certifications

Testing with 12cR1 as the source is still pending.

Full transportable export/import, a new feature in 12c to move an entire database, is not certified for use with E-Business Suite databases yet. 

Transportable Database (TDB), a migration process for platforms of the same "endian" format, is also a pending 12cR1 certification exercise. 

References

 Related Articles


Friday Nov 14, 2014

Java JRE 8 Certified with Oracle E-Business Suite

Java logo

[Dec. 3, 2014 Update: JRE support dates are not the same as JDK support dates any longer.  Corrected support dates for JRE 6, 7, and 8.]

Java Runtime Environment 1.8.0_25 (a.k.a. JRE 8u25-b18) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 12.0, 12.1, and 12.2 for Windows and Mac OS X 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.

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

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

Availability of Server-Side Patches:  This certification requires patches to be applied to EBS 11i, 12.0, 12.1, and 12.2 servers.  Patches for 12.0 and 12.1 are available for:

  • Linux x86 (Oracle Linux 4, 5, 6; Red Hat Enterprise Linux 4, 5, 6)
  • Linux x86-64 (Oracle Linux 4, 5, 6; Red Hat Enterprise Linux 4, 5, 6; SLES 10,11) 
  • Oracle Solaris on SPARC (64-bit)(10, 11)

Patches for other server operating systems are pending. You can monitor the documentation for updates on platform availability.

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:

    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.

    Enabling the JRE Auto-Update feature on desktops with JRE 7 installed will only apply JRE 7 updates today. 

    In the future, enabling Auto-Update will upgrade JRE 7 to JRE 8.  For details, see:

    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) and 10.9 (Mavericks) desktops.  For details, see:

    The certification of JRE 8 for Mac OS X 10.10 (Yosemite) desktops is planned.  

    Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates.

    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. 


    Thursday Oct 16, 2014

    JRE 1.7.0_71 and 1.7.0_72 Certified with Oracle E-Business Suite

    Java logo

    Java Runtime Environment 1.7.0_71 (a.k.a. JRE 7u71-b14) and 1.7.0_72 (7u72-b14) 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 new in this release?

    Starting with JRE 1.7.0_71 Oracle will release a Critical Patch update (CPU) at the same time as the corresponding Patch Set Update (PSU) release for Java SE 7. It is recommended that Oracle E-Business Suite customers use the CPU release (JRE 1.7.0_71) and only upgrade to the PSU release (JRE 1.7.0_72) if they require a specific bug fix.  For further information and bug fix details see Java 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.

    JRE 1.7.0_71  (7u71) 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.

    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:

    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 X 10.9 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

    Java JRE 1.6.0_85 Certified with Oracle E-Business Suite

    Java logo

    The latest Java Runtime Environment 1.6.0_85 (a.k.a. JRE 6u81-b13) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12 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 new in in this Java release?

    JRE 1.6.0_85  (6u81-b13) is a CPU release. If you are running on the JRE 6 stream, it is strongly recommended that you upgrade to this latest version of the JRE 6 Plug-in.

    Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

    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.

    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 Deploying JRE documentation for your EBS release for details.

    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.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

    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:

    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 X 10.9 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

    Friday Sep 26, 2014

    Google Chrome 35 Certified with Oracle E-Business Suite 12.1 & 12.2

    Google Chrome logo flatGoogle Chrome 35 is certified for web-based content with Oracle E-Business Suite 12.2.4 and 12.1.3 for Windows desktop clients and Android mobile clients.  See:

    Windows and Android certified

    Chrome 35 is certified for web-based content with Oracle EBS 12.2.4 and 12.1.3 on the following platforms:

    • Windows 7 (32-bit and 64-bit)
    • Android 4.1 and higher

    Java / Forms not supported

    This certification covers web-based (OA Framework / HTML) E-Business Suite product modules only. 

    Google is expected to phase out Chrome's support for Java "before the end of 2014."  Once that occurs, Forms / Java-based EBS product modules and applets will not be compatible with Google Chrome.  

    For details about Chrome's upcoming inability to run Java, see:

    You can contact Google directly if you have questions about their plans for Google Chrome.

    Support implications of Google Chrome's rapid release cycle

    In 2011, Mozilla switched Firefox to a rapid release cycle with a new release coming out every six weeks.  Most enterprises (including Oracle) can't keep up with that deployment rate, so we switched our E-Business Suite + Firefox certification track to Mozilla's Extended Support Release (ESR) channel. Mozilla's ESR releases come out every 12 months.

    Chrome is also released on a rapid release cycle.  Chrome updates average out to a new release every six to eight weeks. Google does not offer an equivalent of Mozilla's annually-updated ESR option for Chrome. 

    Oracle is unable to test every new version of Chrome with every EBS release every eight weeks. We expected that we will certify selected Chrome releases on an ongoing basis.

    We are also unable to test Chrome on all Android versions on all Android devices.  We primarily test Chrome on Samsung and Nexus devices running Android 4.1 and higher.

    If you report an issue with a later version of Chrome that we have not documented, you may be advised to:

    • Use IE or Firefox as a backup browser (Windows clients)
    • Wait for the next version of Chrome (Android clients)
    • Consult with your device vendor (e.g. for issues that cannot be reproduced on Samsung or Nexus devices)

    Pending certifications 

    Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates.  Customers can monitor or subscribe to this blog.  Updates will be posted as soon as soon as they're available. 

    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.


    About

    Search

    Categories
    Archives
    « August 2015
    SunMonTueWedThuFriSat
          
    1
    2
    3
    6
    8
    9
    10
    12
    13
    14
    15
    16
    17
    18
    19
    20
    22
    23
    25
    26
    27
    28
    29
    30
    31
         
    Today