Monday Feb 08, 2016

JRE 1.8.0_73/74 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_73 (a.k.a. JRE 8u73-b2) and JRE 1.8.0_74 (8u74-b2) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows desktop clients.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

What's new in this release?

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

  • CPU Release:  JRE 1.8.0_73
  • PSU Release:  JRE 1.8.0_74

Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_73) and only upgrade to the PSU release (1.8.0_74) if they require a specific bug fix.  For further information and bug fix details see Java CPU and PSU Releases Explained.

Internet Explorer users are advised to upgrade to the JRE 1.8.0_74 rather than JRE 1.8.0_73 due to a known performance issue.

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

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.

Known Iusses

Internet Explorer Performance Issue

Launching JRE 1.8.0_73 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_74.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue

Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles

JRE 1.7.0_97 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_97 (a.k.a. JRE 7u97-b2) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 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 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?

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:

Known Issues

When using Internet Explorer, JRE 1.7.0_01 had a delay of around 20 seconds before the applet started to load. This issue is fixed in JRE 1.7.0_95.

References

Related Articles

JRE 1.6.0_113 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_113 (a.k.a. JRE 6u113-b1) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 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

Wednesday Jan 20, 2016

JRE 1.8.0_71/72 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_71 (a.k.a. JRE 8u71-b15) and JRE 1.8.0_72 (8u66-b15) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows desktop clients.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

What's new in this release?

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

  • CPU Release:  JRE 1.8.0_71
  • PSU Release:  JRE 1.8.0_72

Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_71) and only upgrade to the PSU release (1.8.0_72) if they require a specific bug fix.  For further information and bug fix details see Java CPU and PSU Releases Explained.

Internet Explorer users are advised to upgrade to the JRE 1.8.0_72 rather than JRE 1.8.0_71 due to a known performance issue.

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

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.

Known Iusses

Internet Explorer Performance Issue

Launching JRE 1.8.0_71 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_72.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue

Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles

JRE 1.7.0_95 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_95 (a.k.a. JRE 7u95-b14) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 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 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?

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:

Known Issues

When using Internet Explorer, JRE 1.7.0_01 had a delay of around 20 seconds before the applet started to load. This issue is fixed in JRE 1.7.0_95.

References

Related Articles

JRE 1.6.0_111 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_111 (a.k.a. JRE 6u111-b12) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 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

Tuesday Dec 15, 2015

Reminder: Error Correction Support Ended for Database 11.2.0.3

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ended for the 11.2.0.3 Database patchset on August 27, 2015

All EBS customers should upgrade to a later patchset or database release.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles

Thursday Dec 10, 2015

Configuring Oracle Workflow with Cloud E-Mail Servers

It is now possible to configure Oracle Workflow Notification Mailer with any cloud-based email server that supports SSL/TLS protocols.  This includes cloud-based email servers such as Microsoft Office 365 and GMail. You can configure cloud-based SMTP and IMAP email servers to handle inbound and outbound Workflow mailer processing. 

Patches are available for E-Business Suite Release 12.1.3 and 12.2.  For complete details, see:

Workflow Office 365 Gmail setup table

The notification mailer configuration wizard within Oracle Applications Manager currently does not support these new security protocol parameters, so you must perform the required configuration steps manually. You should configure outbound processing for your notification mailer first, and then configure inbound processing.

After you configure a notification mailer to use a cloud e-mail server, you must no longer use the notification mailer configuration wizard for that mailer. Instead, continue using the manual configuration scripts to update the mailer configuration as needed.

Related Articles

Monday Nov 30, 2015

Database 11.2.0.4 Certified with HP-UX and EBS 12.1.3

HP logoAs a follow up to the prior announcements on November 20th 2013, Oracle Database 11g Release 2 (11.2.0.4) is now certified with Oracle E-Business Suite Release 12.1.1 or later updates to the 12.1 code line on the following additional platform:

  • HP-UX PA-RISC (64-bit) (11.31)
