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

    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

      Friday Oct 18, 2013

      Sign E-Business Suite JAR Files Now

      Java Security logoOracle E-Business Suite uses Java, notably for running Forms-based content via the Java Runtime Environment (JRE) browser plug-in. 

      The default security settings for the JRE plug-in are expected to become more stringent over time.  To prepare for upcoming changes to Java security, all EBS 11i, 12.0, 12.1, and 12.2 system administrators must follow the procedures documented here:

      More information about Java security is available here:

      Getting help

      If you have questions about Java Security, please log a Service Request with Java Support.

      If you need assistance with the steps for signing EBS JAR files, please log a Service Request against the "Oracle Applications Technology Stack (TXK)" > "Java."


      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

        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

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

        Wednesday Apr 17, 2013

        Java JRE 1.6.0_45 Certified with Oracle E-Business Suite

        The latest Java Runtime Environment 1.6.0_45 (a.k.a. JRE 6u45-b06) 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_45?

        See the 1.6.0_45 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism. Java logo

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

        References

        Related Articles

        Tuesday Mar 05, 2013

        Resolving "JInitiator version too low" Errors in EBS Environments

        [Aug. 7, 2013: Clarified JRE 1.7 compatibility with EBS; removed old interop patch numbers]

        Oracle JInitiator 1.3 was desupported for E-Business Suite environments at the end of July 2009.  JInitiator 1.1.8 was desupported at the end of December 2008. E-Business Suite users should have switched from Oracle JInitiator to the native Java JRE plug-in at that time.

        JRE 1.7 is certified with E-Business Suite 11i, 12.0, and 12.1. Some EBS sysadmins are mistakenly concluding that the following error message means that they must revert to JRE 1.6:

        FRM-92095: Oracle Jlnitiator version too low. Please install version 1.1.8.2 or higher.

        FRM-92095: Oracle Jlnitiator version too low. Please install version 1.1.8.2 or higher.

        Details:
        Java Exception: oracle.forms.engine.RunformException: FRM-92095: oracle Jlnitiator version too low. Please install version 1.1.8.2 or higher.

        at oraclr.forms.net.HTTPConnection.<init>(Unknown Source)
        at oraclr.forms.engine.FormsDispatcher.initConnection(Unknown Source)
        at oraclr.forms.engine.FormsDispatcher.init(Unknown Source)
        at oraclr.forms.Runform.initConnection(Unknown Source)
        at oraclr.forms.Runform.startRunForm(Unknown Source)
        at oraclr.forms.Main.createRunform(Unknown Source)
        at oraclr.forms.Main.start(Unknown Source)
        at com.sun.deploy.uitoolkit.impl.awt.AWTAppletAdapter.start(Unknown Source)
        at sun.plugin2.applet.plugin2Manager$AppletExecutuonRunnable.run(Unknown Source)
        at java.lang.Thread.run(Threat.java.722)

        What's causing this error?

        This error message may occur if you try and launch an E-Business Suite form using the JRE 7 client plug-in without applying the prerequisite Forms patch needed to enable JRE 7 compatibility.

        What's needed to enable EBS environments for JRE 7?

        EBS customers should ensure that they are running the latest JRE 7 plug-in, at minimum, on Windows desktop clients.  If you've reached this article via a search engine, please check our Certifications summary page for the latest certified JRE 7 release.

        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.  Clease check the Notes for the authoritative list of patches.

        The documented interop 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

        Related Articles

        Monday Mar 04, 2013

        Java JRE 1.6.0_43 Certified with Oracle E-Business Suite

        The latest Java Runtime Environment 1.6.0_43 (a.k.a. JRE 6u43-b01) 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_43?

        See the 1.6.0_43 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism. Java logo

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

        References

        Related Articles

        Tuesday Feb 19, 2013

        Java JRE 1.6.0_41 Certified with Oracle E-Business Suite

        The latest Java Runtime Environment 1.6.0_41 (a.k.a. JRE 6u41-b02) 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_41?

        See the 1.6.0_41 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism. Java logo

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

        References

        Related Articles

        Saturday Feb 02, 2013

        Java JRE 1.6.0_39 Certified with Oracle E-Business Suite

        Java logoThe latest Java Runtime Environment 1.6.0_39 (a.k.a. JRE 6u39-b04) 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_39?

        See the 1.6.0_39 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

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

        References

        Related Articles

        Friday Jan 18, 2013

        Quarterly E-Business Suite Upgrade Recommendations: January 2013 Edition

        [Updated Jan. 22: Added link for OAM 11.1.2; thanks to Jennifer C. for pointing out the inadvertent omission]

        I've previously published advice on the general priorities for applying EBS updates.  But what are your top priorities for major upgrades to EBS and its technology stack components?

        Here 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 January 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 Oracle Access Manager 11gR1 11.1.1.5 Bundle Patch 4 or OAM 11gR2 11.1.2.

        6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to Oracle Access Manager 10g 10.1.4.3.

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

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

        9. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.6 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_38 or later 1.6 updates, or JRE 1.7.0_11 or later 1.7 updates.

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

        Related Articles

        Friday Jan 04, 2013

        Java JRE 1.6.0_38 Certified with Oracle E-Business Suite

        [Editor's note: this announcement should have gone out concurrently with the JRE 1.7 certification announcement; our apologies for the inadvertent delay]

        Java logoThe latest Java Runtime Environment 1.6.0_38 (a.k.a. JRE 6u38-b05) is now certified with Oracle E-Business Suite Release 11i and 12 desktop clients.  

        What's new in Java 1.6.0_38?

        See the 1.6.0_38 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

        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.

        All JRE 1.6 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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

        References

        Related Articles

        Wednesday Nov 07, 2012

        Implications of Java 6 End of Public Updates for EBS Users

        [Update Feb. 28, 2013: Added pointer to Note 1439822.1]

        [Update Dec. 11, 2012: JRE 7 is now certified with the E-Business Suite; see this announcement for complete details.]

        Java logo

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

        The certification of Oracle E-Business Suite with JRE 7 (for desktop clients accessing EBS Forms-based content) is in its final stages.  If you plan to upgrade your EBS desktop clients to JRE 7 when that certification is released, you can get a head-start on that today.

        Coexistence of JRE 6 and JRE 7 on Windows desktops

        The upgrade to JRE 7 will be 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.

        The certification of Oracle E-Business Suite with JRE 7 for Mac-based desktop clients accessing EBS Forms-based content is underway. Mac users waiting for that certification may find this article useful:

        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.

        The certification of Oracle E-Business Suite with JDK 7 for EBS application tier servers on Windows, Linux, and Solaris as well as other platforms such as IBM AIX and HP-UX is planned.  Customers running platforms other than Windows, Linux, and Solaris should refer to their Java vendors's sites for more information about their support policies.

        Related Articles


        Wednesday Oct 31, 2012

        Java JRE 1.6.0_37 Certified with Oracle E-Business Suite

        Java logoMy apologies: this certification announcement got lost in the OpenWorld maelstorm.  Better late than never. The section below entitled, "All JRE 1.6 releases are certified with EBS upon release" should obviate the need for these announcements, but I know that people have gotten used to seeing these certifications referenced explicitly. 

        The latest Java Runtime Environment 1.6.0_37 (a.k.a. JRE 6u37-b06) is now certified with Oracle E-Business Suite Release 11i and 12 desktop clients.  

        What's new in Java 1.6.0_37?

        See the 1.6.0_37 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

        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.

        All JRE 1.6 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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

        Important

        For important guidance about the impact of the JRE Auto Update feature on JRE 1.6 desktops, see:

        References

        Related Articles

        Friday Oct 19, 2012

        Planning Bulletin for JRE 7: What EBS Customers Can Do Today

         [Update Dec. 11, 2012: JRE 7 is now certified with the E-Business Suite; see this announcement for complete details.]

        An initiative to certify Oracle E-Business Suite with JRE 7 desktop clients is underway.  We have tested EBS 11.5.10.2, 12.0, and 12.1 with JRE 7. We have fixes for nearly all of the compatibility issues now, and are working hard to produce the remaining fixes quickly.

        A. When will JRE 7 be certified with Oracle E-Business Suite?

        We will announce the certification of the E-Business Suite with JRE 7 once all fixes are available, verified, and documented.  Certification announcements will be distributed through My Oracle Support, My Oracle Support Community Forums, Oracle Technology Network Forums, newsletters, and user group news outlets.

        Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates.  In addition to the standard communication channels listed above, customers are encouraged to monitor or subscribe to this blog.   

        B. What can customers do to prepare for the JRE 7 certification?

        Customers should ensure that they are on the latest available JRE 6 update.

        Of the compatibility issues identified so far 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 today by ensuring that they have applied the latest certified patches documented for JRE 6 configurations to their EBS application tier servers:

        1. Apply Forms patch 14615390 to EBS 11i environments (Note 125767.1)
        2. Apply Forms patch 14614795 to EBS 12.0 and 12.1 environments (Note 437878.1)

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

        C. What else will be required by the final certified configuration?

        Oracle expects that all other compatibility issues will be resolved by installing a specific JRE 7 release, at minimum.  That specific release has not been finalized yet, and this is subject to change.

        D.  Where will the official patch requirements be documented?

        All patches required for ensuring full compatibility of the E-Business Suite with JRE 7 will be documented in updates to these published Notes:

        For EBS 11i:

        For EBS 12
        Disclaimer

        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 Oct 05, 2012

        Quarterly E-Business Suite Upgrade Recommendations: October 2012 Edition

        I've previously published advice on the general priorities for applying EBS updates.  But what are your top priorities for major upgrades to EBS and its technology stack components?

        Here 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, support deadlines, and newly-certified releases. 

        Upgrade Recommendations for October 2012

        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 Oracle Access Manager 11g 11.1.1.5.

        6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to Oracle Access Manager 10g 10.1.4.3.

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

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

        9. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.6 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_35 or later 1.6 updates.

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

        Related Articles

        Thursday Aug 30, 2012

        Java JRE 1.6.0_35 Certified with Oracle E-Business Suite

        Java logoThe latest Java Runtime Environment 1.6.0_35 (a.k.a. JRE 6u35-b10) is now certified with Oracle E-Business Suite Release 11i and 12 desktop clients.  

        What's new in Java 1.6.0_35?

        See the 1.6.0_35 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

        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.

        All JRE 1.6 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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

        Important

        For important guidance about the impact of the JRE Auto Update feature on JRE 1.6 desktops, see:

        References

        Related Articles

        Wednesday Aug 15, 2012

        Java JRE 1.6.0_34 Certified with Oracle E-Business Suite

        Java logoThe latest Java Runtime Environment 1.6.0_34 (a.k.a. JRE 6u34-b04) is now certified with Oracle E-Business Suite Release 11i and 12 desktop clients.  

        What's new in Java 1.6.0_34?

        See the 1.6.0_34 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

        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.

        All JRE 1.6 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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

        Important

        For important guidance about the impact of the JRE Auto Update feature on JRE 1.6 desktops, see:

        References

        Related Articles

        Wednesday Jun 13, 2012

        URGENT BULLETIN: All E-Business Suite End-Users Must Manually Apply JRE 6 Updates

        [Update Dec. 11, 2012: JRE 7 is now certified with the E-Business Suite; see this announcement for complete details.]

        [Update Oct. 19, 2012: All customers can begin preparing for JRE 7 now by applying a Forms-based patch to their E-Business Suite environments.  For details, see: Planning Bulletin for JRE 7: What EBS Customers Can Do Today]

        [Update 10:00 AM June 20, 2012: Added reference to Note 1469230.1]

        [Update 9:35 AM June 19, 2012: Added reference to Note 1412103.2]

        [Update 11:40 AM June 14, 2012: Updated title based upon expanded guidance from Java team]

        [Update 9:15 AM June 14, 2012: Updated entire text based on expanded guidance from Java team]

        [Update 8:40 AM June 14, 2012: Clarified JRE version references]

        [Update 4:13 PM June 13, 2012: Added reference to My Oracle Support Note 1467442.1]

        [Update 1:40 PM June 13, 2012:  Added more details on finding the Java Update tab, and options 1 to 3]



        As previously announced, Oracle will shortly stop providing public updates for JRE 6.


        To ensure that Java Users remain on a secure version, Windows systems that rely on auto-update will be auto-updated from JRE 6 to JRE 7.

        Until EBS is certified with JRE 7, EBS users should not rely on the windows auto-update mechanism for their client machines and should manually keep the JRE up to date with the latest versions of 6 on an ongoing basis.

        How to get the latest version of JRE 6

        Until November of this year, the latest version of JRE 6 can be found on the Download tab of the Java SE sectionin OTN.  After November of this year further CPU (critical patch updates) to JRE 6 will be available through My Oracle Support.  Having a current EBS support contract grants you the right to download and use these JRE 6 versions on clients accessing EBS.

        Within your organization, you may distribute the latest version of JRE 6 to your users and ask them to run the installer on their systems (or use equivalent enterprise desktop distribution mechanisms).

        To maintain the security of your users’ desktops it is strongly recommended that you repeat the steps above after each CPU release.

        For Oracle Java SE Critical Patch Updates, the next three dates are listed on the Critical Patch Updates, Security Alerts and Third Party BulletinYou can subscribe to the RSS feed on the Bulletin above to receive updates to the CPU schedules.

        Reverting back to Java 6 from Java 7

        If an E-Business Suite end-user's desktop has been inadvertently upgraded to JRE 1.7, you must:

        1. Uninstall JRE 1.7
        2. Reinstall the latest JRE 1.6 release.

        Stay on Java 6 for now

        EBS customers should continue to run JRE 1.6 (a.k.a. JRE 6) on their Windows end-user desktops, and JDK 6 on their EBS servers.

        If a search engine has brought you to this article, please check the Certifications summary for our latest certified Java release.

        Our plans for certifying Java 7 for the E-Business Suite

        We plan on releasing the Java 7 certification for E-Business Suite customers in two phases:

        • Phase 1: Certify JRE 7 for Windows end-user desktops
        • Phase 2: Certify JDK 7 for server-based components

        When will Java 7 be certified with EBS?

        We're working on the first phase now. At this time, we cannot provide delivery dates, but you can monitor or subscribe to this blog for updates.

        Current known issues with JRE 1.7 in EBS environments

        Our current testing shows that there are known incompatibilities between JRE 1.7 and the Forms-invocation process in EBS environments.  In the meantime, EBS customers should not deploy JRE 1.7 to their end-user Windows desktop clients. EBS customers should remain on JRE 6 at this time. 

        References

        Related Articles

        Java JRE 1.6.0_33 Certified with Oracle E-Business Suite

        [June 14, 2012 Update: removed redundant JRE Auto Update information; pointed to standalone blog article]

        I'm pleased to let you know that the latest Java Runtime Environment 1.6.0_33 (a.k.a. JRE 6u33-b03) is now certified with Oracle E-Business Suite Release 11i and 12.  

        What's new in Java 1.6.0_33?

        See the 1.6.0_33 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

        32-bit and 64-bit versions certified

        This certification includes both the 32-bit and 64-bit JRE versions.  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.

        All JRE 1.6 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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

        Important

        For important guidance about the impact of the JRE Auto Update feature on JRE 1.6 desktops, see:

        References

        Related Articles

        Monday Jun 04, 2012

        Plans for Java 7 and E-Business Suite Certification

        [Update Dec. 11, 2012: JRE 7 is now certified with the E-Business Suite; see this announcement for complete details.]

        [Update Oct. 19, 2012: All customers can begin preparing for JRE 7 now by applying a Forms-based patch to their E-Business Suite environments.  For details, see: Planning Bulletin for JRE 7: What EBS Customers Can Do Today]

        Java logoAs of June 2012, Java 7 has not been certified yet with Oracle E-Business Suite.  EBS customers should continue to run JRE 6 on their Windows end-user desktops, and JDK 6 on their EBS servers.

        If a search engine has brought you to this article, please check the Certifications summary for our latest certified Java release.

        Our plans for certifying Java 7 for the E-Business Suite

        We plan on releasing the Java 7 certification for E-Business Suite customers in two phases:

        • Phase 1: Certify JRE 7 for Windows end-user desktops
        • Phase 2: Certify JDK 7 for server-based components

        When will Java 7 be certified with EBS?

        We're working on the first phase now. As usual, I cannot discuss release dates here, but you can monitor or subscribe to this blog for updates.

        Current known issues with JRE 7 in EBS environments

        Our current testing shows that there are known incompatibilities between JRE 7 and the Forms-invocation process in EBS environments.  We have been working directly with the Java division on this for a while now.  In the meantime, EBS customers should not deploy JRE 7 to their end-user Windows desktop clients. You should stick with JRE 1.6 for now. 

        But wait, you previously said...

        Older JRE certification announcements stated:

        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 higher.  We test all new JRE releases in parallel with the JRE development process, so all JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

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

        Yes, this is true.  This standard boilerplate text was written before JRE 7 was released, so there was no possibility of misunderstanding.  With the availability of JRE 7, that boilerplate needs to be revised to read:

        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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

        References

        Related Articles
        About

        Search

        Categories
        Archives
        « April 2014
        SunMonTueWedThuFriSat
          
        1
        4
        5
        6
        7
        8
        9
        10
        11
        12
        13
        14
        16
        17
        18
        19
        20
        21
        22
        23
        24
        25
        26
        27
        28
        29
        30
           
               
        Today