Wednesday Apr 23, 2014

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

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

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

Our current plans for IE 11

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

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

When will IE 11 be certified?

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

Postpone IE 11 rollouts until certified with EBS

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

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

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

Related Articles

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


Friday Apr 18, 2014

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

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

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

What can EBS customers expect after April 2014?

After Microsoft desupports WinXP and Office 2003 in April 2014:

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

What should EBS users do?

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

What about EBS desktop-based client/server tools?

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

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

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

For complete details, see:

Pending Desktop Certifications 

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

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

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

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

Related Articles


Thursday Apr 17, 2014

Best Practices for Deploying EBS 12.2 on Oracle Database Appliance

Oracle Database Appliance ODA imageThe Oracle Database Appliance (ODA) is an engineered system that combines Oracle software with server, storage, and networking hardware.  The E-Business Suite's application tier and database tier components may be deployed on the Oracle Database Appliance.

Oracle Database Appliance offers the option to deploy highly available Oracle Databases in a bare metal environment or to deploy both Oracle Databases and the Application Tier in virtualized environments within the appliance.

A new whitepaper describes how to use EBS + ODA together:

This white paper describes how to deploy Oracle E-Business Suite 12.2 database and application tiers on Oracle Database Appliance Virtualized Platform 2.8 (and later) using preconfigured Oracle E-Business Suite VM templates.

Each Oracle E-Business Suite deployment consists of two Oracle VM templates:

  1. Database image template
  2. Primary application tier template.
These templates deliver the complete EBS software technology stack.  You have the option of using a preconfigured Vision demonstration environment with sample data or a fresh install database for production environments.

The procedures in this paper are fully supported for production use.

Related Articles


Wednesday Apr 16, 2014

Critical Patch Update for April 2014 Now Available

The  Critical Patch Update (CPU) for April 2014 was released on April 15, 2014.  Oracle strongly recommends applying the patches as soon as possible.

The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

The Critical Patch Update Advisory is available at the following location:

The next four Critical Patch Update release dates are:

  • July 15, 2014
  • October 14, 2014
  • January 13, 2015
  • April 14, 2015
E-Business Suite Releases 11i and 12 Reference

Tuesday Apr 15, 2014

Java JRE 1.6.0_75 Certified with Oracle E-Business Suite

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in in this Java release?

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.7.0_55 Certified with Oracle E-Business Suite

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in JRE 1.7.0_55?

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Quarterly E-Business Suite Upgrade Recommendations: April 2014 Edition

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

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

Upgrade Recommendations for April 2014

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Thursday Apr 03, 2014

Understanding and Managing Licensing Options in Oracle E-Business Suite

License Manager is a utility that registers additional products, country-specific functionalities, and languages for your Oracle E-Business Suite system. Application products that you use after the initial installation must be registered as active in order to be included in various system maintenance tasks.

We receive a lot of questions on this particular area:

  • How does the activation process work?
  • Which tables are involved?
  • How are dependencies between products calculated?
  • What if a product is activated by mistake?


We are pleased to announce a new document that answers all these questions with extensive coverage on how License Manager works:

  • Understanding and Managing Licensing Options in Oracle E-Business Suite (Note 1639705.1)
Related Documents

Monday Mar 17, 2014

Webcast Mar. 18: Advanced Testing & Management of EBS with Oracle Enterprise Manager

Our Oracle Enterprise Manager team has arranged a webcast in which Aramark will discuss their experiences using Oracle Enterprise Manager to manage their E-Business Suite environments.

They will be discussing how they use the Oracle E-Business Suite Plug-in for Oracle Enterprise Manager Grid Control 12c as part of their EBS administration processes. 

This webcast is tomorrow:

EM12c AMP 12.1.0.2 screenshot

Related Articles


Friday Feb 14, 2014

Oracle Database 11.2.0.4 Certified with EBS 11i on Additional HP Platforms

HP logoAs a follow up to the prior announcements on November 20th 2013, Oracle Database 11g Release 2 (11.2.0.4) is now certified with Oracle E-Business Suite Release 11i (11.5.10.2 + ATG PF.H RUP 6 and higher) on the following additional platforms:

  • HP-UX PA-RISC (64-bit) (11.31)
  • HP-UX Itanium (11.31)1

1 : This is a 'database tier only' or 'split tier configuration' certification where the application tier must be on a fully certified E-Business Suite platform.

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

References

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

Wednesday Feb 12, 2014

Oracle Access Manager 11.1.2.2 Certified with Oracle E-Business Suite