This announcement for Oracle E-Business Suite R12 includes:
  • Oracle Database 11gR2 version 11.2.0.4
  • Oracle Database 11gR2 version 11.2.0.4 Real Application Clusters (RAC)
  • Oracle Database Vault 11gR2 version 11.2.0.4
  • Transparent Data Encryption (Column Encryption) using Oracle Database 11gR2 version 11.2.0.4
  • TDE Tablespace Encryption using Oracle Database 11gR2 version 11.2.0.4
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 11gR2 version 11.2.0.4
  • Export/Import Process for Oracle E-Business Suite Release 12 Database Instances
  • Transportable

References

Related Articles



Friday Nov 20, 2015

Mobile Approvals 1.3 for EBS Now Available for iOS and Android

Oracle Mobile Approvals for Oracle E-Business Suite lets you respond to pending Workflow approval requests via an app for iOS and Android. It allows you to handle approval requests for expenses, requisitions, purchase orders, recruitment vacancies and offers, timecards, item changes, Supplier Invoices, and more.

Oracle Mobile Approvals for Oracle E-Business Suite is compatible with Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a authorized user of Oracle E-Business Suite, with mobile services configured on the server side by your EBS system administrator. 

What's New in Version 1.3.0

  • Support for enterprise distribution
  • Customization support for corporate branding
  • Mobile application management (MAM) support with Oracle Mobile Security Suite (OMSS), including single sign-on
  • Support for Web SSO authentication to delegate authentication to Oracle Access Manager (OAM)
  • New approval types: Timecards, Item Changes, and Supplier Invoices
  • Enhanced data layout
  • Improved approvals filtering
  • Translations in 10 additional languages including Brazilian Portuguese, Canadian French, Dutch, French, German, Italian, Japanese, Latin American Spanish, Simplified Chinese, and Spanish.

For more information on how to use Mobile Approvals, please refer to the following document:

References

Related Articles

Wednesday Nov 18, 2015

JRE 8u66-b18 Fixes Java Stability Issues with Firefox ESR 38

Java logo[Dec. 14, 2015 update:  An emergency fix for this issue as well as the fix for the IE Forms delay issue is available in Patch 22286087.  Like Patch 22097409 described in the linked article, these patches are only available to users with a current My Oracle Support contract.  If you do not have a My Oracle Support contract, you will have to wait for a future release to be posted on the public Java download site.]

Running Java content with Firefox ESR 38.4.0 using JRE 7 or 8 may cause Firefox to crash. This may affect Oracle E-Business Suite users when running Forms-based EBS screens.  This issue does not affect Internet Explorer users.

JRE 1.8.0_66-b18 is now available.  This release fixes the issue in JRE 8 for all EBS releases affected: 11i, 12.1, and 12.2:

Although Java patches contain both the JRE and JDK releases you only need the JRE version installed on the desktop client to use this fix.

Also affects JRE 7

The same issue is also displayed when running JRE 1.7.0_91 through Internet Explorer. A fix for the JRE 7 family is currently in progress.

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.

References

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 8u66-b33 Fixes JRE 8 Launch Delays with Internet Explorer

Java logo

[Dec. 14, 2015 update:  An emergency fix for this issue as well as the fix for the Firefox ESR 38 issue is available in Patch 22286087.  Like Patch 22097409 described in the article below, these patches are only available to users with a current My Oracle Support contract.  If you do not have a My Oracle Support contract, you will have to wait for a future release to be posted on the public Java download site.]

Running JRE 1.8.0_60 through 1.8.0_66 (pre-build 33) using Internet Explorer causes Update the initial Java applet launch to be delayed by around 20 seconds.  This affects all E-Business Suite users when starting Forms-based EBS screens for the first time.  This issue does not affect Firefox users.

JRE 1.8.0_66-b33 is now available.  This release fixes the issue in JRE 8 for all EBS releases affected: 11i, 12.1, and 12.2:

Although Java patches contain both the JRE and JDK releases you only need the JRE version installed on the desktop client to use this fix.

Also affects JRE 7

The same issue is also displayed when running JRE 1.7.0_91 through Internet Explorer. A fix for the JRE 7 family is currently in progress.

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.

