Friday Jul 24, 2015

Quarterly EBS Upgrade Recommendations: July 2015 Edition

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

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

You can research these yourself using this Note:

Upgrade Recommendations for July 2015

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

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

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

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

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

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

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

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

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

  10. All Windows desktop users should migrate from older Java releases (including JInitiator) to JRE 1.6.0_101 or later 1.6 updates or JRE 1.7.0_85 or later 1.7 updates or JRE 1.8.0_51 or later 1.8 updates.

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

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

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

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

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

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

Related Articles

Wednesday Jul 15, 2015

JRE 1.8.0_51 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

What's new in this release?

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

For further information and bug fix details see Java CPU and PSU Releases Explained.

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

No.

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

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

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

References

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


JRE 1.7.0_85 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in this release?

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

For further information and bug fix details see Java CPU and PSU Releases Explained.

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.6.0_101 Certified with Oracle E-Business Suite

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

New EBS installation scripts

This JRE release is the first with a 3-digit Java version. Installing this in your EBS 11i and 12.x environments will require new installation scripts.  See the documentation listed in the 'References' section for more detail.

32-bit and 64-bit versions certified

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here: Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package.

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Tuesday Jun 16, 2015

DSTv24 Timezone Patches Available for E-Business Suite

Hourglass iconIf your E-Business Suite Release environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in September 2014 and released as DSTv23.

DSTv24 is now available and certified with Oracle E-Business Suite Release 12.2, 12.1, and 11.5.10.2. The DSTv24 update includes the timezone information from the IANA tzdata 2015d.  It is cumulative: it includes all previous Oracle DST updates. 

Is Your Apps Environment Affected?

When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

  • Your Oracle E-Business Suite environment is located in the affected country or region OR
  • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

The latest DSTv24 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv24 includes changes to the following timezones since the DSTv23 release:

  • Africa/Cairo,
  • America/Cancun,
  • America/Grand_Turk,
  • America/Santiago,
  • Antarctica/Palmer,
  • Asia/Dacca,
  • Asia/Hovd,
  • Asia/Ulaanbaatar,
  • Asia/Gaza,
  • Asia/Choibalsan,
  • Asia/Hebron,
  • Europe/Minsk,
  • Pacific/Easter,
  • Pacific/Fiji,
  • Egypt,
  • Jamaica,
  • Chile/Continental,
  • Asia/Dhaka,
  • Asia/Ulan_Bator,
  • Chile/EasterIsland.

What Patches Are Required?

In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

Proactive backports of DST upgrade patches to all Oracle E-Business Suite tiers and platforms are not created and supplied by default. If you need this DST release and an appropriate patch is not currently available, raise a service request through support providing a business case with your version requirements.

We've published the following Notes which identify the various components in your E-Business Suite environment that may need DST patches:

Wednesday Apr 22, 2015

Quarterly EBS Upgrade Recommendations: April 2015 Edition

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

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

You can research these yourself using this Note:

Upgrade Recommendations for April 2015

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Thursday Apr 16, 2015

JRE 1.8.0_45 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

No.

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

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

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

References

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


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

Java logo

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in this release?

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

Worried about the 'mismanaged session cookie' issue?

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

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.6.0_95 Certified with Oracle E-Business Suite

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in in this Java release?

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

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Wednesday Mar 04, 2015

JRE 1.8.0_40 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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


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

No.

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

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

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

References

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


Wednesday Jan 21, 2015

JRE 1.8.0_31 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

No.

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

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

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

References

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


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

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

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

What's new in this release?

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

Worried about the 'mismanaged session cookie' issue?

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

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

 

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.6.0_91 Certified with Oracle E-Business Suite

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

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

What's new in in this Java release?

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

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Tuesday Dec 30, 2014

Java Auto-Update Upgrades JRE 7 to 8 in January 2015

This notice is posted on the Java SE Download site:

JRE 7 Auto Update Notice screenshot

If your users are running JRE 7 with auto-update enabled, they will be automatically upgraded to JRE 8 with the January 2015 CPU release on January 20, 2015.  This affects Windows and Mac desktops. 

For more details, see:

Will do EBS sysadmins need to do?

If you do not have Auto-Update enabled on your end-users' desktops, you don't need to do anything.

JRE 8 is certified with all current EBS releases: EBS 11i, 12.0, 12.1, and 12.2.  If you have Auto-Update enabled, you need to apply server-side patches to make your EBS environment compatible with JRE 8.  For details, see:  

See that article for answers to common questions, including:

  • Where are the official patch requirements documented?
  • What are the known issues with JRE 8 and EBS?
  • Does JRE 8 work with Discoverer 11g?
  • What are the implications for EBS users of Java 6 and 7 End of Public Updates?
  • Will EBS users be forced to upgrade to JRE 8?
  • What are the impacts of enabling JRE Auto-Update?
  • Can multiple JRE releases coexist on the same desktop?
  • What do Mac users need?
  • Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

