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

Friday Apr 27, 2012

Sun JRE 1.6.0_32 Certified with Oracle E-Business Suite

Java logo

[Apr. 30, 2012 Update: Clarified certification information for JRE 7, added more details about Java 7 plans]

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

What's new in Java 1.6.0_32?

See the 1.6.0_32 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 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 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.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What about Java 7?

We're working on our Java 7 certification for the E-Business Suite right now.  Our first set of certifications will cover JRE 7 for Windows desktops.  This will be followed by JDK 7 certifications for server-based components.  

These certifications haven't been completed yet.  You should remain on Java 6 for both desktop-based and server-based components until we announce those certifications.

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

References

Related Articles

Wednesday Feb 15, 2012

Sun JRE 1.6.0_31 Certified with Oracle E-Business Suite

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

What's new in Java 1.6.0_31?

See the 1.6.0_31 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.

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 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 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.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

References

Related Articles

Tuesday Dec 13, 2011

Sun JRE 1.6.0_30 Certified with Oracle E-Business Suite

Java logo

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

What's new in Java 1.6.0_30?

See the 1.6.0_30 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.

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:  for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26, and higher.

All JRE 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 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.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

References

Related Articles

Thursday Oct 20, 2011

Sun JRE 1.6.0_29 Certified with Oracle E-Business Suite

Java logoSome questions following our last few JRE certifications indicated that there's still lingering confusion about which JRE releases are safe to use with E-Business Suite environments.  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:  for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26.

As of today, you can also apply Sun Java Runtime Environment 1.6.0_29 (a.k.a. JRE 6u29-b11).  JRE 1.6.0_29 is certified with E-Business Suite Release 11i and 12.

All JRE 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 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.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What happened to JRE 1.6.0_28?

JRE 1.6.0_28 (6u28) was not released externally.  JRE 1.6.0_29 is a CPU Security Java release.

References

Related Articles

Wednesday Aug 17, 2011

Sun JRE 1.6.0_27 Certified with Oracle E-Business Suite

Java logoSome questions following our last JRE certification indicated that there's still lingering confusion about which JRE releases are safe to use with E-Business Suite environments.  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:  for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26.

As of today, you can also apply Sun Java Runtime Environment 1.6.0_27 (a.k.a. JRE 6u27-b07).  JRE 1.6.0_27 is certified with E-Business Suite Release 11i and 12.

All JRE 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 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.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_27?

See the 1.6.0_27 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.

JRE 1.6.0_27 provides the following fixes and functionality change that may affect Oracle E-Business Suite customers:

  • The browser window opening behind the Forms window issue is now fixed for Windows Vista and Windows 7 users running IE.
  • Selecting the "Close Window" Link through Internet Explorer will no longer display a modal window with the prompt, "The webpage you are viewing is trying to close the tab, Do you want to close this tab?".
  • Due to JRE6u27 now adhering more strictly to the IE browser settings,  "File Export" and certain "Form Attachments" will now fail through IE without the correct browser setting for IE6, IE7 & IE8 users.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References

Related Articles

Wednesday Jun 08, 2011

Sun JRE 1.6.0_26 Certified with Oracle E-Business Suite

Java compatible logoYou might get a sense of deja vu when reading this article, but I'll keep repeating myself until it seems safe to stop.  To recap: the mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:

  • Sun Java Runtime Environment 1.6.0_26 (a.k.a. JRE 6u26-b03) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_26 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23, JRE 1.6.0_24, and JRE 1.6.0_25.
All JRE 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 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. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_26?

See the 1.6.0_26 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.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Friday May 27, 2011

Sun JRE 1.6.0_25 Certified with Oracle E-Business Suite

Java compatible logoThe mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:

  • Sun Java Runtime Environment 1.6.0_25 (a.k.a. JRE 6u25, 1.6.0_25-b06) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_25 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23 and JRE 1.6.0_24.
All JRE 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 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. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_25?

See the 1.6.0_25 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.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Tuesday Feb 15, 2011

Sun JRE 1.6.0_24 Certified with Oracle E-Business Suite

jceecolorlogo2.gif
The mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:
  • Sun Java Runtime Environment 1.6.0_24 (a.k.a. JRE 6u24, 1.6.0_24-b07) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_24 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23.
