Tuesday May 19, 2015

Firefox ESR 38 Certified with EBS 12.2 and 11i

Firefox ESR logo

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

The certification with EBS 12.1 is pending; see below.

What is Mozilla Firefox ESR?

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

What does the Mozilla Firefox ESR life cycle look like?

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

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

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

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

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

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

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

EBS patching policy for Firefox compatibility issues

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

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

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

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

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

References

Pending Certification

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

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

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


The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 


Wednesday Apr 22, 2015

Quarterly EBS Upgrade Recommendations: April 2015 Edition

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

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

You can research these yourself using this Note:

Upgrade Recommendations for April 2015

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Thursday Apr 16, 2015

JRE 1.8.0_45 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

Impact of enabling JRE Auto-Update

Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

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

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

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

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

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

Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

No.

JRE is used for desktop clients.  JDK is used for application tier servers.

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

References

Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 


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

Java logo

Java Runtime Environment 1.7.0_79 (a.k.a. JRE 7u79-b15) and 1.7.0_80 (7u80-b15) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i, 12.1, and 12.2 for Windows-based desktop clients.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

What's new in this release?

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

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

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

There are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it.

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2
EBS + Discoverer 11g Users

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

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

JRE 7 End of Public Updates

This is the last JRE 7 update available to the general public.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 7 updates to the end of Java SE 7 Premier Support to the end of July 2016.

How can EBS customers obtain Java 7 updates after the public end-of-life?

EBS customers can download Java 7 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Both JDK and JRE packages are now contained in a single combined download.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

References

Related Articles

Java JRE 1.6.0_95 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_95 (a.k.a. JRE 6u95-b12) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12.x for Windows-based desktop clients.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

What's new in in this Java release?

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

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

Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package.

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

The latest updates to that page (as of Sept. 19, 2012) state:

Java SE 6 End of Public Updates Notice

After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

What does this mean for Oracle E-Business Suite users?

EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

In other words, nothing changes for EBS users after February 2013. 

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017. 

How can EBS customers obtain Java 6 updates after the public end-of-life?

EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

References

Related Articles

Wednesday Apr 15, 2015

Critical Patch Update for April 2015 Now Available

The  Critical Patch Update (CPU) for April 2015 was released on April 14, 2015.  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:

  • July 14, 2015
  • October 20, 2015
  • January 19, 2016
  • April 19, 2016
E-Business Suite Releases 11i and 12 Reference

Tuesday Apr 14, 2015

EBS OA Extensions for JDeveloper Certified with Windows 8.1

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

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

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

For details, see:

Pending Certifications

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

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

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

Related Articles

Wednesday Mar 04, 2015

JRE 1.8.0_40 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

Impact of enabling JRE Auto-Update

Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

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

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

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

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

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


Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

No.

JRE is used for desktop clients.  JDK is used for application tier servers.

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

References

Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 


Thursday Feb 26, 2015

Reminder: Upgrade Database 12.1.0.1 to 12.1.0.2 by July 2015

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 ends for the 12.1.0.1 Database patchset on July 22, 2015. All EBS customers on Database 12.1.0.1 should upgrade to the Database 12c 12.1.0.2 patchset before then. 

Related Articles

Friday Feb 13, 2015

Reminder: EBS 11i Reverts to Sustaining Support on January 1, 2016

E-Business Suite 11.5.10.2 has been in Sustaining Support since December 1, 2013.  We have offered a one-time Exception to Sustaining Support (covering only Severity 1 issues) until December 31, 2015. 

This means that we will revert to Sustaining Support for Oracle E-Business Suite 11i 11.5.10.2 on January 31, 2016.  See:

Chart displaying EBS Premier and Extended Support dates

EBS 11i users should upgrade to EBS 12.1 or 12.2 as soon as possible. You might find this article useful:

What happens after Extended Support ends?

The Exception to Sustaining Support coverage ends and we revert to the normal mode of Sustaining Support on January 1, 2016.  You can request diagnostic assistance for EBS 11i issues and download existing patches and documentation. Sustaining Support does not include:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For more specifics on Premier Support, Extended Support, and Sustaining Support, see:

Implications for EBS 11i users

You may need to freeze your desktop and server configurations while you upgrade to EBS 12.1 or 12.2. 