References

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 Nov 12, 2015

Quarterly EBS Upgrade Recommendations: November 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 November 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 RPC4 or 12.2.  Before upgrading, 12.1 users should be on the minimum minimum 12.1 patching baseline.

  4. EBS 12.2 users should upgrade to EBS 12.2.5, Database 11.2.0.4 or 12.1.0.2, the October 2015 AD/TXK tools, StartCD 50, and FMW 11.1.1.9.

  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 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.9 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_105 or later 1.6 updates or JRE 1.7.0_91 or later 1.7 updates or JRE 1.8.0_65 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 October 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).

  17. EBS 12.1 users should switch their PKI certificates to SHA-2.

Related Articles

Tuesday Nov 03, 2015

DSTv25 Timezone Patches Available for E-Business Suite

Hourglass iconIf your E-Business Suite Release environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in June 2015 and released as DSTv24.

DSTv25 is now available and certified with Oracle E-Business Suite Release 12.2 and 12.1. The DSTv25 update includes the timezone information from the IANA tzdata 2015g.  It is cumulative: it includes all previous Oracle DST updates. 

Is Your Apps Environment Affected?

When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

  • Your Oracle E-Business Suite environment is located in the affected country or region OR
  • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

The latest DSTv25 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv25 includes changes to the following timezones since the DSTv24 release:

  • Africa/Casablanca
  • Africa/El_Aaiun
  • America/Montevideo
  • Asia/Pyongyang
  • Europe/Istanbul
  • Pacific/Fiji
  • Turkey
  • Asia/Istanbul

What Patches Are Required?

In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

Proactive backports of DST upgrade patches to all Oracle E-Business Suite tiers and platforms are not created and supplied by default. If you need this DST release and an appropriate patch is not currently available, raise a service request through support providing a business case with your version requirements.

The following Note identifies the various components in your E-Business Suite environment that may need DST patches:

Thursday Oct 22, 2015

Fourth Recommended Patch Collection for EBS 12.1.3 Now Available

We are pleased to announce the availability of the fourth consolidated patch collection for Oracle E-Business Suite Release 12.1.3.  This patchset combines important patches for Release 12.1.3 into a single integrated and regression-tested patchset:


Reasons to Apply RPC4

Oracle E-Business Suite Release 12.1.3 has been available for a while, and over its lifetime has been significantly enhanced in numerous ways. These enhancements and fixes are provided as individual patches, product family Release Update Packs (RUP), and product-specific Recommended Patch Collections (RPC).

For example, there are Recommended Patch Collections for Financials products such as General Ledger and Payables. On the technology side, there are patchsets such as the OA Framework 12.1.3.1 Consolidated Update Patch.

Identifying and applying all the individual patches, RUPs, and RPCs you need can be time-consuming. Complicating matters further, patchsets across multiple product families are generally not tested together.

Patches included in Oracle E-Business Suite Release 12.1.3+ RPC4 are also available individually, and may contain conditions and prerequisites relevant to their application. RPC4 includes all the recommended patches, along with their dependencies. Applying this patch in a single downtime patching window saves effort and time, rather than applying each recommended patch individually.

What's Included in RPC4?

The EBS 12.1.3+ RPC4 patchset includes the latest recommended patches and their dependencies for the following Oracle E-Business Suite products and product families:

  • Applications Technology (ATG)
  • Oracle Customer Relationship Management (CRM)
  • Oracle Financials (FIN)
  • Oracle Human Resource Management System (HRMS)
  • Oracle Procurement (PRC)
  • Oracle Projects (PJ)
  • Oracle Supply Chain Management (SCM)
  • Oracle Value Chain Planning (VCP)
  • Oracle Business Intelligence (BIS)

Is it necessary to apply this RPC if I only use a subset of Oracle E-Business Suite products?

Applying this RPC is recommended, even if you are using only a subset of Oracle E-Business Suite products. The patching utility 'adpatch' takes care of the files to be applied and generates them based on the product installation status.

I have already applied a few Family Packs included in this RPC. What happens when I apply this RPC?