All JRE 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 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. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_24?

See the 1.6.0_24 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.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Tuesday Dec 07, 2010

Mismanaged Session Cookie Issue Fixed for EBS in JRE 1.6.0_23

jceecolorlogo2.gif
At last:  some good news for those of you affected by the mismanaged session cookie issue in E-Business Suite environments.  This issue is resolved by the latest Sun Java Runtime Environment 1.6.0_23 (a.k.a. JRE 6u23, internal version 1.6.0_23-b05).

See the 1.6.0_23 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.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Wednesday Oct 13, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_22

I'm afraid that this blog article comes bearing continued bad news about our latest JRE release.

jceecolorlogo2.gif
My colleagues in the Java division shipped Java Runtime Environment 1.6.0_22 (a.k.a. JRE 6u22, internal version 1.6.0_22-b04) last week.  See the 1.6.0_22 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.

Unfortunately, like other recent JRE releases, this latest release of JRE 6u22 (1.6.0_22-b04) still has the 'Mismanaged Session Cookie' issue that we reported in earlier articles.  This can cause a failure of the following E-Business Suite functions with certain desktop and browser combinations, notably for IE 6 and 7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails

A JRE plug-in release with fixes for these issues is only available through patch 10189354.  Patch 10189354 contains JRE 1.6.0_22-b03.  This fixed version is not available as a download from Sun or through the Java Update Mechanism (which continues to offer only JRE 1.6.0_22-b04).  This fix will not be available through the normal Sun distribution channels until a future release of JRE 1.6.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for JRE 1.6.0_23 or later
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_22-b03 (released via patch 10189354)
  4. Disable next-generation Java through the 'Java Control Panel'
I understand that this is a frustrating state of affairs and I apologize for the continued delay in resolving this once and for all.  We're continuing to work with our colleagues in the Java division to get this set of fixes into the main JRE codelines.  I'll post updates here as soon as I have more information to share.

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

Friday Aug 13, 2010

Special JRE 6u21-b08 Build Now Available for EBS Customers

jceecolorlogo2.gif
The painful saga of our recent JRE releases' issues with the Oracle E-Business Suite is almost over.  It is expected that a future release of JRE 1.6 will contain a mainline fix for the "Mismanaged Session Cookie" issues that exist with JRE 1.6.0_18 to 1.6.0_21 build 6 (6u21-b06), inclusive. 

There is an interim workaround until that new release is available.  JRE 1.6.0_21 build 8 (6u21-b08) is now available and certified for Oracle E-Business Suite 11i and R12. This Build of the native plug-in fixes the 'Mismanaged Session Cookie' issue for the JRE 6u21 stream, which could cause a failure of the following functionalities on certain desktop/browser combinations, and particularly prevalent for IE6 and IE7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails
Special release vehicle for this JRE build

This version of the plug-in is only available through patch 10021403 and is not available as a download through the usual channels or through the Java automatic update facility. The standard version of the plug-in remains at JRE 1.6.0_21 build 6 (6u21-b06). This fix will not be available through the usual channels until a future release of JRE 1.6.

This release also fixes the long standing z-ordering issue (HTML Window opens behind Forms Window) for Windows XP users running Internet Explorer. A permanent fix is not yet available for Firefox users or Windows Vista or Windows 7 users, therefore please continue to use one of the workaround options if required.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for the upcoming JRE release that includes this fix
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_20-b05 (released via patch 9915543)
  4. Deploy JRE 1.6.0_21-b08 (released via patch 10021403)
For further information and requirements please see:
Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle‚Äôs products remains at the sole discretion of Oracle.

Monday Jul 19, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_21

jceecolorlogo2.gif
My colleagues in the Java division shipped Java Runtime Environment 1.6.0_21 (a.k.a. JRE 6u21, internal version 1.6.0_21-b06) last week.  See the 1.6.0_21 Update Release Notes for details about what has changed in this release.

Unfortunately, this release of JRE 6u21 (1.6.0_21-b06) still has the 'Mismanaged Session Cookie' issue that we reported in earlier articles.  This can cause a failure of the following E-Business Suite functions with certain desktop and browser combinations, notably for IE 6 and 7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails
A JRE plug-in release with fixes for these issues is only available through patch 9915543.  Patch 9915543 contains JRE 1.6.0_20-b05.  This fixed version is not available as a download from Sun or through the Java Update Mechanism (which continues to offer only JRE 1.6.0_20-b02).  This fix will not be available through the normal Sun distribution channels until a future release of JRE 1.6.

