Friday Aug 09, 2013

Internet Explorer 10 Certified with Oracle E-Business Suite

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

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

EBS 12.1 Prerequisites

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

EBS 12.0 Prerequisites

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

EBS 11i Prerequisites

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

Compatibility Mode for IE 10 + EBS 12

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

JRE 1.7 is certified with EBS

There appears to be some inaccurate information lying about on the web that claims that JRE 1.7 is not certified with the E-Business Suite. 

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

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

"JInitiator version too low" errors

Some non-Oracle staff are claiming that "JInitiator version too low" errors confirm this incompatibility and lack of certification.

In fact, if you're getting a "JInitiator version too low" error, it means that you've missed applying the Forms patch required to enable JRE 1.7 compatibility. Simply apply that patch and your EBS environment is ready for JRE 1.7 clients.

References

Related Articles


Friday Jul 26, 2013

E-Business Suite Release 12.1.1 Consolidated Upgrade Patch 2 Now Available

Oracle E-Business Suite Release 12.1.1 Consolidated Upgrade Patch 2 (CUP2) is now available in My Oracle Support. This patch includes fixes and performance improvements for the scripts used to upgrade an EBS 11i environment to 12.1.1.

This patch is mandatory for customers who are upgrading to Release 12.1.1 from the following releases:

  • Oracle E-Business Suite Release 11i version 11.5.9 (base, CU1, CU2)
  • Oracle E-Business Suite Release 11i version 11.5.10 (base, CU1, CU2)

This patch includes all of the upgrade-related fixes released previously in the Consolidated Upgrade Patch 1 (CUP1, Patch 7303029) and many additional upgrade related fixes released since March 2010. 

You can download it here:



What is Oracle E-Business Suite Consolidated Upgrade Patch 2 for Release 12.1.1?

The Consolidated Upgrade Patch 2 (CUP2) for Release 12.1.1 combines critical upgrade error corrections and upgrade performance improvements from Release 11i into a consolidated suite-wide patch.

Who should use it?

Customers who are upgrading to Release 12.1.1 from Release 11.5.9 (base, CU1, CU2) or Release 11.5.10 (base, CU1, CU2) should apply Release 12.1.1 CUP2.

How does it differ from the Family Consolidated Upgrade Patch (FCUP) in Release 11i?

In Release 11i, Family Consolidated Upgrade Patches (FCUP) were the release vehicles used to ship consolidated upgrade-related patches from all products within a product family.  In R12, the term Consolidated Upgrade Patch (CUP) has been coined to ship critical upgrade error corrections and upgrade performance improvements across all the product families in Oracle E-Business suite.

How do you apply Release 12.1.1 CUP2?

For instructions on applying this patch, see the "Notes for Upgrade Customers" section in:
Can this patch be applied by customers who are upgrading to Release 12.1.1 from an earlier version of Release 12?

No.  Release 12.1.1 CUP2 is applicable only if you are upgrading your E-Business Suite Release 11i instance to Release 12.1.1.  If your Oracle E-Business Suite instance is already at Release 12 or higher (e.g. Release 12.0.4, 12.0.6), you should not apply Release 12.1.1 CUP2.

Can I apply Release 12.1.1 CUP2 to Release 12.1.1?

No.  If your environment is already at the Release 12.1.1 level, you do not need this patchset.  You should apply Release 12.1.1 CUP2 only while upgrading a Release 11i Oracle E-Business Suite instance to Release 12.1.1

Is Release 12.1.1 CUP2 mandatory for upgrading to Release 12.1.1 if I have done multiple test upgrades and am close to "Go-Live"?

If you have already performed multiple test upgrades without Release 12.1.1 CUP2 and are close to completing User Acceptance Testing prior to your actual production upgrade, it is not mandatory to apply the patch.

Oracle will continue to provide patches for Oracle E-Business Suite Release 12.1.1 environments that do not have the Release 12.1.1 CUP2 patchset.

How is the Consolidated Upgrade Patch (CUP) different from other release vehicles?

With the introduction of this patchset, there are now five types of release vehicles for the E-Business Suite:
  1. Rapid Install
  2. Maintenance Pack
  3. Product Family Release Update Pack
  4. E-Business Suite Release Update Pack
  5. Consolidated Upgrade Patch
Rapid Install

With Rapid Install (RI), you can install a fully configured Oracle E-Business suite system, lay down the file system and configure server processes for an upgraded system, or install a new database tier or application tier technology stack.

Release 12 Rapid Install versions are
  • Release 12.0.0
  • Release 12.0.4
  • Release 12.1.1
Maintenance Pack

A Maintenance Pack (MP) is an aggregation of patches for all products in Oracle E-Business Suite. It is a feature-rich release which combines new functionalities along with error corrections, statutory/regulatory updates, and functionality enhancements, etc.

The Release 12.1.1 Maintenance Pack can be used to upgrade an existing Oracle E-Business Suite Release 12.0.x environment to Release 12.1.1

Product Family Release Update Pack

Product Family Release Update Pack (RUP) is an aggregation of patches on a given codeline created for all products in a specific product family for a specific point release. RUPs are generally cumulative in nature.

Examples of Product Family Release Update Packs released in Release 12.0:
  • R12.ATG_PF.A.Delta.4
  • R12.FIN_PF.A.Delta.5
  • R12.ATG_PF.A.Delta.6
  • R12.HR_PF.A.Delta.7