Applying this RPC on top of already applied individual Family Packs will not harm your system because the patching utility 'adpatch' skips the files already applied on the system. You can apply the latest available RPC on your system.

A patch I need isn't included in this RPC. Why not?

This RPC combines recommended patches that were released after Release 12.1.3 into a single, integrated and regression-tested patch to help ensure a successful installation. If you don't find the patch in the RPC, it is likely that the patch was released after the patch list for the specific RPC was frozen or the patch was not marked "recommended" at the time the list was generated.

Should I only install the latest RPC? Do I have to install all prior RPCs? Should I install later individual product family RPCs?

To keep your system up-to-date with the most current Oracle E-Business Suite recommended patches, you should only apply the latest available RPC (which supersedes any prior release suitewide RPC) and thereafter either install individual product-level recommended patches as required or install the next suitewide level RPC when it becomes available.

Related Articles

Wednesday Oct 21, 2015

JRE 1.8.0_65/66 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_65 (a.k.a. JRE 8u65-b17) and JRE 1.8.0_66 (8u66-b17) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 12.1, and 12.2 for Windows desktop clients.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

What's new in this release?

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

  • CPU Release is JRE 1.8.0_65
  • PSU Release is JRE 1.8.0_66
Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_65) and only upgrade to the PSU release (JRE 1.8.0_66) if they require a specific bug fix.  For further information and bug fix details 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 8 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 8 Plug-in.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

IE Performance issue: Launching JRE 1.8.0_65 or 1.8.0_66 through Internet Explorer will have a delay of about 20 seconds befre the applet starts to load. Java Console will come up if enabled. This issue does not affect Firefox, where the applet launches as usual.  A fix for this issue is currently being investigated. Please monitor this blog for updates.

EBS + Discoverer 11g Users

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

Implications of Java 6 and 7 End of Public Updates for EBS Users

The Oracle Java SE Support Roadmap and Oracle Lifetime Support Policy for Oracle Fusion Middleware documents explain the dates and policies governing Oracle's Java Support.  The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology in these documents.

Starting with Java 7, Extended Support is not available for Java SE Deployment Technology.  It is more important than ever for you to stay current with new JRE versions.

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

  • You can continue to do so until the end of Java SE 6 Deployment Technology Extended Support in June 2017
  • You can obtain JRE 6 updates from My Oracle Support.  See:

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

  • You can continue to do so until the end of Java SE 7 Deployment Technology Premier Support in July 2016
  • You can obtain JRE 7 updates from My Oracle Support.  See:

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

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_91 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_91 (a.k.a. JRE 7u91-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_105 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_105 (a.k.a. JRE 6u105-b15) 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

Tuesday Oct 20, 2015

SHA-2 Signed PKI Certificates Certified with EBS 12.1.3

I'm pleased to announce that SHA-2 signed PKI certificates are now certified for inbound connections to the Oracle HTTP Server (OHS) delivered with Oracle E-Business Suite 12.1.3.

As published in a prior blog article, SHA-2 signed PKI certificates are already certified for outbound connections from Oracle E-Business Suite 12.1.3.

Required Steps

If you are enabling SSL/TLS for the first time for Oracle E-Business Suite 12.1.3, refer to the following for all prerequisite requirements and post steps:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 3 (Note 376700.1)

If you have already enabled SSL or TLS and are updating to a SHA-2 signed PKI certificate with the OHS for Oracle E-Business Suite 12.1.3, refer to the following for all prerequisite requirements and post steps:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 11 (Note 376700.1)

Overview of the Requirements

The following is a summary of the requirements for deploying a SHA-2 signed PKI certificate for inbound connections to the OHS for Oracle E-Business Suite 12.1.3 include the following:

  • Update OPatch

If you have not already updated to the OPatch 9i, 10.1 version 1.0.0.0.63 or later, download and install it. For the latest OPatch information, refer to the following:

OPatch for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4), (Note 283367.1)
  • Apply the minimum required patch level for the Oracle Fusion Middleware 10.1.3 Oracle Home