A fixed version of the JRE 1.6.0_21 (6u21) plug-in is expected to be made available through a special patch download in the near future.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for JRE 1.6.0_22 or later
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_20-b05 (released via patch 9915543)
I understand that this is a frustrating state of affairs and I apologize for the continued delay in resolving this once and for all.  We're continuing to work with our colleagues in the Java division to get this set of fixes into the main JRE codelines.  I'll post updates here as soon as I have more information to share.

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

Thursday Apr 15, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_20

jceecolorlogo2.gif
My colleagues in the Java division have just released Java Runtime Engine (JRE) 1.6.0_20 today.  See the 1.6.0_20 Update Release Notes for details about what has been changed in this release.

The issues reported in the following articles still also apply to JRE 1.6.0_20:
Depending upon your security and Java deployment policies for your end-user desktops, you may need to update your users to this JRE release.  Unfortunately, you will have to balance your need for the fixes in JRE 1.6.0_20 against the impact of the open EBS compatibility issues reported with 6u18, 6u19, 6u20.

We're working closely with the Sun JRE team to get the open EBS compatibility issues resolved as quickly as possible.  This is being worked at the top priority.  Please monitor this blog for updates.


Monday Apr 05, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_19

jceecolorlogo2.gif
Sadly, the issues reported in the following article also apply to JRE 1.6.0_19:
Once again, if you haven't already upgraded your end-users to JRE 1.6.0_18 or 1.6.0_19, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).

We're working closely with the Sun JRE team to get this issue resolved as quickly as possible.  Please monitor this blog for updates.


Monday Mar 22, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_18

jceecolorlogo2.gif
Users need a Java client to run the Forms-based content in Oracle E-Business Suite.  With Oracle JInitiator 1.3 out of Premier Support as of July 2009, Apps users must run the native Sun Java Runtime Engine (JRE) to access this content.

In early 2008 we relaxed our certification and support policy for the use of the native Sun JRE clients with the E-Business Suite. The policy reflected a switch from certifying specific JRE versions for the E-Business Suite to specifying minimum versions, instead. This permits E-Business Suite users to run any JRE release above following minimum certified levels, even later ones that Oracle hasn't explicitly tested with the E-Business Suite:
  • JRE 1.5.0_13 and higher
  • JRE 1.6.0_03 and higher
Under our current policy, Oracle E-Business Suite end-users can upgrade their JRE clients whenever Sun releases a new JRE release on either the 1.5 or 1.6 versions. EBS users do not need to wait for Oracle to certify new JRE 1.5 or 1.6 plug-in updates with the E-Business Suite.

Known E-Business Suite Issues with JRE 1.6.0_18

We test every new JRE release with both E-Business Suite 11i and 12.  We have identified a number of issues with JRE 1.6.0_18.  If you haven't already upgraded your end-users to JRE 1.6.0_18, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).

Due to a regression in JRE 1.6.0_18 (6u18), the following Oracle Forms-based features may fail when running Oracle E-Business Suite through Internet Explorer;
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form in a new window from forms.
  • Opening an Applet in a new window from Oracle Forms (i.e. AHM)
The bug can cause the session cookie to be mismanaged causing a new iexplore.exe session to open on the desktop client. This affects the Oracle E-Business Suite releases in different ways:
  • If this problem occurs running Oracle E-Business Suite 11i a new login page is rendered rather than the correct window or functionality
  • If this problem occurs running Oracle E-Business Suite Release 12 the window opens with the following error:
fndgfm.jsp error : The current session is invalid. Unable to proceed without a valid session.
This issue is particularly prevalent for users running Internet Explorer 6 or 7.  These issues do not reproduce on all desktop client/Oracle E-Business Suite environment combinations, even from the same desktop client. 

Temporary Workaround for JRE 1.6.0_18 Issues

Users may still upgrade to JRE 1.6.0_18 (6u18) or later if required, for example if needing a critical fix from this or a later release of the plug-in.

