Thursday Feb 11, 2016

ETCC Tool Enhanced for Finding Mandatory EBS 12.2 Patches

Contributing author: Paul Holman

The E-Business Suite Technology Codelevel Checker (ETCC) tool has been provided to help you identify missing database or middle tier patches that may need to be applied to your E-Business Suite Release 12.2 system.

The utility has now been significantly enhanced to map bug fixes to patches, generating a Patch Recommendation Summary that lists the patches (including versions and associated filenames) that are required for your system.

The following example shows part of an ETCC run, where the DB-ETCC script is used to identify missing database patches.

DB-ETCC Example

Why Does This Matter?

As the last section of the above example shows, there is a difference between bug fixes and patches. A bug fix ID for an issue does not change, but the patch ID that delivers the fix might: for example, the original patch could be superseded by another patch. So you need to not only know what bug fix you require, but which patch currently delivers it.

With previous versions of ETCC, the relevant patches (including Patch Set Updates and Exadata patches) had to be identified manually, by referring to the relevant documentation.  In this latest version, bug fix to patch mapping is done for you, avoiding the need for manual identification and the risk of misidentifying the patch needed. That is the principal enhancement in this version of ETCC.

Coverage

This new version of ETCC maps missing bug fixes to corresponding patches for the latest and latest but one quarterly bundles supported by EBS 12.2. You can use this version of ETCC with older bundles, but it will only list missing bug fixes (as previous versions did), and you will see a message saying "Patch mapping not available".

Obtaining ETCC

The ETCC utility can be downloaded via Patch 17537119 from My Oracle Support.

References

Related Articles


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

Friday Jan 22, 2016

Configuring Oracle XML Gateway for TLS

Oracle XML Gateway uses Oracle Transport Agent (OTA) - a lightweight messaging platform to transmit XML-based business transaction messages over HTTP and Secure HTTP (HTTPS) with trading partners. In general, it supports Server and Mutual Authentication mechanisms for inbound and outbound transactions over HTTPS.  Oracle XML Gateway now supports SHA-2 signed certificates and TLS protocol for XML-based transactions in Oracle E-Business Suite 12.1 and 12.2.

Diagram showing message flow protocols

Oracle E-Business Suite Release 12.2

For information on configuring Oracle XML Gateway for SSL/TLS in Oracle E-Business Suite Release 12.2, see:

Outbound transactions in Oracle E-Business Suite Release 12.2.3 and 12.2.4 require a patch; see the documentation for details.

Outbound transactions in Oracle E-Business Suite Release 12.2.5 and later EBS 12.2 updates do not require any additional patches.

Oracle E-Business Suite Release 12.1

For information on configuring Oracle XML Gateway for SSL/TLS in Oracle E-Business Suite Release 12.1.3, see:

References

Related Articles

Thursday Jan 21, 2016

January 2016 Updates to AD and TXK for EBS 12.2

We have been fine-tuning the administration tools for E-Business Suite 12.2 via a series of regular updates to the Applications DBA (AD) and EBS Technology Stack (TXK) components:

We have now made available an eighth set of critical updates to AD and TXK. If you are on Oracle E-Business Suite Release 12.2, we strongly recommend that you apply both of these two newly-released patch collections at your earliest convenience:

They can be downloaded from My Oracle Support, as shown by this example for AD:

Refer to the following My Oracle Support knowledge document for full installation instructions and associated tasks:

Why should I apply these updates?

These updates provide the latest codelevels for AD-TXK. A codelevel is a collection of patches that implements and provides fixes for a set of features associated with a point release of an EBS product. Codelevels are cumulative, with each subsequent one including the features and fixes in each of its predecessors.

There are several important reasons you should adopt this latest AD-TXK codelevel:

  • It includes a number of significant fixes and improvements.
  • New patches to implement code fixes can only be applied to the latest AD-TXK codelevel.
  • No new code fixes are created for earlier AD-TXK codelevels.