New versions of desktop components may not work with EBS 11i. These include new releases of:

  • Windows
  • Mac OS X
  • Internet Explorer (IE)
  • Firefox
  • Safari
  • Office
  • Desktop-based Java Runtime Environment (JRE)  

New versions of server-based components may not work with EBS 11i. 

These include new releases of:

  • Server-based operating systems (Linux, AIX, HP-UX, Solaris, etc.)
  • Oracle Database
  • Java JDK
  • Fusion Middleware components (Oracle HTTP Server, JServ, Forms, etc.)

Related Articles

Friday Feb 06, 2015

Internet Explorer 11 Certified with E-Business Suite 11.5.10.2

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

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

Certified IE 11 Modes

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

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

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

JRE 6, 7, and 8 are certified with EBS

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

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

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

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops. We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

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

"JInitiator version too low" errors

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

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

References

Related Articles


Thursday Feb 05, 2015

Reminder: Upgrade Database 10.2.0.5 Before July 2015

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 ends for the 11.1.0.7 Database patchset on July 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

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

Related Articles


Reminder: Upgrade Database 11.1.0.7 Before August 2015

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 ends for the 11.1.0.7 Database patchset on August 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

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

Related Articles


Reminder: Upgrade Database 11.2.0.3 Before August 2015

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 ends for the 11.2.0.3 Database patchset on August 27, 2015

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

Related Articles


Thursday Jan 22, 2015

Using SHA-2 Signed Certificates with EBS

Secure Hash Algorithms (SHA) are used for a variety of cryptographic purposes including signing of public key infrastructure (PKI) certificates (e.g., code signing cerificates and Secure Socket Layer (SSL) or Transport Layer Security (TLS) server certificates). Currently, the SHA family of functions include SHA-0, SHA-1, SHA-2 and SHA-3. This article and reference notes focus on the use of the SHA256 hash function of SHA-2 with Oracle E-Business Suite.

Why is SHA-2 important to you?

Industry standards for encryption algorithms are constantly under review. Many certificate authorities are recommending or mandating SHA-2 as the minumum signature algorithm for issuing certificates. The time frame for moving to SHA-2 varies depending upon the certificate authority that is used. The requirement for SHA-2 also impacts intermediate certificates which must also be SHA2 in order to chain back to the end-entity SHA-2 certificate issued. Root certificates are not impacted.

When does Oracle E-Business Suite use certificates?

1. HTTPS clients (outbound connections)
HTTPS client connections that originate from Oracle E-Business Suite. For HTTPS clients, you may need to apply product patches to use SHA-2 certificates. Currently, the following products have identified additional requirements to support SHA-2 for HTTPS clients:

  • XML Gateway
    Follow the instructions in the patch README and apply the following patch: 19909850
  • iProcurement
    Follow the instructions for iProcurement in My Oracle Support Note 1937220.1.

In addition to products that initiate outbound connections from java code on the application tier, the Oracle Database may also act as an HTTP client when the UTL_HTTP package is utilized. Some Oracle E-Business Suite products leverage UTL_HTTP for outbound HTTPS connections. You may also use UTL_HTTP for external integrations and customizations.

For the Oracle Database to utilize a PKI (including SHA-2 signed) certificate, SSL/TLS for outgoing connections database connections must be configured.  Our testing in Oracle E-Business Suite development has confirmed that UTL_HTTP is SHA-2 compliant as of Oracle Database 11.1.0.7 (we have not tested with earlier database versions).The steps for enabling and testing SSL/TLS configuration for the Oracle Database are documented in the following:

2. Server Side
In addition to client side (outbound connections), the Oracle E-Business Suite application tier utilizes PKI certificates for code signing by AD Jar Signing and for the (inbound) SSL/TLS termination point using the Oracle HTTP Server.

AD JAR Signing
During patching, Oracle E-Business Suite uses certificates to sign JARs that will be delivered to the browser. As of Java 1.5, Java and its utilities keytool and jarsigner supports SHA-2 certificates. SHA-2 certificates are certified for JAR signing for all versions of Oracle E-Business Suite (11i, 12.0, 12.1 and 12.2) and Java 1.5 and higher.