I am happy to announce that Oracle Access Manager 11gR2 Patchset 2 (11.1.2.2.0) is now certified with Oracle E-Business Suite Release 11i (11.5.10.2) and 12 (12.0.6, 12.1.1+, 12.2.2+).  If you are implementing single sign-on for the first time, or are an existing Oracle Access Manager user, you may integrate with Oracle Access Manager 11gR2 using Oracle Access Manager WebGate and Oracle E-Business Suite AccessGate.

Choosing the Right Integration

Our previously published blog article and support note with single sign-on recommended and certified integration paths has been updated to include Oracle Access Manager 11gR2PS2:

References

You may refer to the following My Oracle Support Knowledge Documents for additional details regarding certified architectures and versions:

    Related Articles

    Tuesday Jan 21, 2014

    Support Implications for Your EBS Customizations

    I've published this guidance in various articles before but it never hurts to consolidate it here for new readers.

    You may choose to:

    • Modify or extend the E-Business Suite code that we ship
    • Add new database objects or modify existing database objects that we ship
    • Modify our standard EBS database partitioning schemes
    • Introduce various forms of third-party virtualization technologies for any of the E-Business Suite's three tiers -- the database tier, the application server tier, or the desktop tier
    • Use third-party tools to modify your database directly
    • Integrate third-party software with your EBS environment, say, for reporting purposes, or to obtain additional industry-specific functionality
    • Use third-party tools to manage or configure your EBS environment.
    Oracle generally considers all of these activities to be some form of customization.  This is not a complete list. Generally speaking, if you have introduced something new into your environment that we haven't tested, we cannot take responsibility for it, so we consider it to be a customization.

    Where these activities fall on a risk spectrum depends on their invasiveness.  The more invasive a customization is, the greater its potential risk.  Oracle generally recommends against invasive customizations.

    Oracle's official policy on handling customizations is detailed here:

    The support implications boil down to this:

    • Issues that are isolated to the E-Business Suite will be investigated by E-Business Suite Development.
    • Issues that are isolated to your customizations or third-party tools should be directed to the third-party vendor.
    • E-Business Suite Development will provide E-Business Suite Development patches for issues that can be reproduced in environments built using E-Business Suite documented procedures and tools.
    • If the third-party vendor cannot resolve issues isolated to their tools, you should restore from a backup and revert to using Oracle’s documented tools and procedures.

    Related Articles

    Wednesday Jan 15, 2014

    Java JRE 1.6.0_71 Certified with Oracle E-Business Suite

    Java logo

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

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in in this Java release?

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

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

    32-bit and 64-bit versions certified

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

      Related Articles

      Java JRE 1.7.0_51 Certified with Oracle E-Business Suite

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

      Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

      New Features in JRE 1.7.0_51

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

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

      Exception Site List

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

      32-bit and 64-bit versions certified

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

      Where are the official patch requirements documented?

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

      For EBS 11i:

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

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

      Worried about the 'mismanaged session cookie' issue?

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

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

      Implications of Java 6 End of Public Updates for EBS Users

      The Support Roadmap for Oracle Java is published here:

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

      Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

      Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

      Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

      What do Mac users need?

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

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

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

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

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

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

      References

      Related Articles

      Tuesday Jan 14, 2014

      Critical Patch Update for January 2014 Now Available

      The  Critical Patch Update (CPU) for January 2014 was released on January 14, 2014.  Oracle strongly recommends applying the patches as soon as possible.

      The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

      Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

      Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

      The Critical Patch Update Advisory is available at the following location:

      The next four Critical Patch Update release dates are:

      • April 15, 2014
      • July 15, 2014
      • October 14, 2014
      • January 13, 2015
      E-Business Suite Releases 11i and 12 Reference

      Monday Jan 06, 2014

      ATG Live Webcast Jan. 8th: Advanced EBS Management using Enterprise Manager

      I'm pleased to announce our first webcast of the year:

      • Oracle Enterprise Manager: Advanced Management of Oracle E-Business Suite
        Wednesday, January 8, 2014
        10:00 AM Pacific Standard Time

      You will receive links to the live webcast after you register here:

      Angelo Rosado and Vasu Rao, EBS Product Management, will provide an update on the latest Application Management Pack features for managing E-Business Suite environments with Oracle Enterprise Manager 12c.  They will cover AMP features such as:

      • Online Patching with E-Business Suite 12.2
      • Customization management 
      • Cloning
      • System monitoring
      • Configuration and compliance management 

      They will also provide a glimpse of the product roadmap, and you will have the opportunity to ask questions during the live webcast.

      EM12c AMP 12.1.0.2 screenshot

      Related Articles


      Friday Jan 03, 2014

      Which JDeveloper Version Works With Your EBS Release?

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

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

      This Note lists the JDeveloper with OA Extension updates for EBS 11i, 12.0, 12.1, and 12.2:

      Related Articles

      Thursday Nov 21, 2013

      Can You Use Third-Party Tools to Modify Your EBS Database?

      In short: no. But it's possible to give a more-nuanced answer for one scenario where they might be useful.

      Our official policy on direct modifications to EBS databases

      Every Oracle E-Business Suite manual in our documentation library contains this warning (emphasis added):

      Do Not Use Database Tools to Modify Oracle E-Business Suite Data

      Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed.

      Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.

      Because Oracle E-Business Suite tables are interrelated, any change you make using an Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite.

      When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.

      Can data corruption really occur?

      Yes. Even if you're using SQL*Plus, which is obviously not a third-party tool, you run the risk of corrupting your EBS database.  This is true for all tools that modify an EBS database directly.

      What about third-party data archiving and purging tools?

      Some third-party tools reduce the size of EBS databases by deleting data.  Some use database links, aliases, and other approaches to separate older data into other databases.

      These tools can be useful for reducing the size of a production database for development purposes.  It generally doesn't matter if these smaller sandbox or testbed databases have referential integrity violations.

      You should never use these tools to reduce the size of your production EBS database.

      Why are these tools dangerous?  They claim that they're safe.

      The E-Business Suite data model is partially documented here:

      Unfortunately, that manual is not comprehensive. Third-party tools that rely on it to determine data relationships in the EBS data model will miss important dependencies.

      EBS data dependencies are implemented through seed data, business logic, and other undocumented areas.  These hidden and undocumented dependencies mean that only current EBS Development staff are qualified to determine whether data can be safely removed. 

      It is certain that third-party tools will violate EBS database referential integrity in some manner.  This is true even for third-party tools that are produced by people who used to work for Oracle EBS development.  EBS products continue to evolve and new dependencies are introduced on a regular basis.  These new dependencies may be undocumented.

      What are the support implications of using third-party tools?

      Oracle regards the use of third-party database tools to be customizations. Oracle's official policy is detailed here:

      You should also review the support implications for using third-party tools.  They boil down to this:

      • Issues that are isolated to the E-Business Suite will be investigated by E-Business Suite Development.
      • Issues that are isolated to third-party tools should be directed to the third-party vendor.
      • E-Business Suite Development will provide E-Business Suite Development patches for issues that can be reproduced in environments built using E-Business Suite documented procedures and tools.
      • If the third-party vendor cannot resolve issues isolated to their tools, you should restore from a backup and revert to using Oracle’s documented tools and procedures.

      Related Articles


      Tuesday Nov 19, 2013

      Quarterly E-Business Suite Upgrade Recommendations: November 2013 Edition

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

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

      Upgrade Recommendations for November 2013

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

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

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

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

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

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

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

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

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

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

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

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

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

        Related Articles

        Thursday Nov 14, 2013

        Firefox ESR 24 Certified with Oracle E-Business Suite

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

        What is Mozilla Firefox ESR?

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

        What does the Mozilla Firefox ESR life cycle look like?

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

        Firefox ESR schedule

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

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

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

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

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

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

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

        EBS patching policy for Firefox compatibility issues

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

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

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

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

        E-Business Suite Prerequisites

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

        EBS 12.2.x:

        • Base release

        Certified desktop operating systems

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

        References

        Your feedback is welcome

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

        Related Articles

        Wednesday Oct 30, 2013

        Getting Optimal Performance from Oracle E-Business Suite

        Performance tuning and optimization in E-Business Suite environments can involve many different components and diagnostic tools.  Samer Barakat, Senior Architect in our Applications Performance group, held an OpenWorld 2013 session that covered:

        • Performance triage, analysis and diagnostic tools
        • Optimizing the E-Business Suite application tier, including Concurrent Manager
        • Optimizing the E-Business Suite database tier
        • Optimizing the E-Business Suite on Real Application Clusters (RAC)
        • E-Business Suite on engineered systems, including Exadata and Exalogic
        • Optimizing E-Business Suite data management, including archiving and purging 

        Table showing workload management strategy for Concurrent Manager

        The Applications Performance group works with the world's largest E-Business Suite customers to isolate and resolve performance bottlenecks. This team has helped tune the E-Business Suite environments of world's largest companies to handle staggering amounts of transactional volume in multi-terabyte databases.  This group also publishes our official Oracle Apps benchmarks, white papers, and performance metrics.

        This is an essential set of tips and techniques that all EBS sysadmins and DBAs can use to improve the performance of their environments:

        OpenWorld 2013 presentations are only available for approximately six months -- until ~March 2014.  Download this one while it's still available.

        Related Articles

        Wednesday Oct 23, 2013

        New Whitepaper: Best Practices for Gathering EBS Database Statistics

        Most Oracle Applications DBAs and E-Business Suite users understand the importance of accurate database statistics.  Missing, stale or skewed statistics can adversely affect performance. 

        Oracle E-Business Suite statistics should only be gathered using FND_STATS or the Gather Statistics concurrent request. Gathering statistics with DBMS_STATS or the desupported ANALYZE command may result in suboptimal executions plans for E-Business Suite.

        Our E-Business Suite Performance Team has been busy implementing and testing new features for gathering statistics using FND_STATS in Oracle E-Business Suite databases.  The new features and guidelines for when and how to gather statistics are published in the following whitepaper:

        The new white paper, written by Deepak Bhatnagar, Mohammed Saleem, and Andy Tremayne, details the following options for gathering statistics using FND_STATS and the Gather Statistics concurrent request::

        • History Mode - backup existing statistics prior to gather new statistics
        • GATHER_AUTO Option - gather statistics for tables based upon % change
        • Histograms - collect statistics for histograms
        • AUTO Sampling - use the new FND_STATS feature that supports the AUTO option for using AUTO sample size
        • Extended Statistics - use the new FND_STATS feature that supports the creation of column groups and automatic statistics collection on the column groups when table statistics are gathered
        • Incremental Statistics - gather incremental statistics for partitioned tables

        The new white paper also includes examples and performance test cases for the following:

        • Extended Optimizer Statistics
        • Incremental Statistics Gathering
        • Concurrent Statistics Gathering

        This white paper includes details about the standalone Oracle E-Business Suite Release 11i and 12 patches that are required to take advantage of this new functionality.

        Your feedback is welcome

        We would be very interested in hearing about your experiences with these new options for gathering statistics.  Please feel free to post your comments here or drop us a line privately.

        Related Oracle OpenWorld 2013 Session

        Related My Oracle Support Notes

        Non-EBS Related Blogs, White Papers and My Oracle Support Notes 


        Friday Oct 18, 2013

        Sign E-Business Suite JAR Files Now

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

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

        More information about Java security is available here:

        Getting help

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

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


        Thursday Oct 17, 2013

        Java JRE 1.7.0_45 Certified with Oracle E-Business Suite

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

        Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

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

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

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

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

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

        Where are the official patch requirements documented?

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

        For EBS 11i:

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

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

        Worried about the 'mismanaged session cookie' issue?

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

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

        Implications of Java 6 End of Public Updates for EBS Users

        The Support Roadmap for Oracle Java is published here:

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

        Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

        Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

        Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

        What do Mac users need?

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

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

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

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

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

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

        References

        Related Articles

        Java JRE 1.6.0_65 Certified with Oracle E-Business Suite

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

        Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

        What's new in in this Java release?

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

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

        32-bit and 64-bit versions certified

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

        32-bit JREs are certified on:

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

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

        Worried about the 'mismanaged session cookie' issue?

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

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

        Implications of Java 6 End of Public Updates for EBS Users

        The Support Roadmap for Oracle Java is published here:

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

        Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

          Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

          Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

          What do Mac users need?

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

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

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

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

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

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

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

          References

          Related Articles

          Wednesday Oct 16, 2013

          Should You Upgrade to E-Business Suite 12.1.3 or 12.2?

          Title page of EBS 12.1.3 vs. 12.2 whitepaperAre you wondering whether to plan your next upgrade to E-Business Suite 12.1.3 or 12.2?  This guidance should help:

           This short white paper lists the major criteria:

          When Should You Choose 12.1?

          Consider targeting 12.1 if any of the following circumstances applies to your organization:

          • You prefer to target a release on which Oracle has thousands of live customers.
          • You would like to stay on 12.1 for 3-5 years before upgrading to 12.2.
          • You need to move from a release below 11.5.10 with no direct upgrade to 12.2.

          When Should You Choose 12.2?

          Consider targeting 12.2 if any of the following circumstances applies to your organization:

          • You need the high availability provided by Online Patching.
          • You want the functional enhancements that are in 12.2.
          • You prefer to invest in a single project to upgrade directly to 12.2.

          It discusses those considerations in detail and provides links to other resources that you might use to weigh the pros and cons of each release.

          Related Articles


          Tuesday Oct 15, 2013

          Critical Patch Update for October 2013 Now Available

          The  Critical Patch Update (CPU) for October 2013 was released on October 15, 2013. Oracle strongly recommends applying the patches as soon as possible.

          The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

          Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

          Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

          The Critical Patch Update Advisory is available at the following location:

          The next four Critical Patch Update release dates are:

          • January 14, 2014
          • April 15, 2014
          • July 15, 2014
          • October 14, 2013
          E-Business Suite Releases 11i and 12 Reference

          Monday Oct 14, 2013

          Fusion Middleware 11gR1 Support Dates Updated

          Support dates for Premier and Extended Support for Oracle Fusion Middleware 11gR1 products were recently extended.  The new dates allow more time for current FMW 11gR1 users to upgrade to FMW 12c.  These new dates are published here:
          These changes are explained in more detail here:
          Impact on E-Business Suite Users

          These changes do not affect support dates for EBS 11.5.10.2, 12.0, 12.1, or 12.2.  Fusion Middleware components used in the internal application-tier technology stack for these EBS releases include Oracle HTTP Server, Forms & Reports, Oracle Containers for Java (OC4J), and others.  Support dates for the E-Business Suite for these internal components override the published FMW support dates.

          These changes affect EBS users who are currently running:
          • Java SE 6 (JDK and JRE)
          • Oracle WebCenter Portal 11.1.1.x
          • Oracle Business Intelligence Suite Enterprise Edition 11.1.1.x
          EBS users who have integrated their environments with the following products are not affected:

          Getting help for your questions about Fusion Middleware support dates

          We're EBS specialists on this blog.  We can only provide basic assistance with questions about FMW support dates.  You should log Service Requests against the specific Fusion Middleware products for which you have support date-related questions.

          Related Articles


          Saturday Sep 28, 2013

          E-Business Suite Support Timelines Updated at OpenWorld 2013

          [Oct. 30, 2013 Update: Corrected typo -- US Form 1099 updates are provided to 2014]

          Our release of E-Business Suite 12.2 is accompanied by changes to support timelines for previous releases.  These changes were announced at OpenWorld 2013.  They override changes announced at OpenWorld 2012.

          Latest changes to EBS Support timelines 2013

          EBS 11.5.10.2 covered by an Exception to Sustaining Support to December 31, 2015

          This provides updates during the Sustaining Support period for:

          • New fixes for Severity 1 production issues
          • Critical Patch Updates (CPU) for security-related issues
          • Legislative updates
            • US Form 1099 2013 and 2014 year-end updates
            • Payroll regulatory updates for US, Canada, UK, and Australia for each country's fiscal years ending in 2014

          Longer EBS 12.1 Premier and Extended Support timelines

          • Premier Support runs to December 31, 2016
            (Originally was to end May 2014; 31 extra months added)
          • Extended Support runs to December 31, 2019
            (Originally was to end December 2018; one extra year added)

          These changes are officially documented here:

          Table showing latest 2013 EBS Premier Extended Sustaining Support timelines windows

          What about E-Business Suite technology stack components?

          These support date extensions only cover internal EBS application tier technology stack components such as Oracle Forms and Reports, Oracle HTTP Server, Oracle JServ, Oracle Containers for Java (OC4J), and Java (JDK and JRE).

          They do not extend support dates for the Oracle Database or optional externally-integrated application tier components such as Discoverer, Oracle Single Sign-On, Oracle Access Manager, Oracle Internet Directory, or other Fusion Middleware products.

          To learn more about the interlocking EBS+techstack component support windows, see these two articles:

          Related Articles


          Friday Sep 27, 2013

          Microsoft Windows 8 Certified with Oracle E-Business Suite

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

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

          Oracle E-Business Suite 12.2 Prerequisites

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

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

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

          Use the Native JRE plug-in

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

          Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline. 

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

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

          We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

          You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops. This applies to all certified Windows desktop operating systems, including XP, Vista, 7, and 8.

          WebADI and Report Manager Users

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

          What About Windows Hyper-V?

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

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

          What about other Windows 8 editions?

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

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

          What About Earlier Versions of IE?

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

          Pending Win8 Certifications

          BiDi (Arabic and Hebrew Languages)

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

          MS Projects

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

          Client Server Products

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

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

          References

          Related Articles
          About

          Search

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