Note that it is essential to keep your AD and TXK codelevels synchronized: that is, you must apply both AD.C.Delta.7 and TXK.C.Delta.7, rather than just one of them.

What's New in this Patchset?

  • Support for database password case sensitivity added to the XDF utilities
  • Application short name length increase to 9 characters in ADSPLICE
  • New ADOP Apply failure validations added to the ADOP phases: Prepare, FS_CLONE, Cleanup and Finalize
  • New validation to the Finalize phase to detect FCET execution failures when column changes are introduced by a patch
  • Improvements to ADOP FS_CLONE restartability
  • New algorithm to identify and preserve non-editioned schema connections during the ADOP Cutover phase execution
  • Rapid clone pairs file support for Windows 64-bit

For a more-detailed list, see Section 6 in:

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 Jan 19, 2016

Critical Patch Update for January 2016 Now Available

The  Critical Patch Update (CPU) for January 2016 was released on January 19, 2016.  Oracle strongly recommends applying the patches as soon as possible.

The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

The Critical Patch Update Advisory is available at the following location:

The next four Critical Patch Update release dates are:

  • April 19, 2016
  • July 19, 2016
  • October 18, 2016
  • January 17, 2017
E-Business Suite Releases 11i and 12 Reference

Thursday Jan 14, 2016

Oracle Traffic Director Certified with EBS 12.2 on Exalogic

I'm pleased to announce that Oracle Traffic Director 11gR1 (11.1.1.9) is now certified with Oracle E-Business Suite 12.2 on Oracle Exalogic.

Oracle Traffic Director with Oracle E-Business Suite 12.2 on Exalogic may be configured as follows:
  • as a reverse proxy and load balancer
  • as a TLS accelerator and termination point
  • in DMZ configurations

You may also optionally utilize Oracle Traffic Director features such as content caching and HTTP compression.

For more information regarding Oracle Traffic Director, see:

Deploying and Configuring OTD with EBS 12.2 on Exalogic

For detailed installation and configuration instructions, see:

Related Articles

References

Friday Dec 18, 2015

Platform Migration Certified for EBS 12.2 Application Tiers

We are pleased to announce that application tier migration for Oracle E-Business Suite Release 12.2 is now certified. You can now migrate an existing EBS 12.2 application (middle) tier server to any other Unix/Linux platform certified for EBS 12.2.  These platform migrations preserve patch levels, configurations, customizations, etc.

The E-Business Suite 12.2 application tier migration process requires EBS Release 12.2.3 or later updates to the 12.2 codeline. This documented process outlines only the process for an application tier migration:

What about application tier servers on the same platform?

For application tier migrations between systems of the same platform, you should follow the Rapid Clone process documented in this Note:

What about database tier platform migrations?

Database tier migration should be considered separately. For migration of the database tier, refer to the 'Database Migrations and Upgrades' section in this Note:

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

Monday Dec 14, 2015

Microsoft Office 2016 Certified with E-Business Suite 12.2

We are pleased to announce that Microsoft Office 2013  logoMicrosoft Office 2016 is certified with Oracle E-Business Suite Release 12.2.  For details, see:

This certification covers Office running in 32-bit and 64-bit mode.

Microsoft Office 2016 desktop version is certified for integration with Oracle E-Business Suite Releases 12.1.3 for the following desktop client operating systems:

  • Windows 7 32-bit & 64-bit
  • Windows 8.1 32-bit & 64-bit
  • Windows 10 32-bit & 64-bit
How does the E-Business Suite work with Microsoft Office?

The Oracle E-Business Suite is comprised of several product families such as Financials, Supply Chain Management, Human Resources, and so on.  These product families group together collections of individual products.  Some of these products may be optionally integrated with one or more Microsoft Office components such as Excel, Word, and Projects.

Individual E-Business Suite product teams have the option of building integrations between their products and one or more Microsoft Office components.  This is not mandatory.  Over forty E-Business Suite teams offer these kinds of Office integrations today.