Oracle HTTP Server (inbound connections)
SHA-2 certificates are also used by the Oracle HTTP server that is delivered with the Oracle E-Business Suite Applications Technology. The requirements for SHA-2 for the Oracle HTTP Server vary per Oracle E-Business Suite version as follows:

  • Oracle E-Business Suite Release 12.2
    SHA-2 certificates are certified with the Oracle HTTP Server delivered with Oracle E-Business Suite 12.2. The wallet management tools that are shipped with EBS 12.2 generate Certificate Signing Requests (CSRs) signed using MD5. The following note has been updated with the steps necessary to create CSRs signed with other algorithms including SHA-2:
  • Oracle E-Business Suite Releases 12.0 and 12.1
    We are currently working on the certification of SHA-2 certificates with the Oracle HTTP Server for Oracle E-Business Suite Release 12.0 and 12.1. As an option while we are working on this certification, you may use an alternate technology (ie, a load balancer, reverse proxy, etc) that supports SHA-2 as the SSL/TLS termination point. Another alternative is to request that your certificate authority issue a SHA-1 certificate.

  • Oracle E-Business Suite Release 11i
    SHA-2 certificates are certified with Oracle E-Business Suite Release 11i when using mod_ssl.so OpenSSL library version 0.98za or later.  To get the minimum mod_ssl.sl library required for EBS 11i and SHA-2, you must apply the July 2014 CPU. Note: We always recommend that you apply the most current CPU available to your environment. You may refer to the following note for additional details:

Related Articles

References

Wednesday Jan 21, 2015

JRE 1.8.0_31 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

Impact of enabling JRE Auto-Update

Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

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

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

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

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

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

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

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

Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

No.

JRE is used for desktop clients.  JDK is used for application tier servers.

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

References

Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 


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

Java logo

Java Runtime Environment 1.7.0_75 (a.k.a. JRE 7u75-b13) and 1.7.0_76 (7u76-b13) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

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

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

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

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

What's new in this release?

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

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

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

There are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it.

JRE 1.7.0_75  (7u75) is a CPU release. If you are running on the JRE 7 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 7 Plug-in.

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2
EBS + Discoverer 11g Users

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

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

JRE 7 End of Public Updates

Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 7 updates to the end of Java SE 7 Extended Support in April 2015.

How can EBS customers obtain Java 7 updates after the public end-of-life?

EBS customers can download Java 7 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Both JDK and JRE packages are now contained in a single combined download.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

 

What do Mac users need?

Mac users running Mac OS X 10.9 can run JRE 7 or 8 plug-ins.  See these articles:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

References

Related Articles

Java JRE 1.6.0_91 Certified with Oracle E-Business Suite

Java logo

The latest Java Runtime Environment 1.6.0_91 (a.k.a. JRE 6u91-b13) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12.x for Windows-based desktop clients.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

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

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

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

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

What's new in in this Java release?

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

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

Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package.

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

The latest updates to that page (as of Sept. 19, 2012) state:

Java SE 6 End of Public Updates Notice

After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

What does this mean for Oracle E-Business Suite users?

EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

In other words, nothing changes for EBS users after February 2013. 

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017. 

How can EBS customers obtain Java 6 updates after the public end-of-life?

EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.9 can run JRE 7 or 8 plug-ins.  See these articles:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

References

Related Articles

Tuesday Jan 20, 2015

Critical Patch Update for January 2015 Now Available

The  Critical Patch Update (CPU) for January 2015 was released on January 20, 2015.  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 14, 2015
  • July 14, 2015
  • October 20, 2015
  • January 19, 2016
E-Business Suite Releases 11i and 12 Reference

Monday Jan 05, 2015

Enhance E-Business Suite Security By Switching to TLS

It seems fitting to start 2015 with a security-related blog post about Secure Socket Layer (SSL) and Transport Layer Security (TLS).  TLS is the successor to SSL. TLS, like SSL, is a protocol that encrypts traffic between applications and servers. TLS is based on SSL 3.0. TLS 1.0 is sometimes referred to as SSL 3.1. Going forward you will hear us talk more about TLS and less about SSL.

TLS is considered to be more secure than SSL.  All systems that use SSL 3.0 may be vulnerable to a design vulnerability in SSL’s handling of block cipher mode padding.  The Padding Oracle on Downgraded Legacy Encryption (POODLE) attack is one possible attack vector for web browsers and web servers.

