Tuesday Sep 09, 2014

Firefox ESR 31 Certified with Oracle E-Business Suite

Firefox ESR logo

[Update: Sep. 10, 2014: Removed listings for Windows XP and 8]

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

What is Mozilla Firefox ESR?

Mozilla has begun offering 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.

As of this announcement, Oracle E-Business Suite is certified with Firefox ESR 10, 17, 24, and 31.

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.

E-Business Suite Prerequisites

EBS 11i
  • Oracle E-Business Suite 11.5.10.2 
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) or later (Note 125767.1)
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or higher
  • Applications Framework Patch 7651759
  • Patch 7567782 which removes the use of the jpi-parameter and switches Firefox to a non-static versioning model.
EBS R12.0.x
  • Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or higher
  • Applications Framework Patch 7602616
  • Patch 7567840 which removes the use of the jpi-parameter and switches Firefox to a non-static versioning model.
EBS 12.1.x:
  • Base release

EBS 12.2.x:

  • Base release

Certified desktop operating systems

  • Windows 7 SP1
  • Windows Vista SP2

References

Your feedback is welcome

I'd be very interested in hearing about your plans for adopting Firefox Extended Support Releases in your environments.  Please drop me a private email or post your comments here with your thoughts on this.

Related Articles

Wednesday Aug 13, 2014

Quarterly E-Business Suite Upgrade Recommendations: August 2014 Edition

We've previously provided advice on the general priorities for applying EBS updates.  This article will help you understand your top priorities for major upgrades to EBS and its technology stack components.  This webcast can help you create a maintenance strategy.

The following is a summary of 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. 

Upgrade Recommendations for August 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 RP1 or 12.2.

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

  5. Oracle Database 10gR2 and 11gR1 users should upgrade to 11.2.0.4 or 12.1.0.1

  6. EBS 11i and 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.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_81 or later 1.6 updates or JRE 1.7.0_67 or later 1.7 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 24.

  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.

Related Articles

Tuesday Aug 05, 2014

JRE 1.7.0_67 Certified with Oracle E-Business Suite

Java logo

[Aug. 6, 2014 update: Removed sentence, "If you are already running 1.7.0_65 auto-update will not be triggered to upgrade to 1.7.0_67."]

Java Runtime Environment 1.7.0_67 (a.k.a. JRE 7u67-b01) 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?

JRE 1.7.0_67 fixes a regression in JRE 1.7.0_65 which prevented applets launching when using a "java_ arguments" parameter. This is the only change, it does not include any further security enhancements. Oracle E-Business Suite users are unlikely to be affected by this issue so moving to this release is optional, see the Update Release Notes for further information.

JRE 1.7.0_67 is available for download through the usual Java and Oracle Java SE Downloads public sites. The standard release is also available through Patch 19295656 as well as a special release which has the auto-update function turned off through Patch 19295660.

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

Tuesday Jul 22, 2014

Database 12.1.0.1 Certified with EBS on AIX, Itanium, Windows

As a follow up to the prior announcements, Oracle Database 12c Release 1 (12.1.0.1) is now certified with Oracle E-Business Suite 11i, 12.0 and 12.1 on the following additional platforms:

Release 11.5.10.2 + ATG_PF.H.delta.7 (RUP 7):
  • IBM AIX on Power Systems (64-bit) (6.1, 7.11)
  • HP-UX Itanium (11.31)1
Release 12.0 (12.0.6 and higher):
  • IBM AIX on Power Systems (64-bit) (6.1, 7.1)
  • HP-UX Itanium (11.31)
  • Microsoft Windows x64 (64-bit) (2008, 2008 R2)1
Release 12.1 (12.1.3 and higher):
  • IBM AIX on Power Systems (64-bit) (6.1, 7.1)
  • HP-UX Itanium (11.31)
  • Microsoft Windows x64 (64-bit) (2008 R2)2
1 : 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.
2 : Only via a migration process from an existing Windows (32-bit) system (see My Oracle Support Note 1188535.1, "Migrating Oracle E-Business Suite Release 12 to Microsoft Windows Server 2008 R2").

This announcement includes:
  • Oracle Database 12cR1 Version 12.1.0.1
  • Oracle Database 12cR1 Version 12.1.0.1 Real Application Clusters (RAC)
  • TDE Column Encryption with Oracle Database 12cR1 Version 12.1.0.1
  • TDE Tablespace Encryption with 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 EBS 11i with RDBMS 12cR1 Version 12.1.0.1
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
References

Release 11i
Release 12.0 and 12.1:

Related Articles

Tuesday Jul 15, 2014

JRE 1.7.0_65 Certified with Oracle E-Business Suite

Java logoJava Runtime Environment 1.7.0_65 (a.k.a. JRE 7u65-b19) 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?