Examples of these integrations include:

  • HRMS Payroll integrations with Microsoft Excel
  • Supply Chain Management Contracts Core integration with Microsoft Word
  • Financials General Ledger (GL) integration with Microsoft Excel
  • Customer Relationship Management (CRM) Proposals integration with Microsoft Word
  • Web Application Desktop Integrator (Web ADI)
  • Desktop Integration Framework
Which Office versions are certified?

We explicitly tested the Office 2016 Professional edition with Oracle E-Business Suite.  We expect that the results of these certification tests apply equally to other desktop-installed editions.

Support implications: We will attempt to reproduce issues reported on other editions on our reference edition -- Office 2016 Professional.  Issues that cannot be reproduced will be handled on a case-by-case basis.  For example, issues that can only be reproduced on, say, Office Home & Student 2016 but cannot be reproduced on Office Professional 2016 will be handled on a case-by-case basis. 

What about OpenOffice, StarOffice, LibreOffice?

We have no plans to certify the E-Business Suite with versions of OpenOffice, StarOffice, LibreOffice, or other equivalents.  

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 Dec 11, 2015

Oracle Unified Directory 11.1.2.3 Certified with EBS 12.2

Oracle Unified Directory 11gR2 Patchset 3 (11.1.2.3) is now certified with E-Business Suite 12.2.  Oracle Unified Directory can be used when enabling single sign-on capabilities for the E-Business Suite via Oracle Access Manager 11gR2.

This certification also includes Directory Integration Platform 11gR1 Patchset 7 (11.1.1.9), which is used to synchronize users between OUD and the E-Business Suite.  

See:

How does this relate to Oracle Internet Directory?

EBS 12.2 users now have the option of using either Oracle Internet Directory or Oracle Unified Directory when enabling single sign-on in their environments. 

Which one should I use?

From the perspective on an E-Business Suite end-user, both directories offer the same functionality, namely, end-users can log on to the E-Business Suite.  The choice really depends upon your user directory administrators.  You should use the one that meets your user administration requirements the best.

Here are the options.  If you're:

  • Running EBS 12.1, you can only use Oracle Internet Directory
  • Running EBS 12.2: you can use Oracle Internet Directory or Oracle Unified Directory

Do I need to switch from OID to OUD?

No.  You can continue to use Oracle Internet Directory with EBS 12.1 and 12.2.  There is no need to switch from Oracle Internet Directory to Oracle Unified Directory.

Can I eliminate both OID and OUD?

No.  When integrating E-Business Suite with Oracle Access Manager, EBS has hardcoded dependencies that require either OID or OUD.  You must have one of these two directories.

This article discusses OID but applies equally to OUD now.  The same technical dependencies exist for Oracle Unified Directory and Oracle Internet Directory when integrating the E-Business Suite with Oracle Access Manager. 

Certified Platforms

Oracle Unified Directory is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. For information on operating systems supported by Oracle WebLogic Server 11g and Oracle Unified Directory, refer to the 'Oracle Fusion Middleware on WebLogic Server - System Certification' in the Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Certification Matrix.

Integration with Oracle Unified 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. 

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

Tuesday Dec 08, 2015

Updated: EBS Upgrade Performance Diagnostics White Paper

We've updated our white paper that describes methods and tools for diagnosing performance-related issues with your EBS 12.x upgrades:

This is a companion Note to:

Both Notes are written by by Jim Machin, a senior member of our Applications Performance group. The companion Note describes a framework and tools for obtaining:

  • Actual statistics: So that you can see exactly which execution plan steps are inefficient, rather than those that you think might be inefficient. You can also estimate the likely impact of a performance fix.
  • Diagnostics that are quick and easy to run, so that you can obtain diagnostics on more jobs/SQL, and obtain them faster.
  • Diagnostics that have very little impact on the performance of the Release 12 upgrade: if they can be run during the upgrade, you will get the diagnostics sooner and be able to resolve the issue more quickly.