Examples of Product Family Release Update Packs released in Release 12.1:
  • R12.AD_PF.B.Delta.2
  • R12.ATG_PF.B.Delta.2
  • R12.CC_PF.B.Delta.2
  • R12.SCM_PF.B.Delta.2
E-Business Suite Release Update Pack

An E-Business Suite Release Update Pack (RUP) is an aggregation of product or product family RUPs on a given codeline created across Oracle E-Business Suite after the initial release. Like product family Release Update Pack, E-Business suite Release Update Pack is cumulative in nature.

Examples of E-Business Suite Release Update Packs
  • Release 12.0.4
  • Release 12.0.6
  • Release 12.1.2
Consolidated Upgrade Patch

A Consolidated Upgrade Patch is a collection of critical fixes that improve the performance and stability of the upgrade process from Release 11i to Release 12.1.1.
References
Related Articles

Monday Jul 22, 2013

Quarterly E-Business Suite Upgrade Recommendations: July 2013 Edition

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

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

Upgrade Recommendations for July 2013

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

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

  3. EBS 12.1 users should upgrade to 12.1.3.

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

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

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

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

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

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

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

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

Related Articles

Thursday Jul 18, 2013

Oracle Access Manager 11gR2 11.1.2.1.0 Certified With E-Business Suite

I am happy to announce that Oracle Access Manager 11gR2  Patchset 1 (11.1.2.1.0) is now certified with E-Business Suite Releases 11i, 12.0 and 12.1.

Choosing the Right Architecture

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 Patchset 1 using Oracle Access Manager WebGate and Oracle E-Business Suite AccessGate. If you are using Oracle Single Sign-On 10gR3 (10.1.4.3) you may migrate to Oracle Access Manager 11gR2 Patchset 1 with Oracle E-Business Suite Access Gate.

Our previously published blog article and support note provides an overview of single sign-on integration options and recommendations:

Platforms Certified

The Oracle E-Business Suite AccessGate Java application is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to the Oracle Fusion Middleware Release 11g (11.1.1.x) Certification Matrix for more details.

For information on operating systems supported by Oracle Access Manager 11gR2 and its components, refer to the Oracle Identity and Access Management 11g Release 2 (11.1.2.1.0) Certification Matrix.

Integration with Oracle Access Manager involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

