Friday Jul 19, 2013

Announcing Oracle E-Business Suite Extensions for Oracle Endeca 12.1.3.3

The Oracle E-Business Suite Extensions for Oracle Endeca provide selected EBS applications with Oracle Endeca-based capabilities. These extensions allow users to take an information-driven approach to business, optimizing operational decisions and improving process efficiency.

Each extension provides an existing EBS application with a search-oriented dashboard that summarizes current operational information. Users can explore this information in whatever way makes sense to them, combining free text and faceted search with drilldown on visualizations such as key performance indicators (KPIs), tag clouds, charts and cross-tabs. With each drilldown or search refinement, the entire set of visualizations and search choices changes to reflect the user’s previous choices. Users can browse and drill to the subset of information that is important for them to act on, automatically passing context to an EBS transaction screen where they can take the necessary action – for example, expediting a sales order by substituting a replacement part.

Endeca screenshot

The Oracle E-Business Suite Extensions for Oracle Endeca allow users to leverage modern, self-service discovery mechanisms for identifying and acting on exceptions and opportunities. Users can find information that that they otherwise might not find with conventional ERP query screens, reducing their reliance on emails, phone calls, and IT-provided reports.

What’s New in Oracle E-Business Suite Extensions for Oracle Endeca 12.1.3.3?
Oracle recently announced Oracle E-Business Suite Extensions for Oracle Endeca 12.1.3.3 for EBS 12.1.3 environments.  This release adds six new extensions:

  • Oracle Warehouse Management Extensions for Oracle Endeca
  • Oracle Installed Base Extensions for Oracle Endeca
  • Oracle Process Manufacturing Extensions for Oracle Endeca
  • Oracle Cost Management Extensions for Oracle Endeca
  • Oracle Depot Repair Extensions for Oracle Endeca
  • Oracle Learning Management Extensions for Oracle Endeca

In addition, 12.1.3.3 includes updates to nine previously-available extensions:

  • Oracle Order Management Extensions for Oracle Endeca
  • Oracle Discrete Manufacturing Extensions for Oracle Endeca
  • Oracle Inventory Management Extensions for Oracle Endeca
  • Oracle Channel Revenue Management Extensions for Oracle Endeca
  • Oracle Enterprise Asset Management Extensions for Oracle Endeca
  • Oracle Field Service Extensions for Oracle Endeca
  • Oracle Project Management Extensions for Oracle Endeca
  • Oracle iProcurement Extensions for Oracle Endeca
  • Oracle iRecruitment Extensions for Oracle Endeca  

Technical Overview of Oracle E-Business Suite Extensions for Oracle Endeca
Oracle E-Business Suite Extensions for Oracle Endeca use Oracle Endeca Information Discovery (EID) technology, which features:

  • A hybrid search-analytical engine
  • A user interface optimized for visual discovery and analysis
  • A data integration (ETL) engine

E-Business Suite transactional information is loaded and stored in a faceted, in-memory data model that gets refreshed with changes at intervals prescribed by the system administrator. Information is pre-classified, pre-summarized, and pre-sorted before it becomes available for search, discovery and analysis in a rich content container that is embedded within an EBS HTML page.  EBS handles session management so that Endeca content in the rich content container is consistent with EBS context and security.

EBS customers can add Endeca-based capabilities using an all-in-one installer, achieving out-of-the box security and integration with their Oracle E-Business Suite applications. We typically recommend that the EID components be run on any hardware or VM running 64-bit Oracle or Redhat Linux V5 or V6.

Downloads

You can download the Oracle E-Business Suite Extensions for Oracle Endeca Media Pack here:

References

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)

    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:


    Tuesday Jul 02, 2013

    Plans for Certifying Oracle Database 12c with E-Business Suite

    Oracle Database 12c Logo

    [Oct. 24, 2013 Update: Database 12.1.0.1 is certified with the E-Business Suite]

    The Oracle Database 12c is now officially released.  We're as excited about this new database release as you are. 

    In fact, we've been testing a wide variety of E-Business Suite releases and configurations with internal DB 12c betas for some time.  This testing is going well, but as usual, Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates

    You're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.   


    Monday Jul 01, 2013

    E-Business Suite R12 Certified on 2012 Hyper-V Windows Guests

    Microsoft LogoOracle E-Business Suite Release 12 (12.1) is now certified on Windows Server 2008 (32-bit) and Windows Server 2008 R2 running as guest operating systems within Window Server 2012 Hyper-V virtual machines.

    Hyper-V is a built-in feature of Microsoft Windows Server that allows for the creation and management of virtualized computing environments. With this certification, the E-Business Suite is now supported on the above Windows virtualized guest operating systems in a similar way to non-virtualized Windows.

    References

    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

    Monday Jun 10, 2013

    Java (JDK) 7 Certified for E-Business Suite 12.0 and 12.1 Servers

    Java logoWindows and Mac-based desktop clients connecting to the E-Business Suite can use the Java Runtime Environment (JRE) plug-in to run Forms-based components.  JRE 7 was certified with EBS 11.5.10.2, 12.0, and 12.1 in 2012.  As of today, the latest available version is JRE 1.7.0_21 for Windows clients and for Mac clients.  All new JRE releases on the 1.6 and 1.7 codelines are automatically certified with EBS on the day of their release.  If you're reaching this article via a search engine, please check My Oracle Support or the Certifications summary for the latest desktop version available.

    Java (JDK) 7 is now certified for E-Business Suite 12.0 and 12.1 application and database tier servers.  For instructions on upgrading your EBS 12.x environments, see:

    The Java version currently in your environment

    Oracle E-Business Suite Release 12 Rapid Install delivers the following Java SE Development Kit (JDK) Versions for use by Oracle E-Business Suite:

    Release 12.0.x

      • Java SE Development Kit (JDK) Version 5.0 on the application tier
      • Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
      • Java SE Runtime Environment (JRE) Version 5.0 on the database tier

    Release 12.1.x

      • Java SE Development Kit (JDK) Version 6.0 on the application tier
      • Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
      • Java SE Runtime Environment (JRE) Version 6.0 on the database tier

    You can now upgrade to the newer Java 7.0 Update on all EBS application tier and database tier nodes. Please note that the JRE 7.0 upgrade on the database tier is independent from the others. But if the application tier nodes are planned to be upgraded to Java 7.0, the same upgrade in the OracleAS 10.1.2 ORACLE HOME must be planned together.

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

    In other words, nothing 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 JDK 7 for EBS 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.

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

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

    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 290801.1 and 393931.1.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What will Mac users need?

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

    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.

    References

    Related Articles

    Friday Jun 07, 2013

    WebCenter 11.1.1.7 Certified with E-Business Suite 12

    Oracle WebCenter Suite is an integrated suite of Fusion Middleware 11gR1 tools used to create web sites and portals using service-oriented architecture (SOA).  Applications adapters are also available.

    WebCenter Development Framework

    WebCenter Portal 11.1.1.7 (a.k.a. Patchset 5) is now certified with Oracle E-Business Suite Release 12 (12.0.6 and higher; 12.1.1 and higher).  WebCenter Portal 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 Platforms

    Oracle WebCenter 11gR1 Version 11.1.1.6 is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. For information on operating systems supported by Oracle WebLogic Server 11g and Oracle Portal, refer to the 'Oracle Fusion Middleware on WebLogic Server - System Certification' in the Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Certification Matrix.

    Migrating to Oracle WebCenter

    If you're currently using Oracle Portal, you should be aware that Portal is now in maintenance mode.  Updates with bug fixes will continue to be produced, but you should consider migrating to Oracle WebCenter for ongoing new features.

    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

    Friday May 10, 2013

    Oracle Access Manager 11gR1 Patchset 2 11.1.1.7 Certified with EBS 12

    Oracle Access Manager 11gR1 Patchset 2 (a.k.a. 11.1.1.7) is now certified with E-Business Suite Release 12.0 and 12.1.  Applying Oracle Access Manager 11gR1 Patchset 2 will provide you with the latest set of fixes for Oracle Access Manager 11gR1 which have been validated with Oracle E-Business Suite Release 12.0 and 12.1.

    Oracle has two single sign-on solutions, Oracle Single Sign-On Server (OSSO) and Oracle Access Manager. 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. Oracle Single Sign-On is no longer being actively developed and will not be ported to Oracle WebLogic Server.

    Prerequisites

    • Oracle E-Business Suite Release 12.1.1 and higher, Release 12.0 RUP 6 (12.0.6)
    • Oracle Internet Directory 11gR1 PS1 (11.1.1.2) or higher

    Platforms Certified

    Oracle Access Manager 11gR1 is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to Oracle Fusion Middleware Supported System Configurations on the Oracle Technology Network (OTN):

    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

    The following documents have been updated to include a new table listing Oracle Access Manager 11gR1 bundle patches that have been certified with Oracle E-Business Suite Release 12:

    Related Articles

    Wednesday May 08, 2013

    BPEL 11.1.1.7 Certified for Prebuilt E-Business Suite 12.1 SOA Integrations

    Service Oriented Architecture (SOA) integrations with Oracle E-Business Suite can either be custom integrations that you build yourself or prebuilt integrations from Oracle.  For more information about the differences between the two options for SOA integrations, see this previously-published certification announcement.

    There are five prebuilt BPEL business processes by Oracle E-Business Suite Release 12 product teams:

    1. Oracle Price Protection (DPP)

    1. Complex Maintenance, Repair & Overhaul (CMRO/AHL)

    1. Oracle Transportation Management (WMS, WSH, PO)

    1. Advanced Supply Chain Planning (MSC)

    1. Product Information Management (PIM/EGO)

    BPEL integration architecture diagram example

    Last year we announced the certification of BPEL 11.1.1.6 for Prebuilt E-Business Suite 12.1.3 SOA integrations.  The five prebuilt BPEL processes have now been certified with Oracle BPEL Process Manager 11g version 11.1.1.7 (in Oracle Fusion Middleware SOA Suite 11g).  These prebuilt BPEL processes are certified with Oracle E-Business Suite Release 12.1.3 and higher.

    Note: The Supply Chain Trading Connector (CLN) product team has opted not to support BPEL 11g with their prebuilt business processes previously certified with BPEL 10.1.3.5.  If you have a requirement for that certification, I would recommend contacting your Oracle account manager to ensure that the Supply Chain team is notified appropriately. 

    For additional information about prebuilt integrations with Oracle E-Business Suite Release 12.1.3, please refer to the following documentation:

    Certified Platforms

    • Linux x86 (Oracle Linux 4, 5)

    • Linux x86 (RHEL 5)

    • Linux x86 (SLES 10)

    • Linux x86-64 (Oracle Linux 4, 5, 6)

    • Linux x86-64 (RHEL 5)

    • Linux x86-64 (SLES 10) 

    • Oracle Solaris on SPARC (64-bit) (9, 10, 11)

    • HP-UX Itanium (11.23, 11.31)

    • HP-UX PA-RISC (64-bit) (11.23, 11.31)

    • IBM AIX on Power Systems (64-bit) (5.3, 6.1, 7)

    • IBM: Linux on System z (RHEL 5, SLES 10)

    • Microsoft Windows Server (32-bit) (2003, 2008) 

    • Microsoft Windows x64 (64-bit) (2008 R2)

    Getting Support

    If you need support for the prebuilt EBS 12.1.3 BPEL business processes, you can log Service Requests against the Applications Technology Group product family.

    Related Articles


    Thursday May 02, 2013

    Secure Global Desktop 5 Certified with E-Business Suite 12

    Screenshot of Oracle Secure Global DesktopOracle Secure Global Desktop provides secure access to centralized applications—Microsoft Windows, UNIX, mainframe, and midrange—from a variety of clients including Windows PCs, Oracle Solaris workstations, Linux PCs, and thin clients.  Secure Global Desktop 4.6 was certified with the E-Business Suite last year.

    Secure Global Desktop 5 is now certified with E-Business Suite 12.  

    Secure Global Desktop 5 is certified for use with Microsoft Windows Server 2003 and 2008 virtualized environments acting as desktop clients connecting to Oracle E-Business Suite Release 12 environments.  32-bit and 64-bit versions of Microsoft Windows Server are certified. These combinations may also be used in conjunction with Oracle VM, if required.

    Requirements

    Windows Server 2008 R2 (64-bit)

      • Windows Server 2008 R2 (64-bit) is certified with Oracle E-Business Suite 12.1.3 running:
      • Internet Explorer 8 (32-bit and 64-bit) or Internet Explorer 9 (32-bit and 64-bit)
      • JRE Plug-in 1.6.0_32 (32-bit and 64-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit and 64-bit) or higher

    Windows Server 2008 (32-bit)

    • Windows Server 2008 (32-bit) is certified with Oracle E-Business Suite 12.1.3 running:
    • Internet Explorer 8 (32-bit) or Internet Explorer 9 (32-bit)
    • JRE Plug-in 1.6.0_32 (32-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit) or higher

    Windows Server 2003 R2 (64-bit)

    • Windows Server 2003 R2 (64-bit) is certified with Oracle E-Business Suite 12.1.3 running:
    • Internet Explorer 8 (32-bit and 64-bit)
    • JRE Plug-in 1.6.0_32 (32-bit and 64-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit and 64-bit) or higher

    Windows Server 2003 R2 (32-bit)

      • Windows Server 2003 (32-bit) is certified with Oracle E-Business Suite 12.1.3 running:
      • Internet Explorer 8 (32-bit)
      • JRE Plug-in 1.6.0_32 (32-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit) or higher

    References

    Related Articles

     

    Wednesday Apr 24, 2013

    Seven EBS 12 Products Supported on Linux, Solaris, and AIX

    Some earlier Oracle E-Business Suite R12 certifications on newer operating systems excluded the following products due to the lack of third-party product support:
    • Advanced Supply Chain Planning
    • Inventory Optimization
    • Constraint Based Optimization
    • Sourcing
    • Engineering
    • Work In Process
    • Manufacturing Scheduling

    These restrictions are now lifted and the products are now officially supported on the following operating systems:

    • Oracle Linux 6 and Red Hat Enterprise Linux 6 on Linux x86 (32-bit)
    • Oracle Linux 6 and Red Hat Enterprise Linux 6 on Linux x86-64 (64-bit)
    • Novell SUSE Linux Enterprise Server (SLES) 11 on Linux x86-64 (64-bit)
    • Solaris 11 on Oracle Solaris on SPARC (64-bit)
    • AIX 7 on IBM AIX on Power Systems (64-bit)
    References

    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.7.0_21 Certified with Oracle E-Business Suite

    Java logoJava Runtime Environment 7u21 (a.k.a. JRE 7u21-b11) 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_21 32-bit + EBS 11.5.10.2

    JRE 1.70_21 32-bit + EBS 12.0 & 12.1

    JRE 1.7.0_21 64-bit + EBS 11.5.10.2

    JRE 1.70_21 64-bit + EBS 12.0 & 12.1

    EBS + Discoverer 11g Users

    JRE 1.7.0_21 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_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


    Friday Mar 22, 2013

    Apple iPads Certified with Oracle E-Business Suite 12.1

    Apple iPad and iPad miniApple iPads are certified with Oracle E-Business Suite 12.1. 

    This certification covers Safari with E-Business Suite OA Framework-based (HTML) applications.  These are sometimes also referred to as "Self-Service Web Applications" (SSWA).

    This certification also covers the use of Apple's Mail app to approve E-Business Suite Workflow notification emails.

    It is not possible to run Java-based applications on iOS devices, so Oracle Forms-based products requiring the Java Runtime Environment (JRE) plug-in are not available on iPads.

    Requirements

    • Oracle E-Business Suite 12.1.3 and higher
    • iOS 6.0 and higher

    What about iPhones?

    EBS OA Framework-based products are currently designed assuming that the client device has a desktop-class screen (e.g. 1024 x 768).  Safari on iPhones also works, but given the smaller screen size, the user experience is not ideal.  We recommend using iPads for the optimal user experience when accessing OA Framework-based EBS products.

    The use of Apple's Mail app to approve EBS Workflow notification emails is certified for both iPads and iPhones.

    Using standards-compliant mail clients to approve Workflow notifications

    Oracle Workflow is a key part of the E-Business Suite's technology stack.  It can be configured to send emails (via SMTP) that notify E-Business Suite users that certain EBS transactions are awaiting their approval.  E-Business Suite end-users can respond to those notification emails by clicking on a link in those emails, or responding with an email containing certain keywords in the body of a reply.

    We test Workflow and E-Business Suite notifications using Windows desktop based email clients such as Microsoft Outlook.  We have tested Apple's Mail app as part of this iOS certification.  We do not currently perform any tests of Workflow notification emails with other mobile devices (e.g. Android, BlackBerry Email).

    We would expect standards-compliant email clients to be able to handle Workflow notification emails properly, including email clients on mobile devices.  Some mobile email clients are unable to handle standards-based emails, and other email clients may truncate long Workflow notification emails.  These issues may prevent certain email clients on mobile devices from handling Workflow notifications properly.

    If you encounter issues with Workflow email notifications on smartphones or mobile devices that can't be reproduced on standards-compliant email client, our recommendation would be to process Workflow notifications on the latter.

    On a side note: technically-inclined readers might be interested to hear that we're aware of at least one web-based email client that does not comply with RFC 2368 in its handling of new line characters in mailto URL encoding.  Web-based email clients with issues like that will be unable to handle Workflow notifications properly.  If you encounter issues with web-based email clients that cannot be reproduced on a conventional Windows desktop-based email client, our recommendation would be to process Workflow notifications on the latter.

    What about other mobile devices?

    Other mobile devices are not certified yet.  If you have deployment plans for Android-based devices as EBS clients in your organisation, please drop me a line with details.  We are working through complications around fragmentation in the Android space, and insights into your requirements would be helpful.

    References

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

    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

    Tuesday Feb 26, 2013

    MKS Toolkit 9.5 certified with EBS Release 12.1 on Microsoft Windows

    MKS Toolkit logoMKS Toolkit version 9.5 is now certified as a release maintenance tool with Oracle E-Business Suite Release 12.1.1 or higher on Microsoft Windows Server (32-bit) and Microsoft Windows x64 (64-bit).

    The operating systems supported by MKS Toolkit v9.5 on this platform:

    • Microsoft Windows Server (32-bit) (2003, 2008)
    • Microsoft Windows x64 (64-bit) (2008 R2)

    Please review the documents below for all requirements to use MKS Toolkit v9.5 with E-Business Suite Release 12.

    Where can I find more information?


    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

    Tuesday Feb 12, 2013

    New Source Databases Added for Transportable Tablespaces + EBS 11i

    The Transportable Tablespace (TTS) process was originally certified for migrating E-Business Suite 11i databases across different "endian" (byte ordering) formats from 11gR2 source databases to 11g2 target databases.

    This certification has now been expanded to include two new source database releases:

    • Database 11gR1 11.1.0.7
    • Database 10gR2 10.2.0.5

    Endian formats supported

    Obtaining this patch

    This migration process requires a Controlled patch delivered by the Oracle E-Business Suite Platform Engineering team, i.e. it requires a password obtainable from Oracle Support. We released the patch in this manner to gauge uptake, and help identify and monitor any customer issues due to the nature of this technology. 

    Does it meet your requirements?

    Note that for migration across platforms of the same "endian" format, users are advised to use the Transportable Database (TDB) migration process instead for large databases. The "endian-ness" target platforms can be verified by querying the view V$DB_TRANSPORTABLE_PLATFORM using SQL*Plus (connected as sysdba) on the source platform:

    SQL>select platform_name from v$db_transportable_platform;

    If the intended target platform does not appear in the output, it means that it is of a different endian format from the source. Consequently. database migration will need to be performed via Transportable Tablespaces (for large databases) or export/import.

    The use of Transportable Tablespaces can greatly speed up the migration of the data portion of the database. However, it does not affect metadata, which must still be migrated using export/import. We recommend that users initially perform a test migration on their database, using export/import with the 'metrics=y' parameter. This will help identify the relative amounts of data and metadata, and provide a basis for assessing likely gains in timing. In general, the larger the amount of data (compared to metadata), the greater the reduction in downtime that can be expected from using XTTS as a migration process.

    Where can I find more information?

    Related Articles

    About

    Search

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