There is an extensive range of diagnostics available, which include:

  • Identifying the top SQL in cursor cache or AWR
  • Displaying cursor reports for long-running SQL
  • Matching long-running SQL to jobs
  • Reporting on CBO statistics for all EBS tables
  • Reviewing the AD job timing report
  • Identifying long-running upgrade jobs
  • Specific diagnostics for Online Patching enablement performance

This white paper is updated regularly with new tips and recommendations based upon our Application Performance group's work with actual EBS 12.2 customers and their Service Requests.  All EBS 12.2 sysadmins should monitor this white paper regularly.

Related Articles

Monday Dec 07, 2015

Updated: Minimizing EBS 12.2 Upgrade Downtimes White Paper

We have updated our recommendations for minimizing downtimes when upgrading to EBS 12.2:

Written by Jim Machin, a senior member of our Applications Performance group, this white paper contains a wealth of detailed technical recommendations for reducing the amount of time needed for an EBS 12.2 upgrade. 

Events vs. sessions bottlenecks diagram

It covers:

  • Technical preparation and planning activities
  • Diagnostics for monitoring and troubleshooting performance issues
  • Common solutions to performance issues
  • Oracle Applications Tablespace Model (OATM) considerations
  • Methods for purging old data
  • Gathering statistics
  • Detailed recommendations for improving resource management, sizing, and workloads

This white paper is updated regularly with new tips and recommendations based upon our Application Performance group's work with actual EBS 12.2 customers and their Service Requests.  All EBS 12.2 sysadmins should monitor this white paper regularly.

Related Articles

Wednesday Nov 25, 2015

WebCenter Portal 11.1.1.9 Certified with E-Business Suite 12.2

Oracle WebCenter Suite is an integrated suite of Fusion Middleware 11gR1 tools used to create web sites and portals using service-oriented architecture (SOA).  Applications adapters are also available.

WebCenter Development Framework

WebCenter Portal 11.1.1.9 is now certified with Oracle E-Business Suite Release 12.2.  WebCenter Portal 11.1.1.9 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.9.0, also known as FMW 11gR1 Patchset 8. 

Certified Platforms

Oracle WebCenter Portal is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. For information on operating systems supported by Oracle WebLogic Server 11g and Oracle WebCenter Portal, refer to the 'Oracle Fusion Middleware on WebLogic Server - System Certification' in the Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Certification Matrix.

Integration with Oracle WebCenter Portal 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.

Migrating to Oracle WebCenter

If you're currently using Oracle Portal, you should be aware that Portal is now in maintenance mode.  Updates with bug fixes will continue to be produced, but you should consider migrating to Oracle WebCenter for ongoing new features.

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

Thursday Nov 19, 2015

BPEL 12.1.3 Certified for Prebuilt EBS 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.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 12c version 12.1.3 (in Oracle Fusion Middleware SOA Suite 12c) for Oracle E-Business Suite Release 12.2.

References

Certified Platforms

Oracle SOA Suite Release 12c Version 12.1.3 is certified to run on any operating system upon which Oracle WebLogic Server 12c 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

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.

Tuesday Nov 17, 2015

Rapid Install StartCD 50 for EBS 12.2 Now Available

We are pleased to announce the availability of the latest Oracle E-Business Suite startCD 50 (12.2.0.50). As the fundamental installation medium for EBS, the startCD is what you begin with when installing or upgrading to Release 12.2.

This latest version includes many important fixes and updates; see the README of the startCD patch. The new startCD is highly recommended for all customers who will use Rapid Install to perform an installation or upgrade to Release 12.2.

How to Obtain startCD 12.2.0.50

  • You can download the startCD as Patch 21055525.

Using Rapid Install

Full instructions for Rapid Install can be found here:

  • Oracle E-Business Suite Installation Guide: Using Rapid Install  (PDF, HTML)

What's New in this Update?