JRE 1.7.0_65 (7u65-b19) is a CPU release. If you are running on the JRE 7 stream, it is strongly recommended that you upgrade to this latest version of the JRE 7 Plug-in.

Details about update in this release are listed in the release notes.

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

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.6.0_81 Certified with Oracle E-Business Suite

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in in this Java release?

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

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Wednesday Jun 04, 2014

Java JRE 1.7.0_60 Certified with Oracle E-Business Suite

Java logoJava Runtime Environment 7u60 (a.k.a. JRE 7u60-b19) 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 JRE 1.7.0_60?

JDK 7u60 contains IANA time zone data version 2014b. For more information, refer to Timezone Data Versions in the JRE Software.

It is strongly recommended that all customers upgrade to this release.  Details about update in this release are listed in the release notes.

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

JRE 1.7.0_60 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

Tuesday Jun 03, 2014

Oracle Database 11.2.0.4 Certified with EBS on Microsoft Windows Server

Microsoft logoAs a follow up to to a previous announcement, Oracle Database 11g Release 2 (11.2.0.4) is now certified with Oracle E-Business Suite Release 11i and Release 12 on the following Microsoft Windows Server operating systems:

Release 12.2 (12.2.3 and higher):

  • Microsoft Windows x64 (64-bit) (2008 R2)

Release 12.1 (12.1.1 and higher):

  • Microsoft Windows Server (32-bit) (2003, 2008)
  • Microsoft Windows x64 (64-bit) (20031, 20081, 2008 R22)

Release 12.0 (12.0.4 and higher):

  • Microsoft Windows Server (32-bit) (2003)
  • Microsoft Windows x64 (64-bit) (2003, 2008, 2008 R2)1
Release 11i (11.5.10.2 + ATG PF.H RUP 6 and higher)::
  • Microsoft Windows Server (32-bit) (2003, 20081)
  • Microsoft Windows x64 (64-bit) (2003, 2008, 2008 R2)1

Notes:

1: This OS is a 'database tier only' or 'split tier configuration' platform where the application tier must be on a fully certified E-Business Suite platform.
2: This OS is a 'database tier only' platform for Release 11i. For 12.1.1 or higher, it is also supported on the application tier via the migration process outlined in My Oracle Support Document 1188535.1.

This announcement for Oracle E-Business Suite 11i and R12 includes:

  • Oracle Database 11gR2 version 11.2.0.4
  • Oracle Database 11gR2 version 11.2.0.4 Real Application Clusters (RAC)
  • Oracle Database Vault 11gR2 version 11.2.0.4
  • Transparent Data Encryption (Column Encryption) using Oracle Database 11gR2 version 11.2.0.4
  • TDE Tablespace Encryption using Oracle Database 11gR2 version 11.2.0.4
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 11gR2 version 11.2.0.4
  • Export/Import Process for Oracle E-Business Suite Release 11i and Release 12 Database Instances
  • Transportable Database and Transportable Tablespaces Data Migration Processes for Oracle E-Business Suite Release 11i and Release 12