Related Articles

Monday Dec 29, 2014

Quarterly EBS Upgrade Recommendations: December 2014 Edition

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

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

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

You can research these yourself using this Note:

Upgrade Recommendations for December 2014

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Thursday Dec 04, 2014

JRE Support Ends Earlier than JDK Support

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

Screenshot from Java Lifetime Support Policy document JDK JRE different dates

These dates are published here:

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

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

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

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

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

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

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

Related Articles

Friday Nov 14, 2014

Java JRE 8 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

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

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

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

    No.

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

    Impact of enabling JRE Auto-Update

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

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

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

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

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

    Coexistence of multiple JRE releases Windows desktops

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

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

    What do Mac users need?

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

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

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

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

    No.

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

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

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

    References

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


    Thursday Oct 16, 2014

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

    Java logo

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in this release?

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

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

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

    32-bit and 64-bit versions certified

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

    Java JRE 1.6.0_85 Certified with Oracle E-Business Suite

    Java logo

    The latest Java Runtime Environment 1.6.0_85 (a.k.a. JRE 6u81-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?

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

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

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

    32-bit and 64-bit versions certified

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

    The latest updates to that page (as of Sept. 19, 2012) state (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

    Tuesday Sep 16, 2014

    DSTv23 Timezone Patches Available for E-Business Suite 12

    Hourglass iconIf your E-Business Suite Release 12.x environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in June 2014 and released as DSTv22.

    DSTv23 is now available and certified with Oracle E-Business Suite Release 12.x. The DSTv23 update includes the timezone information from the IANA tzdata 2014f and includes Russia's reintroduction of "winter time" when the clocks will be turned back one hour on October 26, 2014.  It is cumulative: it includes all previous Oracle DST updates. 

    Is Your Apps Environment Affected?

    When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

    • Your Oracle E-Business Suite environment is located in the affected country or region OR
    • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

    The latest DSTv23 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv23 includes changes to the following timezones since the DSTv22 release:

    • Africa/Cairo, 
    • Africa/Casablanca, 
    • Africa/El_Aaiun, 
    • Asia/Taipei, 
    • Asia/Yekaterinburg, 
    • Asia/Omsk, 
    • Asia/Novosibirsk , 
    • Asia/Krasnoyarsk, 
    • Asia/Irkutsk,  
    • Asia/Yakutsk, 
    • Asia/Vladivostok, 
    • Asia/Magadan, 
    • Asia/Sakhalin, 
    • Europe/Kaliningrad, 
    • Europe/Moscow, 
    • Europe/Simferopol, 
    • Europe/Volgograd, 
    • Egypt, 
    • ROC, 
    • W-SU.

    What Patches Are Required?

    In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

    We've published the following Notes which identify the various components in your E-Business Suite environment that may need DST patches:

    Monday Sep 15, 2014

    Preventing "Java was blocked" IE Warnings with Oracle EBS

    Microsoft Internet Explorer (IE) started warning users about out-of-date ActiveX controls running through any security zone except the 'Local intranet' or the 'Trusted sites' zones when using IE 8 or later. Attempts to run any Java content from your desktop using older JRE releases -- releases prior to the latest Critical Patch Updates (CPU) on any JRE codeline -- through any other zone now result in a warning message. This may prevent you from accessing Java-based or Forms-based content within Oracle E-Business Suite.

    IE will not block functionality for end-users who meet any of these conditions:

    • Are running EBS through the browsers "Local Intranet" or "Trusted sites" zones
    • Have the latest Java Runtime Environment (JRE) Critical Patch Update (CPU) release on Java 6 or 7

    IE will block end-users whose desktops meet all of the following conditions:

    • Users are running the E-Business Suite in the the "Internet" zone
    • Users do not have latest Java Runtime Environment (JRE) Critical Patch Update (CPU) release on Java 6 or 7

    Affected end-users will see the following warning:

    Java(TM) was blocked because it is out of date and needs to be updated

    How do I prevent this Issue?

    OPTION 1

    Follow our documented recommendations to run Oracle E-Business Suite through the "Trusted sites" zone. 

    See the "Recommended Internet Explorer Browser Settings" section within:

    OPTION 2

    Follow Microsoft's workaround to turn this feature off:

    OPTION 3

    Upgrade to the latest JRE release. See:

    Related Articles

    Wednesday Sep 10, 2014

    Invoking JAVA APIs via REST in EBS 12.2

    Oracle E-Business Suite Integrated SOA Gateway (ISG) introduced PL/SQL as RESTful webservices in EBS 12.2.3.  EBS 12.2.4 expands that functionality further, allowing Plain Old Java Objects (POJO) / Java Beans to be published as RESTful web services using ISG. This new Java API REST service provides support for both GET and POST verbs.

    What is POJO?

    POJO stands for Plain Old Java Object. It is a Java object which does not implement any framework-specific interfaces such as Spring, Hibernate, JDO, or EJB. POJOs allow applications to be decoupled from infrastructure frameworks.

    Prerequisites for Using Custom Java API as REST service in ISG

    The following tasks needs to be performed to use custom Java API as REST services:

    Custom Java API steps

    Custom Java APIs are configured and deployed on the application tier.  For more information, see Section 5, "Deploying Custom Application Tier Objects" in this document:

    Java REST API Lifecycle

    Java REST API lifecycle

    Java API REST services follow the same lifecycle as PLSQL rest services. Once the custom classes and ILDT loader files are uploaded, you are ready to use Java APIs as REST services from the Integration Repository.

    You can find the newly uploaded Java API in the Integration Repository using the new “Java Bean Services” Interface Subtype :

    Java Bean Services Interface Subtype

    Select GET, POST, or both based on your requirements. Provide a service alias and deploy the service.

    Voila! the service is ready to be used.

    Java Web Service Details

    What’s more in a Java API rest services?

    Java API REST services support GET and POST methods. GET requests can be invoked as Uniform Resource Identifiers (URI) from any browser.  The invocation process is simple, user-friendly and quick.

    URI Format:

    http://<host>:<port>/webservices/rest/<Service Alias>/<rest method name>/[<key-param>]?queryParam=paramValue[&....

    Example :

    Get all employees reporting “Mark ”, location “CA”

    http://<host:port>/webservices/rest/empSvc/getEmployees/Mark/?location=CA

    Key Features of GET

    • GET requests can be cached
    • GET requests can be bookmarked
    • GET requests remain in the browser history

    GET requests should not be used when dealing with sensitive data.

    Related Articles

    Wednesday Aug 13, 2014

    Quarterly E-Business Suite Upgrade Recommendations: August 2014 Edition

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

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

    Upgrade Recommendations for August 2014

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

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

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

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

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

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

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

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

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

    10. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_81 or later 1.6 updates or JRE 1.7.0_67 or later 1.7 updates.

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

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

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

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

    Related Articles

    Tuesday Aug 05, 2014

    JRE 1.7.0_67 Certified with Oracle E-Business Suite

    Java logo

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

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in this release?

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

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

    32-bit and 64-bit versions certified

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

    Tuesday Jul 15, 2014

    JRE 1.7.0_65 Certified with Oracle E-Business Suite

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in this release?

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

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

    32-bit and 64-bit versions certified

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

    Java JRE 1.6.0_81 Certified with Oracle E-Business Suite

    Java logo

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in in this Java release?

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

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

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

    32-bit and 64-bit versions certified

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

    Thursday Jun 19, 2014

    Latest DSTv22 Timezone Patches Available for E-Business Suite 12

    Hourglass iconIf your E-Business Suite Release 12.0 or 12.1 environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in July 2013 and released as DSTv20.

    DSTv22 is now available and certified with Oracle E-Business Suite Release 12.0 and 12.1. The DSTv22 update includes the timezone information from the IANA tzdata 2014c and is cumulative: it includes all previous Oracle DST updates. 

    This update also includes new DST timezone definitions for Egypt for May and August 2014.

    Is Your Apps Environment Affected?

    When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

    • Your Oracle E-Business Suite environment is located in the affected country or region OR
    • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

    The latest DSTv22 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv22 includes changes to the following timezones since the DSTv20 release:

    •  Africa/Cairo,
    • Africa/Tripoli,
    • Africa/Casablanca,
    • Africa/El_Aaiun,
    • America/Havana,
    • America/Araguaina,
    • America/Porto_Acre,
    • America/Eirunepe,
    • Asia/Jerusalem,
    • Asia/Amman,
    • Asia/Gaza,
    • Asia/Hebron,
    • Europe/Istanbul,
    • Europe/Kiev,
    • Europe/Simferopol,
    • Pacific/Fiji,
    • Egypt,
    • Libya,
    • Cuba,
    • Brazil/Acre,
    • Asia/Tel_Aviv,
    • Turkey,
    • America/Rio_Branco,
    • Israel,
    • Asia/Istanbul

    What Patches Are Required?

    In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

    We've published the following Notes which identify the various components in your E-Business Suite environment that may need DST patches:

    Wednesday Jun 04, 2014

    Java JRE 1.7.0_60 Certified with Oracle E-Business Suite

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in JRE 1.7.0_60?

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

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

    32-bit and 64-bit versions certified

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

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

    Search

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