References

    Related Articles

    (Article Contributor:  Allison Sparshott)

    Wednesday Jul 17, 2013

    Critical Patch Update for July 2013 Now Available

    The  Critical Patch Update (CPU) for July 2013 was released on July 16, 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:

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

    Tuesday Jul 09, 2013

    Latest DSTv20 Timezone Patches Available for E-Business Suite

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

    DSTv20 is now available and certified with Oracle E-Business Suite Release 11i, 12.0, and 12.1. The DSTv20 update includes the timezone information from Olson tzdata 2012j and is cumulative: it includes all previous Oracle DST updates. 

    Is Your Apps Environment Affected?

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

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

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

    • Africa/Casablanca,
    • America/Port-au-Prince,
    • America/Santiago,
    • America/Asuncion,
    • Antarctica/Palmer,
    • Asia/Gaza,
    • Asia/Hebron,
    • Pacific/Easter,
    • Chile/Continental,
    • Chile/EasterIsland

    What Patches Are Required?

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

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


    Wednesday Jul 03, 2013

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

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

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

    What can EBS customers expect after April 2014?

    After Microsoft desupports WinXP and Office 2003 in April 2014:

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

    What should EBS customers do?

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

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

    Related Articles

    Wednesday Jun 19, 2013

    Java JRE 1.6.0_51 Certified with Oracle E-Business Suite

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

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

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

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

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

    What's new in Java 1.6.0_51?

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

    32-bit and 64-bit versions certified

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

    32-bit JREs are certified on:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

    Java JRE 1.7.0_25 Certified with Oracle E-Business Suite

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

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

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

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

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

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

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

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

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

    For EBS 12

    Prerequisites for 32-bit and 64-bit JRE certifications

    JRE 1.70_25 32-bit + EBS 11.5.10.2

    JRE 1.70_25 32-bit + EBS 12.0 & 12.1

    JRE 1.7.0_25 64-bit + EBS 11.5.10.2

    JRE 1.70_25 64-bit + EBS 12.0 & 12.1

    EBS + Discoverer 11g Users

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

    References

    Related Articles

    Thursday Jun 06, 2013

    Discoverer 11.1.1.7 Certified with E-Business Suite

    Oracle Business Intelligence Discoverer is an ad-hoc query, reporting, analysis, and Web-publishing tool that allows end-users to work directly with Oracle E-Business Suite OLTP data.

    Discoverer graph screenshot

    Discoverer 11g (11.1.1.7) is now certified with Oracle E-Business Suite Release.  Discoverer 11.1.1.7 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.7.0, also known as FMW 11gR1 Patchset 6.  Certified E-Business Suite releases are:
    • EBS Release 11i 11.5.10.2 + ATG RUP 7 and higher
    • EBS Release 12.0.6 and higher
    • EBS Release 12.1.1 and higher

    Certified Platforms

    Oracle Discoverer Release 11g R1 Patch Set 6 (11.1.1.7) is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. For platform details, see:

    References


    Tuesday Jun 04, 2013

    Oracle Internet Directory 11gR1 11.1.1.7 Certified with E-Business Suite

    Oracle E-Business Suite comes with native user authentication and management capabilities out-of-the-box. If you need more-advanced features, it's also possible to integrate it with Oracle Internet Directory and Oracle Single Sign-On or Oracle Access Manager, which allows you to link the E-Business Suite with third-party tools like Microsoft Active Directory, Windows Kerberos, and CA Netegrity SiteMinder. 


    For details about third-party integration architectures, see:

    Oracle Internet Directory 11.1.1.7 is now certified with Oracle E-Business Suite Release 11i, 12.0 and 12.1.  OID 11.1.1.7 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.7.0, also known as FMW 11g Patchset 6.  Certified E-Business Suite releases are:
    • EBS Release 11i 11.5.10.2 + ATG PH.H RUP 7 and higher
    • EBS Release 12.0.6 and higher
    • EBS Release 12.1.1 and higher

    Supported Configurations

    Oracle Internet Directory 11.1.1.7.0 can be integrated with these single sign-on solutions for EBS environments:

    • Oracle Internet Directory (OID) and Directory Integration Platform (DIP) from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 11gR2 (11.1.2.0) with an Oracle E-Business Suite system (Release 11i, 12.0.6 or higher or 12.1.x).
    • Oracle Internet Directory and Directory Integration Platform from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 11gR1 Patchset 2 (11.1.1.7.0) with an Oracle E-Business Suite system (Release 12.0.6 or higher or 12.1.x).
    • Oracle Internet Directory and Directory Integration Platform from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 10g (10.1.4.3) with an existing Oracle E-Business Suite system (Release 11i or 12.1.x).
    • Oracle Internet Directory and Directory Integration Platform from Oracle Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Single Sign-On Server and Oracle Delegated Administration Services Release 10g (10.1.4.3.0) with an existing Oracle E-Business Suite system (Release 11i, 12.0.6 or 12.1.x).
    Oracle Access Manager strongly recommended

    Oracle has two single sign-on solutions: Oracle Single Sign-On Server (OSSO) and Oracle Access Manager (OAM). Oracle strongly recommends that all new single sign-on implementations use Oracle Access Manager. Oracle Access Manager is the preferred solution going forward, and forms the basis of Oracle Fusion Middleware 11g. OSSO is no longer being actively developed and will not be ported to Oracle WebLogic Server.

    Platform certifications

    Oracle Internet Directory is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to the Oracle Fusion Middleware 11g System Requirements for more details.

    For information on operating systems supported by Oracle Internet Directory and its components, refer to the Oracle Identity and Access Management 11gR1 certification matrix.

    Integration with Oracle Internet Directory involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

    References

    Related Articles

    Tuesday Apr 30, 2013

    Where Should EBS Concurrent Managers be Located?

    This FAQ topic continues to bounce around, suggesting that this needs to be called out explicitly:

    EBS concurrent managers do not need to be installed on database servers any more.

    Nick Quarmby correctly noted this as one of five common mistakes that customers make when installed the E-Business Suite:

    COMMON ERROR #2: Placing concurrent processing services and the database tier on the same node to improve performance.

    ORACLE’S RECOMMENDATION: There is no significant performance benefit to placing concurrent processing and the database tier on the same node. Your system will be more scalable if your database tier hardware is dedicated solely to serving the needs of the database. Patching, cloning and E-Business Suite administration will also be much easier as you will have at least one less APPL_TOP and application tier technology stack to maintain. Placing concurrent processing on the database tier node to distribute load might suggest that your application tier hardware is already undersized. You should place concurrent processing on the same nodes as your web/forms services or create a dedicated concurrent processing tier in exceptionally busy environments.

    Where is this correctly documented?

    This is currently noted in our official documentation here:

    • Oracle E-Business Suite Technology Stack Release Notes for Release 12.1.3 [ID 1098650.1]
    2.6 Updated Architectural Guidance

    With fast local networks and the typical co-location of database and application tier machines, it is now generally preferable to perform concurrent processing on a separate machine from the database. This facilitates ease of management and maintenance, and provides deployment flexibility.

    This is updated guidance is already reflected in our 12.1.3 Concepts Guide and Installation Guides, and will continue to be included in future versions of our documentation.

    A shibboleth of sorts

    Interestingly, this question is a bit of a shibboleth in the EBS sysadmin community.  DBAs who instinctively place the concurrent processing server on the same physical server as the database have been around a long time -- before gigabit network speeds made the placement irrelevant.

    In fact, sharp-eyed readers might notice that this is incorrectly-documented even in some versions of our official R12 Installation Guides, which may state erroneously: "Batch Processing services must be installed on the same node as the database."

    This is a documentation artifact from a bygone time.  This guidance doesn't apply any longer.


    Monday Apr 22, 2013

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

    Apple logoOracle E-Business Suite Release 12 is now certified with the Safari 6 browser and the JRE 7 plugin on the following Apple Mac OS X desktop configurations:

    • Mac OS X 10.7 ("Lion" version 10.7.5 or higher) and 10.8 ("Mountain Lion" version 10.8.2 or higher)
    • Safari version 6 (6.0.2 or higher)
    • Oracle JRE 7 plugin (1.7.0_21 or higher)

    Users should review all relevant information along with other specific patching requirements and known limitations posted in the Notes listed below.

    Internationalization certification for non-English desktops is also in progress.

    Where can I find more information?

    Wednesday Apr 17, 2013

    Java JRE 1.6.0_45 Certified with Oracle E-Business Suite

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

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

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

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

    What's new in Java 1.6.0_45?

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

    32-bit and 64-bit versions certified

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

    32-bit JREs are certified on:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    References

    Related Articles

    Friday Apr 05, 2013

    Covering our EBS Technology Stack Roadmap at OAUG Collaborate

    OAUG Collaborate 2013 Denver logo

    [Update Apr. 25, 2013:  The presentation is available for download here:

    I have historically covered our technology certification roadmap for the E-Business Suite in two sessions at OAUG Collaborate every year:  once during the EBS technology stack Special Interest Group meeting on Sunday, and again later in the week as a formally-scheduled conference session.

    We're trying to expand our coverage of other topics with other speakers.  This year you'll only have one chance -- not two -- to hear this material:

    • EBS Applications Technology Special Interest Group
      SIG chair: Srini Chavali, Cummins
      Sunday, April 07, 12:00 PM - 01:00 PM
      Location: Room 603

    Please join us for this session if you'd like to hear about our latest E-Business Suite technology stack certification roadmap and updates to our support terms and policies. 

    There will be a special panel in the same room at 1:15 PM where you will have the chance to ask questions of our Applications Technology Group staff members attending the conference.  These include Elke Phelps, Max Arderius, Kevin Hudson, Gustavo Jimenez, Isam Alyousfi, and me.  Other Oracle Development staff will be in the audience, too, since the dais can only seat a small number of us.

    Related Articles


    Monday Apr 01, 2013

    New Whitepaper: Function Security + Role-Based Access Control in Oracle EBS

    There are two main ways to implement security in Oracle E-Business Suite: “traditional” Oracle E-Business Suite responsibility-based security (usually referred to as “function security”) and Role-Based Access Control (RBAC).   Since they overlap in functionality, and RBAC incorporates and builds upon responsibility-based security, there is often confusion about how the two security models coexist and interact.

    I am pleased to announce the availability of a new whitepaper to help eliminate that confusion:

    RBAC vs. Grants

    This heavily-illustrated whitepaper discusses the main similarities and differences between the two types of security setups, as well as the objects involved.  It includes the following topics:

    1. Responsibility-based security (Function Security)
    2. Role-Based Access Control
    3. Functions and Permissions
    4. Roles and Grants
    5. Role Hierarchy and Role Inheritance
    6. Using Role Hierarchies to Simplify User Administration
    7. Best Practices for Implementing RBAC and Function Security

    This whitepaper is written for Oracle E-Business Suite system administrators, super-users, and implementers.  It applies to Oracle E-Business Suite Release 11i, 12.0, and 12.1.

    Happy reading!


    Wednesday Mar 27, 2013

    Migrating from EBS 11i + Oracle Single Sign-On to EBS 12 + Oracle Access Manager

    Our Identity Management team has just published an important change in the Oracle Software Technical Support Policies document (March, 2013):

    "For customers with a current support contract for Oracle Single Sign-On 10gR3, Extended Support will be made available until December 2013 at then-current Extended Support fees. During this period, Extended Support will be limited to Severity 1 fixes only; critical patch updates will not be made available."

    This is important if you've been wondering how to deal with this challenge: 

    • You know that Oracle Access Manager has supplanted Oracle Single Sign-On.  
    • You integrated Oracle Single Sign-On 10g with your E-Business Suite 11i environment several years ago.  
    • You plan to switch from Oracle Single Sign-On to Oracle Access Manager as part of your EBS 12 upgrade.
    • You want to get to EBS 12, but want to perform your EBS upgrade and OAM migrations different downtimes.
    • You've been staring at the latest EBS support timelines and deliberating your options:

    Timeline showing updated EBS Support dates

    All of the crucial pieces for this are now in place:

    1. Oracle Access Manager 11.1.2 is certified with EBS 11.5.10.2.
    2. Support for Oracle Single Sign-On 10g has been extended to Dec. 31, 2013.
    3. EBS 11.5.10's Exception to Sustaining Support has been extended to Dec. 31, 2014.
    4. EBS 12.1's Extended Support has been extended to Dec. 31, 2018.

    This means that you have sufficient support coverage for all major components while you do this in a multi-phase implementation.  You can migrate your EBS 11i environment from Oracle SSO 10g to Oracle Access Manager 11.1.2 this year, in one initial downtime.  You can then upgrade that environment from EBS 11i to EBS 12.1.3 in a later downtime. 

    Your implementation phases will look like this:

    1. Today: EBS 11i + Oracle Single Sign-On 10.1.4.3
    2. Interim phase:  EBS 11i + Oracle Access Manager 11.1.2
    3. Final phase: EBS 12.1.3 + Oracle Access Manager 11.1.2

    Each of these undertakings can be fairly major initiatives on their own, so breaking the overall project into smaller parts helps you manage your risk.  I would be very interested in hearing about your experiences with this kind of combined migration + upgrade implementation approach.  Please feel free to post a comment here or drop me a line privately.

    Related Articles


    Monday Mar 18, 2013

    Oracle Access Manager 11.1.2 Certified With E-Business Suite 11i

    I am pleased to announce that Oracle Access Manager 11gR2 (11.1.2.0.0) is now certified with E-Business Suite Release 11.5.10.2.  If you are implementing single sign-on for the first time, or currently use Oracle Access Manager or Oracle Single Sign-On, you may integrate with Oracle Access Manager 11gR2 using Oracle Access Manager WebGate and Oracle E-Business Suite AccessGate.

    EBS Oracle Access Manager architecture

    Transitionary architecture for EBS 12 upgrades

    This new certification can be used as a intermediate architecture on your upgrade path to EBS 12. This may allow you to reduce your overall risk and downtimes by doing your upgrade in multiple phases.

    For example, you might be using Oracle Single Sign-On with your EBS 11i environment today.  You will need to switch from Oracle Single Sign-On to Oracle Access Manager as part of your upgrade.  You can use the following strategy to phase in this new component:

    1. Today: EBS 11i + Oracle Single Sign-On 10.1.4.3
    2. Interim phase:  EBS 11i + Oracle Access Manager 11.1.2
    3. Final phase: EBS 12.1.3 + Oracle Access Manager 11.1.2
    Supported Architecture and Release Versions
    • Oracle Access Manager 11.1.2
    • Oracle E-Business Suite Release 11.5.10.2 + ATG Rollup Patchset 6 (11i.ATG_PF.H.delta.6) and higher.
    • Oracle Internet Directory 11.1.1.6
    • Oracle WebLogic Server 10.3.5+

    References

    Related Articles

    Tuesday Mar 12, 2013

    New YouTube Channel for Oracle E-Business Suite

    We've just launched a new YouTube channel for Oracle E-Business Suite.  The videos on this YouTube channel have a strategic and functional focus, so it's an excellent business-oriented complement to this blog's technology stack and DBA-oriented material and our ATG Live Webcasts.

    Cliff Godwin, Senior Vice President, has just posted a new video discussing the E-Business Suite's latest Strategy and Roadmap:

    EBS YouTube channel screenshot

    This video covers some of the highlights of Cliff's presentation at conferences such as Oracle OpenWorld, OAUG Collaborate, and other international events.

    You and your business users can subscribe to this channel to get updates on a variety of functionally-oriented EBS topics.

    Related Articles


    Tuesday Mar 05, 2013

    Resolving "JInitiator version too low" Errors in EBS Environments

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

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

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

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

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

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

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

    What's causing this error?

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

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

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

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

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

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

    For EBS 12

    Related Articles

    Monday Mar 04, 2013

    Java JRE 1.6.0_43 Certified with Oracle E-Business Suite

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

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

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

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

    What's new in Java 1.6.0_43?

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

    32-bit and 64-bit versions certified

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

    32-bit JREs are certified on:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    References

    Related Articles

    Java JRE 1.7.0_17 Certified with Oracle E-Business Suite

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

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

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

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

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

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

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

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

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

    For EBS 12

    Prerequisites for 32-bit and 64-bit JRE certifications

    JRE 1.70_17 32-bit + EBS 11.5.10.2

    JRE 1.70_17 32-bit + EBS 12.0 & 12.1

    JRE 1.7.0_17 64-bit + EBS 11.5.10.2

    JRE 1.70_17 64-bit + EBS 12.0 & 12.1

    EBS + Discoverer 11g Users

    JRE 1.7.0_17 (7u17) 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 will change for EBS users after February 2013. 

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What will Mac users need?

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

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

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

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

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

    References

    Related Articles

    Postpone IE 10 Upgrades Until E-Business Suite Certification

    New IE logo

    [Aug. 9, 2013 update: IE 10 is now certified with EBS]

    [May 3, 2013 update: Added EBS version numbers]

    Microsoft has recently announced their plans to automatically update IE 8 or IE 9 on Windows 7 desktops to IE 10; see:

    Microsoft states:

    Distribution of Internet Explorer 10 by Automatic Updates will begin slowly and take several months to complete.

    We're still certifying Microsoft Internet Explorer 10 with Oracle E-Business Suite 11.5.10.2, 12.0, and 12.1. We expect IE 10 to work with few issues, but it is always prudent to ensure that your mission-critical desktops remain on an earlier certified IE version until this certification is completed.  You can block automatic updates by using Microsoft's Internet Explorer 10 Blocker Toolkit:

    When will IE10 be certified with EBS?

    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.   

    Related Articles

    Friday Mar 01, 2013

    Plans for Certifying Google Chrome with E-Business Suite

    Google Chrome logoGoogle Chrome is a popular browser in the consumer sector.  It's fast, clean, and standards-compliant.  It's also popular internally at Oracle: many of our own Applications Technology Group staff -- notably, our OA Framework architects and developers -- ignore Oracle's own desktop standards and use Chrome as their default browser. 

    This tells you that Chrome generally works nicely with Oracle E-Business Suite. There may be some quirks with specific products, but it is largely compatible with most OA Framework-based screens.

    That said, it isn't officially certified with the E-Business Suite.

    Why not?

    We're reserving judgement on making it an official certification because of what appears to be low demand from EBS enterprise customers. This seemingly-low demand doesn't warrant expanding our current certification permutations further.

    Our current certification space is already intimidatingly-large.  For Windows desktops alone, we currently have over 400 officially-certified combinations of EBS {11i | 12.0 | 12.1} * Windows {XP | Vista | 7 | 8} * {{IE 6 | 7 | 8 | 9 | 10} | Firefox ESR } * JRE {6 | 7} * Office {2003 | 2007 | 2010 | 2013}.

    Adding Chrome for just Windows 7 and 8 could add up to 48 new combinations to be tested.

    The impending death of the conventional browser certification model

    You're probably not shocked to hear that we don't test every one of those 400 combinations with every new EBS release.  And, yes, I've heard every variant of the obvious jokes about the number of combinations that we actually do test.

    It's clear that conventional certification approaches aren't sustainable.  Mobile devices and their associated browsers are proliferating. The new reality of bring-your-own-device (BYOD) in the enterprise space is inescapable.

    We're examining options for moving beyond the conventional certification model for EBS browsers.  I'll post more details when they're available.  Until then, we're going to continue with the status quo of certifying specific browser versions with specific clients with specific EBS releases.

    Enterprises leery of browsers on rapid release cycles?

    In 2011, Mozilla switched Firefox to a rapid release cycle with a new release coming out every six weeks.  Most enterprises (including Oracle) can't keep up with that deployment rate, so we switched our E-Business Suite + Firefox certification track to Mozilla's Extended Support Release (ESR) channel. Mozilla's ESR releases come out every 12 months.

    My impression is that enterprises have become a little wary of using Firefox since Mozilla's change to a rapid release cycle. I conduct straw polls of my audiences at various conferences.  It seems like enterprise use of Firefox has dwindled dramatically in the last few years.

    That's just a theory, and it doesn't affect our certification policies.  We've certified Firefox with the E-Business Suite in the past, so we'll continue to certify Firefox for the foreseeable future. But that illustrates the importance of being careful about certification decisions.  Once we certify something, it's very difficult to withdraw support in the future.

    Chrome is also released on a rapid release cycle.  This cycle appears to be driven by various less-predictable or unpublished factors, but the upshot is that their cycles average out to a new release every 6 to 8 weeks

    This begs some interesting questions.  If enterprise usage of Firefox changed because of Mozilla's switch to a rapid release cycle, what do enterprises think of Chrome's rapid release cycle?  Google doesn't offer an equivalent of Mozilla's annually-updated option for Chrome.  How are enterprises managing Chrome deployments?

    Some EBS customers can't control their users desktops

    EBS customers with externally-facing modules (e.g. iRecruitment, iSupplier, iStore, etc) cannot control their users's desktops.  This is especially true for educational institutions.

    Luckily for those customers, the vast majority of EBS OA Framework-based (HTML) screens work reliably with a wide range of certified and uncertified browsers, including Chrome.  Things get trickier when dealing with the Forms-based products that require specific JRE releases, but this generally isn't an issue since Forms-based EBS products aren't available to "external" (non-enterprise) users.

    Would you like us to certify Chrome with EBS?

    Chrome generally works well with the E-Business Suite, but we can only provide EBS patches for issues that can be reproduced with certified browsers. 

    If you'd like us to add Chrome as an officially-certified browser, please log a Service Request and ask Support to update enhancement request 5921574 with details about:

    • Your business case (e.g. "student user population not centrally managed")
    • Minimum desired EBS release
    • EBS products to be used
    • Estimates of desktops affected
    • Minimum desired Windows release

    Related Articles

    Monday Feb 25, 2013

    Avoid Mixing Custom Applications with E-Business Suite Environments

    The E-Business Suite technology stack is extensive. Many components are distributed across the EBS database and application tiers.  These include the Oracle Database, Oracle HTTP Server, Oracle Forms and Reports 10g, Oracle Containers for Java, and many others.

    EBS 12.1 technology stack architecture

    Internal EBS components are tightly-coupled

    Most of these components are not "user-serviceable" in the conventional manner.  They're tightly integrated with the E-Business Suite, with deep dependencies, custom configuration files, and dedicated configuration management utilities that are designed specifically for the E-Business Suite.  

    The internal E-Business Suite technology stack is relatively tightly-coupled: you generally cannot change one thing without understanding how those changes will affect other components. 

    Examples of what this means:

    • You can't drop a new UIX library into an EBS environment without also delivering the corresponding changes in the OA Framework layer.
    • You can't simply replace the E-Business Suite's Oracle Forms and Reports 10g with, say, Oracle Forms and Reports 11g. 

    External integrations are loosely-coupled

    It is also possible to integrate the E-Business Suite with other Oracle products.  These integrations are optional, in the sense that you don't need them to use the core E-Business Suite functionality.  These are sometimes called external integrations since they're outside of the core EBS technology stack.

    Examples of external integrations:

    • You can optionally integrate Oracle Business Intelligence Enterprise Edition with your EBS environment to offer advanced analytic capabilities.
    • You can optionally use Oracle Access Manager and Oracle Internet Directory if you'd like to integrate the E-Business Suite with a third-party authentication system.
    External integrations (e.g. OBIEE, Oracle Access Manager, Discoverer) are loosely-coupled.  For example, applying the Discoverer 11.1.1.6 patchset won't trigger changes to EBS products that deliver Discoverer workbooks. Some small interoperability patches required, but you can generally upgrade externally-integrated Oracle products without significant changes to E-Business Suite technology stack components or product level code. 

    Before you upgrade internal and external components

    You should always check that newer versions of internal and external components are certified before upgrading them.  We release around 80 new certified component updates a year, comprising over 150 configurations.  Monitoring or subscribing to this blog is the best way of keeping up.

    The official Certification database on My Oracle Support is the definitive source of all EBS certifications.  I've also published a one-page summary of all of the latest E-Business Suite techstack certifications on this blog.

    What does this mean for custom applications?

    You might be tempted to deploy a custom application in the E-Business Suite technology stack.  After all, you think to yourself, that's easier than installing a separate server for, say, OC4J. 

    Don't do it.

    The E-Business Suite internal technology stack should be reserved strictly for the E-Business Suite. Mingling your own custom applications into the E-Business Suite technology stack:

    • Makes it difficult to debug or isolate EBS performance or stability issues.
    • Increases your security risk.  If your custom application is compromised, then your EBS environment may also be jeopardized, or vice versa.
    • Makes it difficult to upgrade EBS components if your custom application is dependent on older versions.
    • Makes it difficult to upgrade your custom application if the E-Business Suite is dependent on older component versions than your custom code.
    • Potentially doubles your maintenance outages for your users. Your EBS environment will be taken down every time you need to apply an update to your custom application, and vice versa.

    What you should do

    Option 1: Deploy on a separate server

    Ideally, you should install your custom application and its required technology stack prerequisites on a different physical server.  This will ensure that the E-Business Suite remains completely isolated from your custom application, its technical requirements, and its load requirements.  This is the recommended approach.

    Option 2: Deploy in a separate ORACLE_HOME on an EBS server

    Less ideally, you can install your custom application in a different ORACLE_HOME on an existing E-Business Suite server.

    This is not recommended. There are a number of downsides to this approach:

    • If your custom application's security is compromised, this might put your E-Business Suite environment at risk.
    • Deploying your custom application and its components on your EBS server will make performance tuning difficult.  If your server's resources are maxed out, how do you determine whether the problem lies with EBS or your custom application?  

    • A single point of failure: server maintenance or outages take down all applications that share that server.  Physical consolidation saves money but increases risk.

    Implications for support

    Here's the biggest reason not to mix EBS environments with custom applications:  it makes support very difficult, if not impossible. 

    Oracle can best assist with issues that we can reproduce.  We can issue EBS patches only for issues that can be reproduced on standard EBS environments. 

    If a problem occurs in an E-Business Suite environment that includes other uncertified components or code, then our default recommendation will be to disable those before investigating further.

    Related Articles

    Thursday Feb 21, 2013

    Getting Started as an E-Business Suite DBA

    The other day, a reader asked, "How does one become an EBS DBA?" He'd worked on an ERP environment in the past but seemed to be overwhelmed. This is understandable; there's lots to learn.  The good news is that there are many options to becoming an Apps DBA.

    If you have limited funds

    1. Start with the official documentation

    There is a vast trove of information contained within the online E-Business Suite Documentation Library. Our documentation writers are devoted to capturing everything that you need to know to manage the E-Business Suite, and the organization of the documentation is top-notch.  All aspiring DBAs should start here:

    Screenshot of new EBS documentation library

    2. Build your own sandbox environment

    The only way to learn is to work with a real environment. You can download Oracle VM templates for the E-Business Suite and have an environment running within a few hours:

    3. Get the latest information

    EBS technology is constantly being refreshed.  You can learn about specific EBS topics from the developers themselves in these free one-hour webcasts:

    We release over 150 new certifications a year, so it's vital to monitor or subscribe to this blog to stay current:

    4. Talk with your peers

    There are dozens of Oracle EBS discussion forums. The best DBAs in the world congregate here and are generous with their expertise.  Some recommendations for DBAs:

    If you prefer formal classroom-style training

    Oracle University has some excellent courses: Oracle Applications - E-Business Suite Training

    Here are some great ways get started in E-Business Suite Tools and Technologies:

    If you want to get certified

    You can get certified through the Oracle Certified Professional (OCP) program. Here is the learning track to becoming an EBS DBA:

    There's no free lunch

    As I was getting ready to fire off an email to the gentleman, I sat back and thought about the context of the gentleman’s inquiry. We have a diversified selection of education offerings that are fee-based and free. Oracle University courses are outstanding. Self study classes can be performed from anywhere. Our documentation resources are extensive as well as comprehensive. We have software to download and try. Everything is in place to achieve all the goals you might ever want to achieve dealing with Oracle Application Technologies. 

    There is just one catch: whatever route the gentleman chooses to take, there will have to be a substantial investment in time and resources. Technology continually advances, so this will be an ongoing investment.

    Often, individuals who embark on the path of learning our technologies miss that. I wish I could convey to those that start the journey, that even for those of us who are Oracle professionals, we never stop learning our own technologies.

    There is no easy way to become an expert.  but it's worth it


    Wednesday Feb 20, 2013

    Plans for Certifying Windows 8 and IE 10 with E-Business Suite

    Windows 8 logo

    [Aug. 9, 2013 update: IE 10 is now certified with EBS]

    Microsoft Windows 8 was recently released with Internet Explorer 10 as its default browser.  Here's an interim update on our plans for certifying them with Oracle E-Business Suite.

    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 Windows 8 and IE 10

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

    When will Win8 and IE 10 be certified with EBS?

    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, which I'll post as soon as soon as they're available.    

    Which Windows 8 versions will be certified?

    As of today, I expect that we will explicitly test the Windows 8 Pro edition with Oracle E-Business Suite.  We expect that the results of these certification tests will apply equally to the following editions:

    • Windows 8
    • Windows 8 Enterprise
    • Windows 8 N edition
    • Windows 8 Pro N edition
    • Windows 8 Pro Pack N edition
    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 64-bit Windows 8?

    Windows 8 is available in a 64-bit version as well as a 32-bit version.  It is expected that we will certify the 32-bit version first, followed by the 64-bit version later.

    IE logoWhat about IE 10 for other Windows releases?

    Internet Explorer 10 requires Windows 8 or Windows 7 SP1.  We expect to certify IE10 on those operating systems as desktop clients for EBS 11.5.10.2, 12.0, and 12.1.

    We have no current plans to certify the E-Business Suite with IE 10 on Windows RT.

    Any Early Adopter Programs planned?

    No, we don't currently have any plans to offer an Early Adopter Program for either Win8 or IE 10 with Oracle E-Business Suite.  If that changes, I'll post an article on this blog with a call for participants.  

    Related Articles

    Tuesday Feb 19, 2013

    Java JRE 1.7.0_15 Certified with Oracle E-Business Suite

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

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

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

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

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

    EBS customers should ensure that they are running JRE 7u15, 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 are summarized here for convenience. If the requirements change over time, please check the Notes for the authoritative list of patches:

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

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

    Where are the official patch requirements documented?

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

    For EBS 11i:

    For EBS 12

    Prerequisites for 32-bit and 64-bit JRE certifications

    JRE 1.70_15 32-bit + EBS 11.5.10.2

    JRE 1.70_15 32-bit + EBS 12.0 & 12.1

    JRE 1.7.0_15 64-bit + EBS 11.5.10.2

    JRE 1.70_15 64-bit + EBS 12.0 & 12.1

    EBS + Discoverer 11g Users

    JRE 1.7.0_15 (7u15) 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 will change for EBS users after February 2013. 

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What will Mac users need?

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

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

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

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

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

    References

    Related Articles

    Java JRE 1.6.0_41 Certified with Oracle E-Business Suite

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

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

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

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

    What's new in Java 1.6.0_41?

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

    32-bit and 64-bit versions certified

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

    32-bit JREs are certified on:

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

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    References

    Related Articles

    Monday Feb 18, 2013

    Plans for Certifying Microsoft Office 2013 with E-Business Suite

    Microsoft Office 2013 logoCongratulations to my colleagues at Microsoft on their launch of Microsoft Office 2013 last month.  Questions about our certification plans for Office 2013 are filling my inbox, so here's an interim update on our plans. 

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

    We plan to certify Oracle E-Business Suite Release 11.5.10.2, 12.0, and 12.1 with Microsoft Office 2013.

    When will Office 2013 be certified with EBS?

    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, which I'll post as soon as soon as they're available.   

    How does the E-Business Suite work with Microsoft Office?

    The Oracle E-Business Suite is comprised of several product families such as Financials, Supply Chain Management, Human Resources, and so on.  These product families group together collections of individual products.  Some of these products may be optionally integrated with one or more Microsoft Office components such as Excel, Word, and Projects.

    Individual E-Business Suite product teams have the option of building integrations between their products and one or more Microsoft Office components.  This is not mandatory.  Over forty E-Business Suite teams offer these kinds of Office integrations today.

    Examples of these integrations include:
    • HRMS Payroll integrations with Microsoft Excel
    • Supply Chain Management Contracts Core integration with Microsoft Word
    • Financials General Ledger (GL) integration with Microsoft Excel
    • Customer Relationship Management (CRM) Proposals integration with Microsoft Word
    • Web Application Desktop Integrator (Web ADI)
    • Desktop Integration Framework
    Which Office versions will be certified?

    Our actual certification plans are under review, but as of today, I expect that we will explicitly test the Office 2013 Professional edition with Oracle E-Business Suite.  We expect that the results of these certification tests will apply equally to the following desktop-installed editions:
    • Home & Student 2013
    • Home & Business 2013
    • Standard 2013 
    • Professional 2013
    • Professional Plus 2013
    We do not currently plan to certify the following editions with Oracle E-Business Suite:
    • SkyDrive-based documents
    • Office On Demand
    • Office Web Apps
    • Office 365
    • Office Home & Student RT

    I would not expect the results of our certification with Office 2013 Professional Edition to apply to the above editions or features.

    What about 64-bit Office?

    Office 2013 offers a 64-bit version as well as a 32-bit version.  It is expected that we will certify the 32-bit version first, followed by the 64-bit version later.

    Any Early Adopter Programs planned?

    No, we don't currently have any plans to offer an Early Adopter Program for Office 2013 with Oracle E-Business Suite.  If that changes, I'll post an article on this blog with a call for participants. 

    What about OpenOffice, StarOffice, LibreOffice?

    We have no plans to certify the E-Business Suite with versions of OpenOffice, StarOffice, LibreOffice, or other equivalents.  

    Related Articles

    About

    Search

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