The only workaround for affected users is to turn off Next-Generation Java from the 'Java Control Panel':
  1. Navigate to: Start > Control Panel > Java > Advanced > Java Plug-in 
  2. De-select the option "Enable the next-generation Java Plug-in (requires browser restart)" 
This issue is being investigated through Sun bug 6927268 - 'ShowDocument calls results in new iexplorer process'.

References
Related Articles

Thursday Oct 22, 2009

Interim Update #2: Certifying Windows 7 with Oracle E-Business Suite

windos7_logo2.png
[Dec 16, 2009 Update:  Windows 7 is now certified with the E-Business Suite; see this article]

This is the second of a series of regular updates on our Windows 7 certification projects for the E-Business Suite. 

Microsoft Windows 7 was officially released today.  Here's a recap of our plans for certifying the Oracle E-Business Suite with Microsoft's latest operating system. As always, the answers to these questions may change as we move through the certification cycle. You're welcome to monitor or subscribe to this blog for later updates. 

Our Progress on Windows 7

We're certifying Windows 7 with the E-Business Suite right now.  We've already tested several of the Win7 betas and release candidates, and those tests have gone very smoothly.  At this point, E-Business Suite product teams need to complete their certification tests with Windows 7 desktop clients.  Once those tests are completed, we'll release our certification.

For the usual reasons that regular readers could have predicted, I can't share any specific schedules or date estimates here. I can provide an interim update on the following Win7 questions:
  1. Which EBS releases will be certified with Windows 7?
  2. Which browsers will be certified?
  3. Will Oracle JInitiator be certified for EBS on Windows 7?
  4. Which Windows 7 editions will be certified?
  5. What about Windows 7E?
  6. What about Windows XP Mode?
1. Which EBS Releases Will Be Certified with Windows 7?

We plan on certifying the following Oracle E-Business Suite release with Windows 7:
  • EBS 11i version 11.5.10.2
  • EBS 12.0.4 and and higher
2. Which Browsers Will Be Certified?

We plan on certifying the following browsers with the E-Business Suite on Windows 7:
  • Internet Explorer 8
  • Firefox 3.5
3. Will Oracle JInitiator Be Certified for EBS on Windows 7?

No.  Oracle JInitiator is no longer supported for E-Business Suite customers.

Oracle JInitiator 1.1.8 was desupported in December 2008, and Oracle JInitiator 1.3 was desupported for EBS customers in July 2009.  For more information about JInitiator desupport and switching your EBS end-users from JInitiator to the Sun JRE, see:
We plan to certify only the native Sun Java Runtime Engine (JRE) with Windows 7.  We have no plans to certify Oracle JInitiator with Windows 7. 

4. Which Windows 7 Editions Will Be Certified?


We plan to test E-Business Suite compatibility against Windows 7 Professional Edition with the E-Business Suite.  We fully expect that other Win7 editions will work, but we have no current plans to explicitly test the Starter, Home Basic, Home Premium, Ultimate, or Enterprise Editions with the E-Business Suite.

5. What About Windows 7E?

Microsoft has changed its plans for Windows 7E since I published our first interim update on this certification.  At present, it appears that Microsoft has no plans to release a special version of Windows 7 for Europe.  Debate around default browser selection screens for Europe continues, so we'll continue to monitor this.

If Microsoft's plans change, and a European variant is released, our current plans are to certify the generic edition of Windows 7 with the E-Business Suite and the browsers listed above. 

6. What About Windows XP Mode?

Microsoft indicates that end-users will be able to run Windows XP in a virtualized environment running via Windows Virtual PC on a Win7 desktop client.  This will presumably be functionally-equivalent to running Windows XP natively.

We have no plans to conduct separate EBS certification efforts for WinXP+Virtual PC images running on Win7 clients.

What Are Your Organization's Plans for Windows 7?

Anecdotal reports from some EBS customers seem to suggest that your plans for Windows 7 will parallel that of Windows Vista:  namely, that new PCs that arrive with Windows 7 will either stay that way or will be downgraded to WinXP for the short term.  I have heard of a few customers with plans to deploy widespread Win7 upgrades across the enterprise, but these customers seem to be in the minority so far.

I'd be very interested in hearing your plans for rolling out Windows 7 in your organization.  Feel free to post a comment here or drop me an email with more details about your deployment plans.

Related Articles

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

Search

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