Oracle E-Business Suite customers can migrate to TLS and mitigate the effects of POODLE attacks by following:

Happy 2015!

.Related Articles

References

Wednesday Dec 31, 2014

2014: A Year in Review for Oracle E-Business Suite

Happy New Year.  2014 was another big year for the Oracle E-Business Suite. 

Did you miss any of the most-important articles of the year?

Upgrading to EBS 12.2

Updates to EBS 12.2

Updates to EBS 12.1

Java

Important Technology Stack Updates

Virtualization

Maintaining and Extending EBS

Support Policies

Monday Dec 29, 2014

Quarterly EBS Upgrade Recommendations: December 2014 Edition

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

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

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

You can research these yourself using this Note:

Upgrade Recommendations for December 2014

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Tuesday Dec 23, 2014

Running E-Business Suite on Exalogic and Exadata

Exalogic serverPrior articles have noted that you can run the E-Business Suite on Oracle Engineered Systems such as Exalogic Elastic Cloud and Exadata Database Machine

What EBS combinations can you run on Exalogic and Exadata?

We certify E-Business Suite releases on operating systems and database releases (e.g. EBS 12.1.3 is certified on Database 12.1.0.2 on Linux 6 x86-64), not specific configurations of hardware such as Exadata or Exalogic.  This means that you can run the E-Business Suite on Exadata and Exalogic with any of the certified combinations listed in the Certifications database on My Oracle Support.

Srini Chavali, my colleague in the Exalogic division, has published a nice summary of all of the latest resources:

Srini gives an overview of the process for getting EBS onto these systems, discusses VM templates and Maximum Availability Architectures, and points to other useful best practices and reference documents. 

Related Articles

Thursday Dec 18, 2014

DB 12.1.0.1 Certified with EBS 11i & R12 on Linux on IBM System z

IBM LogoOracle Database 12c Release 1 (12.1.0.1) is now certified with Oracle E-Business Suite Release 11i, 12.0, and 12.1 on the following Linux on IBM System z operating systems as 'database tier only' platforms:

Release 11i (11.5.10.2 + ATG PF.H.delta.7 (RUP 7) or higher), Release 12.0 (12.0.6 or higher), Release 12.1 (12.1.3 or higher):

  • Red Hat Enterprise Linux (RHEL) version 5 (64-bit)
  • Red Hat Enterprise Linux (RHEL) version 6 (64-bit)
  • Novell SUSE Linux Enterprise Server (SLES) version 11 (64-bit)

This is a 'database tier only' or 'split tier configuration' certification where the application tier must be on a fully certified E-Business Suite platform (see My Oracle Support Certifications for more information). IBM's z systems fully support a mixed platform architecture with distributed Unix and Linux certified application tier servers for customers looking to run Oracle E-Business Suite on System z.

This announcement includes:

  • Oracle Database 12cR1 version 12.1.0.1
  • Oracle Database 12cR1 version 12.1.0.1 Real Application Clusters (RAC)
  • Transparent Data Encryption (TDE) Column Encryption using Oracle Database 12cR1 version 12.1.0.1
  • Transparent Data Encryption (TDE) Tablespace Encryption using Oracle Database 12cR1 version 12.1.0.1
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 12cR1 version 12.1.0.1
  • Export/Import Process for Oracle E-Business Suite Release 11i with Oracle Database 12cR1 version 12.1.0.1
  • Export/Import Process for Oracle E-Business Suite Release 12.0 or 12.1 with Oracle Database 12cR1 version 12.1.0.1

Pending Certifications

The following are not yet certified and will be announced on a later date once completed.

  • Oracle Multitenant 12cR1 version 12.1.0.1
  • Oracle Database Vault 12cR1 version 12.1.0.1
  • Transportable Database and Transportable Tablespaces Data Migration Processes

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

Please also review the platform-specific Oracle Database Installation Guides for operating system and other prerequisites.

Related Articles

Thursday Dec 04, 2014

JRE Support Ends Earlier than JDK Support

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

Screenshot from Java Lifetime Support Policy document JDK JRE different dates

These dates are published here:

The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology (Java Web Start & Java Plug-in technologies) in these documents.

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

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

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

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

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

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

Related Articles

Friday Nov 21, 2014

Testing Your EBS Environment After Database Upgrades

Customers often ask, "What should I test after I upgrade my EBS database?" Your environment is, by definition, unique to you, with your own architectural configurations, setup data, and customizations.  You should always concentrate your testing efforts on the areas that may differ from our generic EBS tests.  Until now, our generic common-sense answer has always been, "Test what is important to your business."  

Our Quality Assurance group in EBS Development has just published some guidance on the things that you might consider adding to your post-upgrade test plans:

They discuss things such as memory-intensive concurrent requests, compliance with new standards for initialization parameters, custom workflows, and more.

Your feedback is welcome.  I'll make sure that the Note's authors are notified if you drop me an email or post a comment here. 

Related Articles

Friday Nov 14, 2014

Java JRE 8 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

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

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

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

    No.

    This upgrade is highly recommended but remains optional while Java 6 and 7 are covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

    Impact of enabling JRE Auto-Update

    Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

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

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

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

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

    Coexistence of multiple JRE releases Windows desktops

    The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

    Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

    What do Mac users need?

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

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

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

    Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

    No.

    JRE is used for desktop clients.  JDK is used for application tier servers.

    JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

    JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

    References

    Related Articles
    The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 


    Thursday Nov 13, 2014

    EBS 12.2.4 OA Extensions for Jdeveloper 10g Now Available

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

    The version of Oracle JDeveloper is specific to the Oracle E-Business Suite Applications Technology patch level, so there is a new version of Oracle JDeveloper with each new release of the Oracle E-Business Suite Applications Technology patchset.

    The Oracle Applications (OA) Extensions for JDeveloper 10g are now available for E-Business Suite Release 12.2.4.  For details, see:

    The same Note also lists the latest OA Extension updates for EBS 11i, 12.0, 12.1, as well as 12.2.

    Related Articles

    Tuesday Oct 21, 2014

    Migrating EBS Environments to Unicode

    It is possible to migrate an E-Business Suite database to a new character set. You might need to do this when you expand your EBS deployment to additional countries, or when preparing for an upgrade to an EBS release that will be used globally.

    You will generally migrate your EBS character set to Unicode (AL32UTF8).  You must use the Database Migration Utility for Unicode (DMU) to scan for data conversion issues.

    Instructions for using the DMU tool with EBS character set conversions are published here:

    Thursday Oct 16, 2014

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

    Java logo

    Java Runtime Environment 1.7.0_71 (a.k.a. JRE 7u71-b14) and 1.7.0_72 (7u72-b14) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.

    Effects of new support dates on Java upgrades for EBS environments

    Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

    • What does this mean for Oracle E-Business Suite users?
    • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
    • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

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

    Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

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

    What's new in this release?

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

    There are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it.

    JRE 1.7.0_71  (7u71) is a CPU release. If you are running on the JRE 7 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 7 Plug-in.

    32-bit and 64-bit versions certified

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

    For EBS 12.0, 12.1, 12.2
    EBS + Discoverer 11g Users

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

    Worried about the 'mismanaged session cookie' issue?

    No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

    The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

    The latest updates to that page (as of Sept. 19, 2012) state (emphasis added):

    Java SE 6 End of Public Updates Notice

    After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

    What does this mean for Oracle E-Business Suite users?

    EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

    In other words, nothing changes for EBS users after February 2013. 

    EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017.

    How can EBS customers obtain Java 6 updates after the public end-of-life?

    EBS customers can download Java 6 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

    Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

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

    This upgrade is highly recommended but remains optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Java 6 is covered by Extended Support until June 2017.  All E-Business Suite customers must upgrade to JRE 7 by June 2017.

    Coexistence of JRE 6 and JRE 7 on Windows desktops

    The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

    Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 7 will be invoked instead of JRE 6 if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

    Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

    Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

    JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

    The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

    What do Mac users need?

    Mac users running Mac OS X 10.9 can run JRE 7 plug-ins.  See this article:

    Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

    JRE is used for desktop clients.  JDK is used for application tier servers

    JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

    Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

    JDK 7 is certified with E-Business Suite 12.  See:

    References

    Related Articles
    About

    Search

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