This new startCD version 12.2.0.50 includes:

  • Important fixes for fresh install and upgrade scenarios.
  • Introduces Fusion Middleware Web Tier utilities 11.1.1.7.0
  • Installs additional technology stack patches for Oracle Database 11g and Fusion Middleware.

A new stage area for startCD 12.2.0.50 is mandatory

You must create a new stage area to use startCD 12.2.0.50. This startCD version requires a later patch set of the Oracle Fusion Middleware Web Tier Utilities (11.1.1.7.0) than the patch set used by earlier startCD versions.  Earlier startCD versions used Web Tier Utilities 11.1.1.6.0.

You cannot use an existing stage area created with an earlier startCD version. You must create a new stage area to install the currently required Oracle Fusion Middleware Web Tier Utilities patch set (11.1.1.7.0).

How to get Web Tier Utilities 11.1.1.7

You can obtain the Oracle Web Tier Utilities 11.1.1.7.0 in the Oracle Software Delivery Cloud as part of the 12.2.5 media:

  • Go to the Oracle Software Delivery Cloud, search for Oracle Financials for your platform
  • Under 12.2.5, download the ZIP file "Oracle Web Tier Utilities 11.1.1.7.0"


To recreate the stage with the new component you have to:

  1. Download Oracle Web Tier Utilities 11.1.1.7.0
    • Place the ZIP file for the new component in the directory where all the EBS ZIP files reside. (You can reuse the ZIPs for the original 12.2.0 media (excluding Web Tier Utilities 11.1.1.6.0). If you don't have it, you will need to download it again)
  2. Rename or delete the old stage
  3. Run buildStage.sh to create the stage onto a new directory location (i.e. Stage12.2-50)

Please refer to 'Oracle E-Business Suite Installation Guide: Using Rapid Install (Part No. E22950)' guide for more information about creating stage area and other prerequisites.

References

Refer to the following My Oracle Support knowledge documents:

Related Articles


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

Monday Nov 02, 2015

DB 12.1.0.2 Certified with EBS 12.2 on Windows x64 (64-bit)

As a follow up to a prior announcement, Oracle Database 12c Release 1 (12.1.0.2) is now certified with Oracle E-Business Suite Release 12.2 (12.2.3 and higher) on Microsoft Windows Server 2008 R2 and 2012 R2 (Windows x64).

This announcement includes:

  • Oracle Database 12cR1 Version 12.1.0.2
  • Oracle Database In-Memory 12cR1 Version 12.1.0.2
  • Oracle Database 12cR1 Version 12.1.0.2 Real Application Clusters (RAC)
  • TDE Column Encryption with Oracle Database 12cR1 Version 12.1.0.2
  • TDE Tablespace Encryption with Oracle Database 12cR1 Version 12.1.0.2
  • Advanced Security Option (ASO)/Advanced Networking Option with Oracle Database 12cR1 Version 12.1.0.2 (ANO)
  • Export/Import and Transportable Database Data Migration Processes with Oracle Database 12cR1 Version 12.1.0.2


The following are not yet certified and will be announced at a later date once completed:

  • Oracle Multitenant 12cR1 Version 12.1.0.2
  • Oracle Database Vault 12cR1 Version 12.1.0.2
  • Transportable Tablespaces Data Migration Process

Please review the documents below for all requirements and additional details:

Please refer to the platform specific Oracle Database Installation Guides for operating system and other prerequisites.
Please refer to Oracle Database 12c Release 1 (12.1.0.2) New Features Guide 12c Release 1 (12.1) and Oracle Database Administrator's Guide for more information regarding the "In-Memory Column Store" feature.

Wednesday Oct 28, 2015

Oracle WebTier Utilities 11.1.1.9 Now Certified with EBS 12.2

The Oracle E-Business Suite Release 12.2's Rapid Install delivers three Fusion Middleware (FMW) components:
  1. Oracle WebLogic Server 10.3.6 (this is the "$FMW_HOME") 
  2. Oracle WebTier Utilities 11.1.1.6
  3. Oracle Common Home (Part of Oracle WebTier Utilities 11.1.1.6)

EBS 12.2 technology stack architecture diagram

The Oracle WebTier Utilities and the Oracle Common Home should be upgraded by EBS sysadmins to get the latest updates for security, performance, and stability.

Oracle strongly recommends that you keep these components current for the latest performance and security updates.  This latest update will enable Java Secure Socket Extensions (JSSE) automatically for EBS 12.2 environments.  You can download it here: 

For instructions on how to apply this update to your EBS 12.2 environment, see:

Related Articles

Monday Oct 26, 2015

Oracle Data Guard 11.2.0.4 with RAC Certified with EBS 12.2

I'm pleased to announce an update to the certification of Oracle Data Guard 11.2.0.4 with Oracle E-Business Suite 12.2. This certification now includes databases deployed with Real Application Clusters (RAC).  

Certification with Oracle Data Guard 11.2.0.4 provides you the ability to create a Physical Standby Database for Oracle E-Business Suite 12.2 environments.  The creation of a Physical Standby Database is a key component of creating a disaster recovery site for Oracle E-Business Suite.

Detailed steps for setting up a 11.2.0.4 Physical Standby Database for Oracle E-Business Suite 12.2 are provided in the following My Oracle Support Note:

Oracle E-Business Suite Data Guard Certifications

The following matrix provides an overview of what's currently certified and what's planned for Oracle E-Business Suite 12.2 and 12.1.3 and Oracle Data Guard 11.2.0.4 and 12.1.0.2:


Oracle Data Guard 11.2.0.4 Oracle Data Guard 12.1.0.2
Oracle E-Business Suite 12.2 Certified, MOS Note 1491855.1 Certified*, MOS Note 1963472.1
Oracle E-Business Suite 12.1.3 Certified, MOS Note 1070033.1 Certified*, MOS Note 1900663.1

*For single node databases only.  Certification with RAC configurations is pending.

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

How to Find the Latest Certification Information

This blog is great for announcing certifications as they happen, but for ongoing updates and the latest information on certifications, your single source of truth is the Certifications tab in My Oracle Support.  From the Certifications tab on My Oracle Support, you can search for certified combinations of products with specific Oracle E-Business Suite versions.  For example:

Step 1.  Log in to My Oracle Support

Step 2. Click on the Certifications tab

Step 3.  Add your search criteria.  For example:  Add Oracle E-Business Suite to the Product List, add Release 12.2.4 to the Release List and optionally add your platform to the Platform List.

Step 4.Click Check certifications with another product

Step 5.  Add Data Guard to the Product List and optionally add the version to the Release List

The above search will list all versions of data guard currently certified as shown in the following screenshot:


References

Friday Oct 23, 2015

EBS Release 12.2 Certified with Linux Containers (LXC)

Oracle E-Business Suite Release 12.2 is now certified with Linux Containers (LXC) on Oracle Linux 6 (64-bit) and Oracle Linux 7 (64-bit).

Linux Containers is a lightweight virtualization solution that enables running multiple Linux instances that are isolated from each other on the same host. These LXC instances have processes that have their own private view of the OS with its own process id (PID) space, file system structure and network interfaces. LXC allows the use of container OS versions that are different from that of the host - for example, one can run Oracle Linux 5, 6 or 7 Containers in an Oracle Linux 6.6 host.

For information on features, installing and configuring Linux Containers on Oracle Linux, please refer to Chapter 9: Linux Containers in the Oracle Linux Administrator's Solutions Guide for Release 6 or Chapter 27: Linux Containers in the Oracle Linux Administrator's Guide for Release 7.

This certification of EBS 12.2's application tier with LXC requires the use of UEK R3 (QU6) or higher. There are a number of other specific requirements for both the host OS and LXC instances - these are documented in the newly added 'Linux Containers (LXC)' section of the EBS 12.2 Installation and Upgrade Notes (MOS Document 1330701.1).

More information on this technology certification can be found in the following:

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. 


About

Search

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