The minimum requirement is to upgrade the Oracle Fusion Middleware 10.1.3 Oracle Home to 10.1.3.5 per the following:

Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12 (Note 454811.1)

  • Apply the October 2015 CPU to the Oracle Fusion Middleware 10.1.3 Oracle Home

The minimum CPU requirement for the Oracle Fusion Middleware 10.1.3.5 is the October 2015 CPU level (Patch 21845960) per the following:

Oracle E-Business Suite Releases 11i and 12 Critical Patch Update Knowledge Document (October 2015) (Note 2051000.1)

Note: Testing is performed with all CPU patches applied across the technology stack components and the Oracle E-Business Suite. It is possible to apply the October 2015 CPU (Patch 21845960) to FMW 10g without applying the Oracle E-Business Suite October 2015 CPU or Oracle Database October 2015 CPU/PSU; however, we recommend that customers apply the latest CPU across all technology stack components and the Oracle E-Business Suite.

  • Perform all necessary post steps.

Post steps include generating the CSR to obtain the SHA-2 signed PKI certificate from your certificate authority (CA). Once you have the certificate, you will import it using Oracle Wallet.

Refer to the appropriate section in the following My Oracle Support note for the complete list of post-steps for your environment:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 11 (Note 376700.1)

Pending Platform Certifications

For AIX, HP Itanium and Windows, there will be an additional patch required on top of the FMW 10g Oracle Home October 2015 CPU. The required patch is currently in development.

Oracle's revenue recognition policy prohibits us from providing time lines and dates for future certifications and releases. Please monitor this blog for the latest in certification announcements.

Related Articles

References

Monday Oct 19, 2015

Should EBS Customers Use Database 12.1.0.2 or 12.1.01?

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. a level where you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 12.1.0.1 Database patchset on August 31, 2016.  All EBS customers should upgrade to a later patchset or database release before then.

Even though Database 12.1.0.1 is still under Error Correction Support, we recommend that all EBS customers currently running Database 12c 12.1.0.1 upgrade to the Database 12.1.0.2 patch set.

Why upgrade?

Better end-user experience.  Database 12.1.0.2 contains important updates for security, stability, and performance.  These updates improve the experience of your end-users.

Easier for system administrators.  We have been working closely with many EBS 12.2 customers.  We have found that the Database 12.1.0.2 patch set streamlines upgrades to EBS 12.2 by reducing the number of additional interoperability patches are required.  Fewer patches mean that upgrades take less time, are less-complex, and less risky.

Minimum baseline for future EBS+Database 12c Certifications.  It is very complex to keep multiple EBS codelines compatible with multiple database releases.  All future EBS 12.2 patches will certified against Database 12.1.0.2 rather than Database 12.1.0.1.  This includes updates to the core AD and TXK system administration tools. 

Faster resolution for database issues. You can still request patches for Database 12.1.0.1 until August 31, 2016, but they will not be produced proactively, so there might be a delay in getting them to you.

Related Articles

Friday Oct 09, 2015

BPEL 11.1.1.9 Certified for Prebuilt EBS 12.1 and 12.2 SOA Integrations

Service Oriented Architecture (SOA) integrations with Oracle E-Business Suite can either be custom integrations that you build yourself or prebuilt integrations from Oracle.  For more information about the differences between the two options for SOA integrations, see this previously-published certification announcement.

The prebuilt BPEL business processes in Oracle E-Business Suite Release 12.1 are:

  • Oracle Price Protection (DPP)
  • Advanced Supply Chain Planning (MSC)
  • Oracle Transportation Management: Oracle Warehouse Management (WMS)
  • Oracle Transportation Management: Oracle Shipping Execution (WSH)
  • Oracle Transportation Management: Oracle Purchasing (PO)

The prebuilt BPEL business processes in Oracle E-Business Suite Release 12.2 are:

  • Oracle Price Protection (DPP)
  • Advanced Supply Chain Planning (MSC)
  • Oracle Transportation Management: Oracle Warehouse Management (WMS)
  • Oracle Transportation Management: Oracle Shipping Execution (WSH)
  • Oracle Transportation Management: Oracle Purchasing (PO)
  • Complex Maintenance, Repair & Overhaul (CMRO/AHL)