Certification data in My Oracle Support (http://support.oracle.com) has been updated with this certification - please review the documents below for all requirements and additional details:

Where can I find more information?

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

Wednesday Apr 23, 2014

Plans for Certifying Internet Explorer 11 with Oracle E-Business Suite

Microsoft IE logo

[Sep. 26, 2014 Update:  IE 11 is certified with EBS 12.1.  Other certifications coming soon.]

Microsoft Internet Explorer 11 is the default browser for Windows 8.1.  It is also compatible with Windows 7.  IE 11 is not certified with any Oracle E-Business Suite releases yet.

If you've reached this article via a search engine, it's possible that a later update on our status is available.  For our latest status, please check the Desktop Client Certifications section of our one-page Certifications summary.

Our current plans for IE 11

We plan to certify Microsoft Internet Explorer 11with Oracle E-Business Suite Release 11.5.10.2, 12.0, 12.1, and 12.2. 

These certifications are underway now.  They will cover Windows 7 and 8 desktop clients, as well as companion certifications with Office 2013, Office 2010, and WebADI.

When will IE 11 be certified?

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.  I will post updates as soon as soon as they're available.    

Postpone IE 11 rollouts until certified with EBS

We're still certifying Microsoft Internet Explorer 11 with Oracle E-Business Suite 11.5.10.2, 12.0, 12.1, and 12.2. We have identified some compatibility issues that will require EBS updates to resolve.

You must ensure that your mission-critical desktops remain on an earlier certified browsers until this certification is completed.  As of the time this article was published, certified browsers include IE 10 and Firefox ESR 24 for Windows desktops.

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

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 Apr 18, 2014

After Windows XP and Office 2003: E-Business Suite Implications

Microsoft logoMicrosoft ended support for Windows XP and Office 2003 on April 8, 2014. 

Our policy for the E-Business Suite is that we support certified third-party products as long as the third-party vendor supports them.  When a third-party vendor retires a product, we consider that to be an historical certification for EBS.

What can EBS customers expect after April 2014?

After Microsoft desupports WinXP and Office 2003 in April 2014:

  • Oracle Support will continue to assist, where possible, in investigating issues that involve Windows XP clients or Office 2003.
  • Oracle's ability to assist may be limited due to limited access to PCs running WinXP or Office 2003.
  • Oracle will continue to provide access to existing EBS patches for WinXP or Office 2003 issues.
  • Oracle will provide new EBS patches only for issues that can be reproduced on later operating system configurations that Microsoft is actively supporting (e.g. Windows 7, Office 2010)

What should EBS users do?

Oracle strongly recommends that E-Business Suite upgrade their end-user desktops from Windows XP and Office 2003 to the latest certified equivalents.  As of today, those are Windows 8 and Office 2010 (32-bit or 64-bit). 

What about EBS desktop-based client/server tools?

EBS sysadmins might use up to 14 different desktop-based tools to administer selected parts of the E-Business Suite.  These are:

Still in use (i.e. eligible for Error Correction Support)
  • BI Publisher (BIP/XMLP)
  • Configurator Developer
  • Discoverer Administrator/Desktop
  • Forms/Reports Developer
  • JDeveloper OA Extensions
  • Sales for Handhelds
  • Warehouse Builder
  • Workflow Builder
  • XML Gateway Message Designer
Obsolete
    • Applications Desktop Integrator (ADI)
    • Balanced Scorecard Architect (BSC)
    • Financial Analyzer
    • Financial Services Suite
    • Sales Analyzer Client

All of the tools still in use are certified with Windows 7.

For complete details, see:

Pending Desktop Certifications 

A subset of desktop tools are certified with Windows 8.  Certifications for Windows 8.1 Update 1 and Office 2013 are still underway.

Although I cannot discuss certification dates, you can monitor this blog for updates on those pending certifications. 

EBS customers should avoid deploying Win8.1 or Office 2013 to end-users who depend on the E-Business Suite until these certifications are announced.

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.

Related Articles


Tuesday Apr 15, 2014

Java JRE 1.6.0_75 Certified with Oracle E-Business Suite

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in in this Java release?

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.7.0_55 Certified with Oracle E-Business Suite

Java logoJava Runtime Environment 7u55 (a.k.a. JRE 7u55-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 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 JRE 1.7.0_55?

JRE 1.7.0_55 is a security-related CPU release.  It is strongly recommended that all customers upgrade to this release.  Details about update in this release are listed in the release notes.

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

JRE 1.7.0_55 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

Quarterly E-Business Suite Upgrade Recommendations: April 2014 Edition

We've previously provided advice on the general priorities for applying EBS updates.  This article will help you understand your top priorities for major upgrades to EBS and its technology stack components.

The following is a summary of 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. 

Upgrade Recommendations for April 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 or 12.2.

  4. Oracle Database 10gR2 and 11gR1 users should upgrade to 11.2.0.4 or 12.1.0.1

  5. EBS 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.0.

  6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.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_75 or later 1.6 updates or JRE 1.7.0_55 or later 1.7 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 24.

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

Related Articles

Wednesday Jan 15, 2014

Java JRE 1.6.0_71 Certified with Oracle E-Business Suite

Java logo

[Jan. 16, 2014 Update:  replaced Windows versions with a generic pointer to the underlying Notes]

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in in this Java release?

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

    Related Articles

    Java JRE 1.7.0_51 Certified with Oracle E-Business Suite

    Java logoJava Runtime Environment 7u51 (a.k.a. JRE 7u51-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 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.

    New Features in JRE 1.7.0_51

    For a full list of new features included in this JRE release, see the JRE 1.7.0_51 Update Release Notes. Amongst other changes and features this includes:

    Changes to Security Slider
    • Self-Signed and Unsigned applets are now blocked on the default 'High' Security Setting. This setting also requires the inclusion of the 'permission' attribute.
    • For information on signing jar files with a 'Trusted Certificate', see Enhanced Jar Signing for Oracle E-Business Suite (Note 1591073.1)

    Exception Site List

    • The 'Exception Site List'  allows end users to control  their own application whitelist to by-pass a number of security rules. For example this would allow applications and sites to run even though they are using using self-signed certificates for example. For further information on this feature see the  Java SE Exception Site List document.

    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

    JRE 1.7.0_51 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

    Wednesday Jan 08, 2014

    Java (JDK) 7 Certified with E-Business Suite 12.2 Servers

    Java logoOracle E-Business Suite 12.2 shipped with Java SE (JDK) 6 as part of its Rapid Install technology stack. 

    Java (JDK) 7 is now certified for EBS 12.2 application and database tier servers.  See:

    You can apply the Java 7 update on all tier nodes:

    • Java 6.0 either Oracle JRockit (JRockit) or Java SE Development Kit (JDK), on the application tier
    • 32-bit or 64-bit Java 6 for use by Oracle WebLogic Server 11.1.1.6.0 only
    • Non-WebLogic middle tier nodes using 32-bit Java version 6.0 only
    • Java SE Development Kit (JDK) version 6.0 on the OracleAS 10g 10.1.2 application tier hosting Oracle Forms and Reports services
    • Java SE Runtime Environment (JRE) version 6.0 on the database tier

    End-users can use either JRE 6 or 7 on their Windows desktop clients to run Forms-based products in EBS 12.2.

    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 changed 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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF).

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

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

    Will EBS users be forced to upgrade to JDK 7 for EBS Servers?

    No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

    No. This upgrade will be highly recommended but currently remains optional. JRE 6 desktop clients can connect to EBS 12.2 environments running JDK 7.

    JRE 6 will be available to Windows users to run with EBS to the end of Java SE 6 Extended Support in June 2017.  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. 

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

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

    No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 to the end of Java SE 6 Extended Support in June 2017.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 to the end of June 2017.

    Summary of EBS Certifications

    There is a one-page summary of all of the latest E-Business Suite techstack certifications here:

    • http://blogs.oracle.com/stevenChan/resource/certifications.html

    This listing summarizes the official CERTIFY database on My Oracle Support.  The CERTIFY database is the official and authoritative reference for all E-Business Suite certifications.

    Related Articles


    Monday Dec 02, 2013

    Office 2010 64-bit Certified with EBS 12

    Office 2010 logoMicrosoft Office 2010 64-bit is now certified with EBS 12.0.6, 12.1.3, and 12.2 with desktop clients using the following configurations:

    The 32-bit equivalents are already certified; details are available here.

    Are any patches required?

    You must apply server-side patches to EBS 12.0.6 and 12.1.3 environments.  Additional server-side patches are not required for EBS 12.2.x.  All required interop patches are documented here:

    What about EBS 11i?

    There are no plans for this certification in E-Business Suite 11i.  This certification primarily affects Web Application Desktop Integrator (a.k.a. WebADI, BNE) and Report Manager (FRM) integration with a 64-bit desktop client configuration.  Architectural constraints in the EBS 11i versions of these components make these certifications infeasible.

    What EBS products are covered by this certification?

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

    Which Office versions are certified?

    We explicitly tested Microsoft Office 2010 64-bit Professional Edition with Oracle E-Business Suite.  We expect that our certification tests also apply to the 64-bit equivalents, if available, to the following editions:

    • Home and Student Edition
    • Home and Business Edition
    • Standard Edition
    • Professional Academic Edition
    • Professional Plus Edition
    We have no plans to certify the following editions with Oracle E-Business Suite:
    • Office Web Apps
    • Starter Edition
    • Mac Edition
    • Office Mobile
    I would not expect the results of our certification with Office 2010 Professional Edition to apply to the four editions above.

    How are these integrations supported?

    You can log Service Requests against the E-Business Suite product that you're trying to integrate with Microsoft Office. 

    For example, you might be trying to take advantage of CRM Marketing (AMS) 12.1.2's integration with Excel 2010.  To get support, you can log an SR against CRM Marketing directly. 

    The Support team for that product will help you diagnose and resolve the problem.  If the issue is isolated to a Microsoft product, then it may be necessary to log a corresponding support ticket with Microsoft, as well.

    Related Articles


    Tuesday Nov 19, 2013

    Quarterly E-Business Suite Upgrade Recommendations: November 2013 Edition

    We've previously provided advice on the general priorities for applying EBS updates.  This article will help you understand your top priorities for major upgrades to EBS and its technology stack components.

    The following is a summary of 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. 

    Upgrade Recommendations for November 2013

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

    4. Oracle Database 10gR2 and 11gR1 users should upgrade to 11.2.0.4 or 12.1.0.1

    5. EBS 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.0.

    6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.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_65 or later 1.6 updates or JRE 1.7.0_45 or later 1.7 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 24.

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

      Related Articles

      Thursday Nov 14, 2013

      Firefox ESR 24 Certified with Oracle E-Business Suite

      Firefox ESR logoMozilla Firefox 24 Extended Support Release (ESR) is certified as a Windows-based client browser for Oracle E-Business Suite 11i, 12.0, 12.1, and 12.2.

      What is Mozilla Firefox ESR?

      Mozilla has begun offering 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.

      Firefox ESR schedule

      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.

      As of this announcement, Oracle E-Business Suite is certified with Firefox ESR 10, 17, and 24.

      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.

      E-Business Suite Prerequisites

      EBS 11i
      • Oracle E-Business Suite 11.5.10.2 
      • Oracle Developer 6i patchset 19 (6.0.8.28.x) or later (Note 125767.1)
      • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or higher
      • Applications Framework Patch 7651759
      • Patch 7567782 which removes the use of the jpi-parameter and switches Firefox to a non-static versioning model.
      EBS R12.0.x
      • Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or higher
      • Applications Framework Patch 7602616
      • Patch 7567840 which removes the use of the jpi-parameter and switches Firefox to a non-static versioning model.
      EBS 12.1.x:
      • Base release

      EBS 12.2.x:

      • Base release

      Certified desktop operating systems

      • Windows 8
      • Windows 7 SP1
      • Windows Vista SP2
      • Windows XP SP3

      References

      Your feedback is welcome

      I'd be very interested in hearing about your plans for adopting Firefox Extended Support Releases in your environments.  Please drop me a private email or post your comments here with your thoughts on this.

      Related Articles

      Thursday Oct 17, 2013

      Java JRE 1.7.0_45 Certified with Oracle E-Business Suite

      Java logoJava Runtime Environment 7u45 (a.k.a. JRE 7u45-b18) 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 needed to enable EBS environments for JRE 7?

      EBS customers should ensure that they are running JRE 7u17, at minimum, on Windows desktop clients.

      Of the compatibility issues identified with JRE 7, the most critical is an issue that prevents E-Business Suite Forms-based products from launching on Windows desktops that are running JRE 7. 

      Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers. 

      These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite.  These patches may be applied immediately to all E-Business Suite environments. All other Forms prerequisites documented in the Notes above should also be applied. 

      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

      JRE 1.7.0_45 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 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

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

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

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

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

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

      References

      Related Articles

      Java JRE 1.6.0_65 Certified with Oracle E-Business Suite

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

      Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

      What's new in in this Java release?

      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:

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

      32-bit JREs are certified on:

      • Windows XP Service Pack 3 (SP3)
      • Windows Vista Service Pack 1 (SP1) and Service Pack 2 (SP2)
      • Windows 7 and Windows 7 Service Pack 1 (SP1)

      64-bit JREs are certified only on 64-bit versions of Windows 7 and Windows 7 Service Pack 1 (SP1).

      Worried about the 'mismanaged session cookie' issue?

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

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

      Implications of Java 6 End of Public Updates for EBS Users

      The Support Roadmap for Oracle Java is published here:

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

      Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

        Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

        Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

        What do Mac users need?

        Mac users running Mac OS 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

        EBS 12 certified with Mac OS X 10.7 and 10.8 with Safari 6 and JRE 7

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

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

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

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

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

        References

        Related Articles

        Friday Sep 27, 2013

        Microsoft Windows 8 Certified with Oracle E-Business Suite

        Microsoft Windows 8 logoI'm very pleased to announce that Microsoft Windows 8 desktop clients are certified for the Oracle E-Business Suite 11.5.10.2, 12.0, 12.1, and 12.2. This certification applies to the following editions:

        • Windows 8
        • Windows 8 Enterprise
        • Windows 8 N edition
        • Windows 8 Pro N edition
        • Windows 8 Pro Pack N edition
        Internet Explorer 10
        Oracle E-Business Suite 11.5.10.2 Prerequisites
        • Oracle Applications 11.5.10.2
        • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or later.
        • Oracle Developer 6i patchset 19 (6.0.8.28.x) (Note 125767.1).
        • MLR Patch 8888184
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates
        Oracle E-Business Suite R12.0 Prerequisites
        • Oracle E-Business Suite 12.0.6
        • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or later.
        • Oracle Forms Version 10.1.2.3 or later.
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates
        Oracle E-Business Suite 12.1 Prerequisites
        • Oracle E-Business Suite 12.1.3
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates

        Oracle E-Business Suite 12.2 Prerequisites

        • Oracle E-Business Suite 12.2.2 or higher
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates
        Firefox ESR 17
        Oracle E-Business Suite 11i Prerequisites
        • Oracle E-Business Suite 11.5.10.2.
        • Oracle Developer 6i patchset 19 (6.0.8.28.x) or later (note 125767.1)
        • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6)(patch 5903765) or later
        • Applications Framework Patch 7651759
        • Patch 7567782 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model.
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates
        Oracle E-Business Suite R12.0 Prerequisites
        • Oracle E-Business Suite 12.0.6
        • Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or later
        • Applications Framework Patch 7602616
        • Patch 7567840 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model.
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates
        Oracle E-Business Suite R12.1 Prerequisites
        • Oracle E-Business Suite 12.1.3 or higher
        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates
        Oracle JInitiator Not Compatible

        Oracle JInitiator was built on top of Java 1.3.  Java 1.3 is desupported and is not compatible with Windows 8, Windows Vista, or Windows 7.  We have no plans to certify Oracle JInitiator with Windows 8.

        Premier Support for Oracle JInitiator 1.1.8 ended in December 2008, and Premier Support for Oracle JInitiator 1.3 ended for EBS customers in July 2009.

        Use the Native JRE plug-in

        Windows 8 desktop clients are certified only with the native Java Runtime Environment (JRE) with Windows 8. 

        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. 

        The minimum JRE prerequisites for Windows 8 are higher than in previous releases.  These are:

        • Java client plug-in JRE 1.6.0_37 or later 1.6 updates
        • Java client plug-in JRE 1.7.0_10 or later 1.7 updates

        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. This applies to all certified Windows desktop operating systems, including XP, Vista, 7, and 8.

        WebADI and Report Manager Users

        Running WebADI and Report Manager through Excel on Windows 8 has additional patch requirements. For further information see Document 1077728.1.

        What About Windows Hyper-V?

        End-users are able to run Windows XP, Vista, and 7 as client guest operating systems via Windows Hyper-V on a Win8 desktop client.

        We have no plans to conduct separate EBS certification efforts for Hyper-V guest client configurations running on Win8 clients.  Oracle Support will attempt to reproduce reported issues using non-virtualized WinXP, Vista, or 7 desktop clients.  Microsoft Support may to be engaged for any issues that can only be reproduced only in Hyper-V on Windows 8 desktops.

        What about other Windows 8 editions?

        We do not currently plan to certify the following editions with Oracle E-Business Suite:

        • Windows RT
        • Windows 8 tablet-oriented interface (formerly called Metro)
        I would not expect the results of our certification to apply to Windows RT.

        What About Earlier Versions of IE?

        Microsoft only supports IE 10 on Windows 8 desktops.  Microsoft does not support earlier versions of IE on Win8, so Oracle is only able to support IE10 on Windows 8 clients for the E-Business Suite.

        Pending Win8 Certifications

        BiDi (Arabic and Hebrew Languages)

        Due to issues with right side truncation, Windows 8 is not currently certified for BiDi (Arabic and Hebrew) languages. A patch fix for this issue is in progress.

        MS Projects

        Posting information between Oracle Projects and Microsoft Projects will currently error when running on Windows 8. A patch fix for this issue is in progress. For further information see Document 1077728.1 listed below.

        Client Server Products

        The majority of Client/Server products are either not currently certified or will not be certified on Windows 8. For further information see document 277535.1 listed below.

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

        References

        Related Articles

        Wednesday Sep 11, 2013

        Java JRE 1.6.0_60 Certified with Oracle E-Business Suite

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

        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 Java 1.6.0_60?

        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:

        32-bit and 64-bit versions certified

        This certification includes both the 32-bit and 64-bit JRE versions.

        32-bit JREs are certified on:

        • Windows XP Service Pack 3 (SP3)
        • Windows Vista Service Pack 1 (SP1) and Service Pack 2 (SP2)
        • Windows 7 and Windows 7 Service Pack 1 (SP1)

        64-bit JREs are certified only on 64-bit versions of Windows 7 and Windows 7 Service Pack 1 (SP1).

        Worried about the 'mismanaged session cookie' issue?

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

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

        Implications of Java 6 End of Public Updates for EBS Users

        The Support Roadmap for Oracle Java is published here:

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

        Java SE 6 End of Public Updates Notice

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

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

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

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

        EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

        1. EBS 11i Extended Support ends November 2013
        2. EBS 12.0 Extended Support ends January 2015
        3. EBS 12.1 Extended Support ends December 2018

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

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

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

        No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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. 

        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 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

        EBS 12 certified with Mac OS X 10.7 and 10.8 with Safari 6 and JRE 7

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

        No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

        Java (JDK) 7 Certified for E-Business Suite 12 Servers

        References

        Related Articles

        Java JRE 1.7.0_40 Certified with Oracle E-Business Suite

        Java logoJava Runtime Environment 7u40 (a.k.a. JRE 7u40-b43) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12 for Windows-based desktop clients.

        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 needed to enable EBS environments for JRE 7?

        EBS customers should ensure that they are running JRE 7u17, at minimum, on Windows desktop clients.

        Of the compatibility issues identified with JRE 7, the most critical is an issue that prevents E-Business Suite Forms-based products from launching on Windows desktops that are running JRE 7. 

        Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers. 

        These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite.  These patches may be applied immediately to all E-Business Suite environments. All other Forms prerequisites documented in the Notes above should also be applied. 

        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

        Prerequisites for 32-bit and 64-bit JRE certifications

        JRE 1.70_40 32-bit + EBS 11.5.10.2

        JRE 1.70_40 32-bit + EBS 12.0 & 12.1

        JRE 1.7.0_40 64-bit + EBS 11.5.10.2

        JRE 1.70_40 64-bit + EBS 12.0 & 12.1

        EBS + Discoverer 11g Users

        JRE 1.7.0_40 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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

        1. EBS 11i Extended Support ends November 2013
        2. EBS 12.0 Extended Support ends January 2015
        3. EBS 12.1 Extended Support ends December 2018

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

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

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

        No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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. 

        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 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

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

        No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

        References

        Related Articles

        Friday Aug 09, 2013

        Internet Explorer 10 Certified with Oracle E-Business Suite

        MS IE logoMicrosoft Internet Explorer 10 is now certified as a desktop client browser for Oracle E-Business Suite Release 11i, 12.0, and 12.1.  The certified desktop operating systems are:

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

        EBS 12.1 Prerequisites

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

        EBS 12.0 Prerequisites

        • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or higher.
        • Oracle Forms Version 10.1.2.3 or higher.
        • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
        • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher

        EBS 11i Prerequisites

        • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or higher
        • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or higher.
        • Oracle Developer 6i patchset 19 (6.0.8.28.x) (see Note 125767.1)
        • MLR patch 8888184 or higher (see note 125767.1 for the latest release)
        • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
        • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher

        Compatibility Mode for IE 10 + EBS 12

        To prevent issues with certain OA Framework pages, you should run IE 10 in "Compatibility Mode." See the "Known Issues" section in Note 389422.1 for more details.

        JRE 1.7 is 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 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.

        "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


        Monday Jul 22, 2013

        Quarterly E-Business Suite Upgrade Recommendations: July 2013 Edition

        We've previously provided advice on the general priorities for applying EBS updates.  This article will help you understand your top priorities for major upgrades to EBS and its technology stack components.

        The following is a summary of 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. 

        Upgrade Recommendations for July 2013

        1. EBS 11i users should upgrade to 12.1.3, or -- if staying on 11i -- should be on the minimum 11i patching baseline,

        2. EBS 12.0 users should upgrade to 12.1.3, or -- if staying on 12.0 -- should be on the minimum 12.0 patching baseline,

        3. EBS 12.1 users should upgrade to 12.1.3.

        4. Oracle Database 10gR2 and 11gR1 users should upgrade to 11gR2 11.2.0.3.

        5. EBS 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.0 or OAM 11gR1 Patchset 2 11.1.1.7.

        6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.0 or Oracle Access Manager 10g 10.1.4.3.

        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_51 or later 1.6 updates , or JRE 1.7.0_25 or later 1.7 updates.

        11. All Firefox users should upgrade to Firefox Extended Support Release 17.

        Related Articles

        Wednesday Jul 03, 2013

        Microsoft Ending Support for Windows XP and Office 2003 in April 2014

        Microsoft LogoMicrosoft is ending support for Windows XP and Office 2003 on April 8, 2014.  The official announcement is published here:

        These products are certified for desktop clients accessing the E-Business Suite today.  Our general policy is that we support certified third-party products as long as the third-party vendor supports them.  When the third-party vendor retires a product, we consider that to be an historical certification for EBS.

        What can EBS customers expect after April 2014?

        After Microsoft desupports WinXP and Office 2003 in April 2014:

        • Oracle Support will continue to assist, where possible, in investigating issues that involve Windows XP clients or Office 2003.
        • Oracle's ability to assist may be limited due to limited access to PCs running WinXP or Office 2003.
        • Oracle will continue to provide access to existing EBS patches for WinXP or Office 2003 issues.
        • Oracle will provide new EBS patches only for issues that can be reproduced on later operating system configurations that Microsoft is actively supporting (e.g. Windows 7, Office 2010)

        What should EBS customers do?

        Oracle strongly recommends that E-Business Suite customers upgrade their desktops from Windows XP and Office 2003 to the latest certified equivalents.  As of today, those are Windows 7 and Office 2010. 

        Certifications for Windows 8 and Office 2013 are still underway; you can monitor this blog for updates on those pending certifications.  EBS customers should avoid deploying Win8 or Office 2013 to end-users who depend on the E-Business Suite until these certifications are announced.

        Related Articles

        Wednesday Jun 19, 2013

        Java JRE 1.6.0_51 Certified with Oracle E-Business Suite

        [Jun. 20, 2013 Update: corrected link to Java 6 downloads via My Oracle Support]

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

        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 Java 1.6.0_51?

        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:

        32-bit and 64-bit versions certified

        This certification includes both the 32-bit and 64-bit JRE versions.

        32-bit JREs are certified on:

        • Windows XP Service Pack 3 (SP3)
        • Windows Vista Service Pack 1 (SP1) and Service Pack 2 (SP2)
        • Windows 7 and Windows 7 Service Pack 1 (SP1)

        64-bit JREs are certified only on 64-bit versions of Windows 7 and Windows 7 Service Pack 1 (SP1).

        Worried about the 'mismanaged session cookie' issue?

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

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

        Implications of Java 6 End of Public Updates for EBS Users

        The Support Roadmap for Oracle Java is published here:

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

        Java SE 6 End of Public Updates Notice

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

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

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

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

        EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

        1. EBS 11i Extended Support ends November 2013
        2. EBS 12.0 Extended Support ends January 2015
        3. EBS 12.1 Extended Support ends December 2018

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

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

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

        No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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. 

        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 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

        EBS 12 certified with Mac OS X 10.7 and 10.8 with Safari 6 and JRE 7

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

        No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

        Java (JDK) 7 Certified for E-Business Suite 12 Servers

        References

        Related Articles

        Java JRE 1.7.0_25 Certified with Oracle E-Business Suite

        Java logoJava Runtime Environment 7u25 (a.k.a. JRE 7u25-b16) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12 for Windows-based desktop clients.

        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 needed to enable EBS environments for JRE 7?

        EBS customers should ensure that they are running JRE 7u17, at minimum, on Windows desktop clients.

        Of the compatibility issues identified with JRE 7, the most critical is an issue that prevents E-Business Suite Forms-based products from launching on Windows desktops that are running JRE 7. 

        Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers. 

        These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite.  These patches may be applied immediately to all E-Business Suite environments. All other Forms prerequisites documented in the Notes above should also be applied. 

        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

        Prerequisites for 32-bit and 64-bit JRE certifications

        JRE 1.70_25 32-bit + EBS 11.5.10.2

        JRE 1.70_25 32-bit + EBS 12.0 & 12.1

        JRE 1.7.0_25 64-bit + EBS 11.5.10.2

        JRE 1.70_25 64-bit + EBS 12.0 & 12.1

        EBS + Discoverer 11g Users

        JRE 1.7.0_25 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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

        1. EBS 11i Extended Support ends November 2013
        2. EBS 12.0 Extended Support ends January 2015
        3. EBS 12.1 Extended Support ends December 2018

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

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

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

        No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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. 

        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 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

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

        No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

        References

        Related Articles

        Monday Jun 10, 2013

        Java (JDK) 7 Certified for E-Business Suite 12.0 and 12.1 Servers

        Java logoWindows and Mac-based desktop clients connecting to the E-Business Suite can use the Java Runtime Environment (JRE) plug-in to run Forms-based components.  JRE 7 was certified with EBS 11.5.10.2, 12.0, and 12.1 in 2012.  As of today, the latest available version is JRE 1.7.0_21 for Windows clients and for Mac clients.  All new JRE releases on the 1.6 and 1.7 codelines are automatically certified with EBS on the day of their release.  If you're reaching this article via a search engine, please check My Oracle Support or the Certifications summary for the latest desktop version available.

        Java (JDK) 7 is now certified for E-Business Suite 12.0 and 12.1 application and database tier servers.  For instructions on upgrading your EBS 12.x environments, see:

        The Java version currently in your environment

        Oracle E-Business Suite Release 12 Rapid Install delivers the following Java SE Development Kit (JDK) Versions for use by Oracle E-Business Suite:

        Release 12.0.x

          • Java SE Development Kit (JDK) Version 5.0 on the application tier
          • Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
          • Java SE Runtime Environment (JRE) Version 5.0 on the database tier

        Release 12.1.x

          • Java SE Development Kit (JDK) Version 6.0 on the application tier
          • Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
          • Java SE Runtime Environment (JRE) Version 6.0 on the database tier

        You can now upgrade to the newer Java 7.0 Update on all EBS application tier and database tier nodes. Please note that the JRE 7.0 upgrade on the database tier is independent from the others. But if the application tier nodes are planned to be upgraded to Java 7.0, the same upgrade in the OracleAS 10.1.2 ORACLE HOME must be planned together.

        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 will change 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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

        1. EBS 11i Extended Support ends November 2013
        2. EBS 12.0 Extended Support ends January 2015
        3. EBS 12.1 Extended Support ends December 2018

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

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

        Will EBS users be forced to upgrade to JDK 7 for EBS Servers?

        No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

        No. This upgrade will be highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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. 

        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 290801.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 will Mac users need?

        Oracle will provide updates to JRE 7 for Mac OS X users. EBS users running Macs will need to upgrade to JRE 7 to receive JRE updates.

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

        No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

        References

        Related Articles

        About

        Search

        Categories
        Archives
        « July 2015
        SunMonTueWedThuFriSat
           
        1
        3
        4
        5
        7
        8
        9
        11
        12
        18
        19
        21
        23
        25
        26
        27
        31
         
               
        Today