BPEL integration architecture diagram example

These prebuilt BPEL processes have now been certified with Oracle BPEL Process Manager 11g version 11.1.1.9 (in Oracle Fusion Middleware SOA Suite 11g) for Oracle E-Business Suite Release 12.1.3 and 12.2.

References

Certified Platforms

    Oracle SOA Suite Release 11g R1 Version 11.1.1.9 is certified to run on any operating system upon which Oracle WebLogic Server 11g is certified. Check the following for more details:

    For information on operating systems supported by Oracle SOA Suite, refer to this document:

    Integration with Oracle SOA Suite involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

    Getting Support

    If you need support for the prebuilt EBS BPEL business processes, you can log Service Requests against the Applications Technology Group product family.

    Related Articles


    Tuesday Sep 22, 2015

    EBS Support Policy for Third-Party Client Components

    End-users connect to the Oracle E-Business Suite using a variety of clients: desktops, laptops, and mobile devices.  Those clients run third-party operating systems (Microsoft Windows, Mac OS X, Apple iOS, Android) and third-party products (Microsoft Office, Internet Explorer, Mozilla Firefox, Safari, and Chrome).

    What happens when you have client-related issues?  What are our support policies when issues involve third-party components as well as Oracle components?

    EBS components affected by third-party client products

    A number of E-Business Suite components or products are affected by third-party client components.  These include:

    • OA Framework (OAF: the user interface infrastructure that underlies most HTML/web-based self-service EBS products)
    • Oracle CRM Technology Foundation (JTT: the infrastructure that underlies EBS CRM products such as Sales, Marketing, Service, eCommerce, Contracts, and Interaction Center)
    • Oracle Forms (Forms-based EBS products running in Java)
    • Web Application Desktop Integrator (Web ADI: provides integrations with Microsoft Office products such as Excel)
    • Report Manager

    Support options partly depend upon the third-party

    Our support policy for EBS client issues depends upon whether those third-party operating systems and products are supported by the third-party vendor.

    You can search Microsoft, Apple, Mozilla, and Google websites for support timelines for their products.

    How to interpret this information 

    We provide updates to the E-Business Suite when both of the following are true:

    1. The E-Business Suite release is eligible for Error Correction Support
    2. The third-party operating system or product is actively supported by the third-party

    If a reported issue is isolated to the third-party component, Oracle will attempt to issue a fix or find a workaround.  Oracle may not be able to provide fixes for all reported issues.  For example, if a browser vendor changes their browser's behavior or chooses to remove a particular feature, customers may need to contact that vendor directly.  

    It is important to keep track of support dates for third-party products.  We do not provide new EBS patches, certifications, and documentation updates for combinations that involve obsolete third-party products.

    Example 1: Windows version obsoleted by Microsoft
    • It is September 1, 2015
    • You see a listing in the Certifications system for EBS 12.1.3 + IE 6 on Windows XP
    • Error Correction Support for EBS 12.1.3 continues to December 2019
    • Microsoft supports IE 6 as part of its Windows XP policy
    • Microsoft desupported Windows XP in April 2014
    • You cannot request new patches for this combination

    Example 2: Office version obsoleted by Microsoft

    • It is September 1, 2015
    • You see a listing in the Certifications system for EBS 12.1.3 + Microsoft Office 2003
    • Error Correction Support for EBS 12.1.3 continues to December 2019
    • Microsoft desupported Office 2003 in April 2014
    • You cannot request new patches for this combination

    Example 3: Firefox version obsoleted by Mozilla

    • It is September 1, 2015
    • You see a listing in the Certifications system for EBS 12.1.3 + Mozilla Firefox ESR 31
    • Error Correction Support for EBS 12.1.3 continues to December 2019
    • Mozilla desupported ESR 31 in August 2015
    • You cannot request new patches for this combination

    Example 4: Chrome version obsoleted by Google

    • It is September 1, 2015
    • You see a listing in the Certifications system for EBS 12.1.3 + Google Chrome 35
    • Error Correction Support for EBS 12.1.3 continues to December 2019
    • The latest Chrome release available is 45
    • Google only supports the latest Chrome release
    • You cannot request new patches for this combination

    Still confused?

    If you're still having trouble, log a Service Request with Oracle Support.  A Support Engineer can help with these types of questions.

    Related Articles

    Monday Sep 14, 2015

    Database Migration using 12cR1 Transportable Database Certified for EBS 12.1

    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.1 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.1) 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 x64*
     IBM: Linux on System z

    * Microsoft Windows x64 is not yet certified and will be announced 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) or Transportable Tablespaces (TTS).

    References

    Related Articles

    Friday Aug 28, 2015

    "Certified" vs. "Error Correction Support": What's the Difference?

    We've recently gotten a string of questions about the support status of obsolete products listed in the Certifications system on My Oracle Support.  This is really important: everyone working with Oracle products should know how to determine the support status of their products.

    The existence of a listing in the Certifications system doesn't necessarily mean that a product release is covered by Error Correction Support. 

    To determine the support status of a particular combination:

    1. Check if the combination is listed in the Certifications system
    2. Check the support status of the product releases
    3. Check the support status of the product patch sets
    4. Interpret this information
    Let's walk through these steps in more detail.

    Understanding the three phases of support

    We produce new patches and certifications for Oracle products while they are covered by either Premier or Extended Support.  Those two support phases are collectively known as the Error Correction Support period. 

    After that period, products are covered by Sustaining Support.  You can download existing patches and documentation for products in Sustaining Support.  You cannot request new patches or certifications for these products.

    See the Oracle Lifetime Support Policy site for more details about Premier, Extended, and Sustaining Support levels.

    Step 1. Check if the combination is listed in the Certifications system

    The Certifications system on My Oracle Support lists all of the combinations that we've tested for the E-Business Suite. Certifications are generally retained for reference purposes after the Error Correction Support phase has ended for those products. The existence of an historical listing in the Certifications system doesn't necessarily mean that that is still covered by Error Correction Support.

    For example, the Certifications system includes historical listings for:

    • EBS 11.5.3 (Error Correction Support ended July 2006)
    • EBS 12.0.6 (Error Correction Support ended January 2015)
    • Oracle Single Sign-On 10.1.2.0.2 (Error Correction Support ended December 2011)
    • Oracle Database 8.1.7.4 (Error Correction Support ended December 2006)

    You cannot request new patches or certifications for any products after their Error Correction Support ends.

    Step 2: Check the support status of a product release

    A product release is the major version.  For example, Database 11gR2 is the product release.

    Database Lifetime Support dates table

    You should always check the Oracle Lifetime Support documents for a product release's Premier and Support dates to determine whether the release is covered by Error Correction Support. 

    See:

    Step 3: Check the the support status of a product patch set

    Product releases have patch sets. For example: the Database 11gR2 release has 11.2.0.3 and 11.2.0.4 patch sets.

    Individual patch sets have their own Error Correction Support dates. You should always check the following documents for the support status of a given patch set:

    Step 4: Interpret this information 

    You can ask for new patches for a given combination only if all products within that combination are still covered by Error Correction Support. 

    Example 1:

    • It is August 1, 2015.
    • You see a listing in the Certifications system for EBS 12.0.6 + Database 11.2.0.4
    • Error Correction Support for E-Business Suite 12.0.6 ended January 2015
    • Error Correction Support for Database 11.2.0.4 continues to January 2018
    • You cannot request new patches for this combination

    Example 2:

    • It is August 1, 2015
    • You see a listing in the Certifications system for EBS 12.1.3 + Oracle Access Manager 10.1.4.3
    • Error Correction Support for EBS 12.1.3 continues to December 2019
    • Error Correction Support for Oracle Access Manager 10.1.4.3 ended December 2011
    • You cannot request new patches for this combination

    Example 3:

    • It is August 1, 2015
    • You see a listing in the Certifications system for EBS 12.1.3 + Oracle Database 11.2.0.2
    • Error Correction Support for EBS 12.1.3 continues to December 2019
    • Error Correction Support for Database 11.2.0.2 ended October 2013
    • You cannot request new patches for this combination

    Still confused?

    If you're still having trouble, log a Service Request with Oracle Support.  A Support Engineer can help with these types of questions.

    Related Articles

    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 Aug 05, 2015

    Using Oracle Database In-Memory with Oracle E-Business Suite

    Authors: Andy Tremayne and Deepak Bhatnagar, Oracle Development

    Database In-Memory is one of a number of options that can be deployed to address Oracle E-Business Suite performance concerns and scalability requirements without the need for any application changes.

    We are pleased to announce the publication of a new white paper that can help with this (including links to patches that you will need to apply):

    The paper starts by providing strategic advice and guidelines that help you decide which objects to populate into Database In-Memory (DBIM), and how to size the In-Memory Column Store (IMCS). It provides a list of best practices and explains the complexities and limitations of using DISTRIBUTE/DUPLICATE with Oracle RAC.

    Database In-Memory diagram

    The examples in this paper take a step away from the classic headline feature of analytical reports that you might have been expecting. Instead, they show how DBIM can be applied to three novel use cases:

    • The Order Organizer Form has a huge number of queryable fields that would all need to be indexed for optimal performance. DBIM provides a 10X improvement in the end-user response time.
    • The Initialize Credit Summaries concurrent program is unusual the optimization is based on an INSERT statement. It is also interesting as the example shows why simply populating objects into the IMCS can result in a performance reduction – in this case spilling to disk. Simply populating the objects into DBIM improved the time by 1.5X; further tuning improved on this to provide an overall gain of 3.5X.
    • The Receiving Transaction Processor had two long-running queries that reduced from 7.8 hrs to 4.85 mins representing about a 100X increase in performance. The overall runtime was about 4X faster.

    One of the key aspects in the paper is describing how to use Oracle E-Business Suite Application Affinity with Oracle RAC. It describes how to overcome some of the limitations of Non-Engineered Systems (commodity hardware), and explains how it can also be used to benefit Oracle Engineered Systems.

    Other References

    The Oracle Database In-Memory blog contains a wealth of generic information, technical details, ideas and news on Oracle Database In-Memory from the author of the Oracle White Paper on Oracle Database In-Memory.

    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

    Monday Jul 20, 2015

    Oracle Internet Directory 11gR1 11.1.1.9 Certified with E-Business Suite

    I'm pleased to announce that Oracle Internet Directory 11gR1 Patchset 7 (11.1.1.9) is now certified for use in the Oracle Access Manager integration with Oracle E-Business Suite Release 11i (11.5.10.2) and 12 (12.1.3+, 12.2.2+). 

    Oracle E-Business Suite comes with native user authentication and management capabilities out-of-the-box. If you need more-advanced features, it's also possible to integrate it with Oracle Internet Directory and Oracle Single Sign-On or Oracle Access Manager, which allows you to link the E-Business Suite with third-party tools like Microsoft Active Directory and Windows Kerberos. 


    For details about third-party integration architectures, see:

    Supported Configurations

    Oracle Internet Directory 11.1.1.9.0 can be integrated with these single sign-on solutions for EBS environments:

    • Oracle Internet Directory (OID) and Directory Integration Platform (DIP) from Fusion Middleware 11gR1 Patchset 7 (11.1.1.9.0) with Oracle Access Manager 11gR2 (11.1.2.0) with an Oracle E-Business Suite system (Release 11i (11.5.10.2), 12.1.3+ or 12.2.2+).
    • Oracle Internet Directory and Directory Integration Platform from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 11gR1 Patchset 2 (11.1.1.7.0) with an Oracle E-Business Suite system (Release 12.1.3+).
    Platform certifications

    Oracle Internet Directory is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to the Oracle Fusion Middleware 11g System Requirements for more details.

    Integration with Oracle Internet Directory involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

    References

    Related Articles
    About

    Search

    Categories
    Archives
    « February 2016
    SunMonTueWedThuFriSat
     
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
         
           
    Today