Friday Apr 18, 2014

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

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

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

What can EBS customers expect after April 2014?

After Microsoft desupports WinXP and Office 2003 in April 2014:

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

What should EBS users do?

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

What about EBS desktop-based client/server tools?

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

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

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

For complete details, see:

Pending Desktop Certifications 

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

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

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

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

Related Articles


Thursday Apr 17, 2014

Best Practices for Deploying EBS 12.2 on Oracle Database Appliance

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

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

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

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

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

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

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

Related Articles


Wednesday Apr 16, 2014

Critical Patch Update for April 2014 Now Available

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

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

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

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

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

The next four Critical Patch Update release dates are:

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

Tuesday Apr 15, 2014

Java JRE 1.6.0_75 Certified with Oracle E-Business Suite

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in in this Java release?

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.7.0_55 Certified with Oracle E-Business Suite

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

Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

What's new in JRE 1.7.0_55?

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Quarterly E-Business Suite Upgrade Recommendations: April 2014 Edition

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

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

Upgrade Recommendations for April 2014

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Thursday Apr 03, 2014

Understanding and Managing Licensing Options in Oracle E-Business Suite

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

We receive a lot of questions on this particular area:

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


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

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

Friday Mar 28, 2014

New Recommended Patch Collection for EBS 12.1.3 Now Available

I am very pleased to announce the availability of E-Business Suite 12.1.3+ Recommended Patch Collection 1.  This Recommended Patch Collection combines recommended patches for EBS 12.1.3 into a single integrated and regression-tested patchset:


Why is this important?

Getting to EBS 12.1.3 isn't enough.  Additional patches must be applied on top of EBS 12.1.3 before going into production. These include individual patches, product family Release Update Packs (RUP), and product-specific Recommended Patch Collections (RPC). 

For example, there are Recommended Patch Collections for Financials products such as General Ledger, Payables, and others.  On the technology side, there are patchsets such as the OA Framework 12.1.3.1 Consolidated Update Patch

Identifying these individual patches, RUPs, Family Packs, and RPCs can be time-consuming.  Complicating matters further, patchsets across multiple product families are generally not tested together.

Included in Recommended Patch Collection 1 (RPC1)

The EBS 12.1.3+ RPC1 patchset includes a comprehensively-tested set of the latest recommended patches and their dependencies for the following EBS product families:

  • Applications Technology Group (ATG)
  • Customer Relationship Management (CRM)
  • Financials (FIN)
  • Human Resource Management System (HRMS)
  • Procurement (PRC)
  • Projects (PJ)
  • Supply Chain Management (SCM)
  • Value Chain Planning (VCP)

Your feedback is welcome

We are very interested in hearing about your experiences with this new Recommended Patch Collection.  You can post a comment here or send me an email directly.

Related Articles

Tuesday Mar 25, 2014

Oracle VM Templates For EBS 12.2.3 For Exalogic

We are pleased to announce that Oracle VM Templates for Oracle E-Business Suite 12.2.3 for Exalogic are available for download from the Oracle Software Delivery Cloud:

Screenshot of Oracle VM template download site for Exalogic images

These VM templates can be imported into the Enterprise Manager Ops Center to deploy E-Business Suite Linux 64-bit environments on Exalogic servers for demonstration, development or production use.

The Exalogic Elastic Cloud platform is optimized for the application tier. We recommend that you run databases that experience heavy loads (such as User Acceptance Tests or Production databases) on a machine dedicated for that purpose.

These templates deliver the full EBS software stack, including the Oracle Linux 5.8 operating system, Oracle E-Business Suite, and additional required technology components.

The available Oracle E-Business Suite Release 12.2.3 templates for Exalogic are:

  • VISION Demo Database Tier
  • Production (PROD) Database Tier
  • Application Tier
  • Sparse Application Tier

An Oracle E-Business Suite Release 12.2.3 for Exalogic installation requires one template for the database tier and another for the primary application tier.

First, choose either the VISION Demo Database template (for a fully-configured demonstration system with sample data) or the Production (PROD) Database template for an empty instance ready for configuration and production deployment. Then choose the Application Tier template.

You can optionally use the Sparse Application Tier template to add a secondary application tier to your new installation or to an existing farm.  Sparse Application Tier templates are small Oracle VM templates that contains an operating system,  Secondary application tiers can be used for EBS web, application, and batch servers.

References

Related Articles


Monday Mar 17, 2014

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

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

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

This webcast is tomorrow:

EM12c AMP 12.1.0.2 screenshot

Related Articles


Thursday Mar 13, 2014

Important Updates to EBS 12.2 AD and TXK Tools

We are pleased to announce two new updates for the Oracle E-Business Suite 12.2 Technology Stack (TXK) and  Applications DBA (AD) suite of administrative tools respectively.  They include important Online Patching updates.  All EBS 12.2 users are strongly encouraged to apply these new updates to their environments as soon as possible.

The updates include:

  • New features: simplified addition and deletion of Weblogic Server managed servers, new Online Patching Log Analyzer utility, and additional Online Patching options.
  • Stability and performance-related updates.

AD-delta-4-screenshot

You can download the two updates (RUPs) here:

Future AD and TXK updates will be delivered on top of these AD and TXK RUPs.

References

Related Articles

Friday Feb 21, 2014

startCD options to install Oracle E-Business Suite Release 12.2

The startCD 12.2.0.47 for Oracle E-Business Suite has been replaced with Patch 17873425. This patch is now available in My Oracle Support.

Screenshot of download page for patch 17873425 startCD

The new startCD includes more than a dozen bug fixes, support for  Microsoft Windows x64 (64-bit) and it also includes JDK 7 as part of the standard E-Business Suite installation (as opposed to JDK 6 installed by the startCD 12.2.0.46).

As a general principle, we recommend using the latest startCD (currently, 12.2.0.47) to install and upgrade to the latest Oracle E-Business Suite Release (currently 12.2.3). However, not all customers may be able to do this immediately, especially if their internal testing cycles were initiated on previous JDK versions.

Two supported upgrade paths are available. Choose the one that best suits your needs:

  • Use startCD 12.2.0.47 to upgrade to Release 12.2.2 or 12.2.3. This will include JDK7 as part of the installation.
  • Use startCD 12.2.0.46 to upgrade to Release 12.2.2 or 12.2.3, in conjunction with the AD/TXK.Delta.3 patches. This will retain JDK6.

Note: With regard to the second option above, the compatibility of the AD/TXK.Delta.3 patches with both JDK 6 and JDK 7 gives you the flexibility to upgrade from 12.2.2 to 12.2.3 and retain JDK6. We  recommend moving to JDK 7 at your earliest opportunity.

These are the permutations:

startCD Version JDK Version AD/TXK Codelevel Release Supported
startCD 12.2.0.46 JDK6 R12.TXK.C.DELTA.2/R12.AD.C.delta.2 12.2.2
startCD 12.2.0.46 JDK6 R12.TXK.C.DELTA.3/R12.AD.C.delta.3 12.2.3
startCD 12.2.0.47  JDK7 R12.TXK.C.DELTA.2/R12.AD.C.delta.2  None
 startCD 12.2.0.47
 JDK7
R12.TXK.C.DELTA.3/R12.AD.C.delta.3 12.2.2
startCD 12.2.0.47 JDK7 R12.TXK.C.DELTA.3/R12.AD.C.delta.3 12.2.3

Related Articles


Wednesday Feb 12, 2014

Oracle Access Manager 11.1.2.2 Certified with Oracle E-Business Suite

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

Choosing the Right Integration

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

References

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

    Related Articles

    Tuesday Jan 21, 2014

    Support Implications for Your EBS Customizations

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

    You may choose to:

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

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

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

    The support implications boil down to this:

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

    Related Articles

    Friday Jan 17, 2014

    EBS 12.2 Certified with Database 11.2.0.3 for Additional "Database Tier-only" Platforms

    I am pleased to announce that Oracle E-Business Suite Release 12.2 (12.2.2 or higher) is now certified with the Oracle Database 11gR2 (11.2.0.3) for the Linux on IBM System z and Oracle Solaris on x86-64 platforms running on the database tier with the following OS versions:

    For Oracle Solaris on x86-64:

    • Oracle Solaris 10 on x86-64 (64-bit)
    • Oracle Solaris 11 on x86-64 (64-bit)

    For Linux on IBM System z:

    • Red Hat Enterprise Linux (RHEL) version 5 (64-bit)
    • Red Hat Enterprise Linux (RHEL) version 6 (64-bit)
    • Novell SUSE Linux Enterprise Server (SLES) version 10 (64-bit)
    • Novell SUSE Linux Enterprise Server (SLES) version 11 (64-bit)

    The application tier of the E-Business Suite 12.2 is not certified with the above platforms, only the database tier; customers must run the application tier on fully certified platforms using the 12.2 software provided as part of our release (see 'Oracle E-Business Suite 12.2 Now Available').

    This announcement for E-Business Suite Release 12.2 includes the following (as well as other features and options):

    • Oracle Database 11gR2 version 11.2.0.3
    • Oracle Database Real Application Clusters (RAC) 11gR2 version 11.2.0.3
    • Oracle Database Vault 11gR2 version 11.2.0.3
    • Transparent Data Encryption (TDE) Column Encryption using Oracle Database 11gR2 version 11.2.0.3
    • TDE Tablespace Encryption using Oracle Database 11gR2 version 11.2.0.3
    • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 11gR2 version 11.2.0.3
    • Export/Import Process for Oracle E-Business Suite Release 12 Database Instances

    References

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

    Wednesday Jan 15, 2014

    Java JRE 1.6.0_71 Certified with Oracle E-Business Suite

    Java logo

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

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

    What's new in in this Java release?

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

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

    32-bit and 64-bit versions certified

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

    Worried about the 'mismanaged session cookie' issue?

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

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

    Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

      Related Articles

      Java JRE 1.7.0_51 Certified with Oracle E-Business Suite

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

      Effects of new support dates on Java upgrades for EBS environments

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

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

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

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

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

      New Features in JRE 1.7.0_51

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

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

      Exception Site List

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

      32-bit and 64-bit versions certified

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

      Where are the official patch requirements documented?

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

      For EBS 11i:

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

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

      Worried about the 'mismanaged session cookie' issue?

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

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

      Implications of Java 6 End of Public Updates for EBS Users

      The Support Roadmap for Oracle Java is published here:

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

      Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

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

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

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

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

      Coexistence of JRE 6 and JRE 7 on Windows desktops

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

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

      Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

      What do Mac users need?

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

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

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

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

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

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

      References

      Related Articles

      Tuesday Jan 14, 2014

      Critical Patch Update for January 2014 Now Available

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

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

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

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

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

      The next four Critical Patch Update release dates are:

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

      Monday Jan 13, 2014

      EBS Release 12 Certified with Mac OS X 10.9 with Safari 7 and JRE 7

      Apple logoOracle E-Business Suite Release 12 (12.1.1 or higher) is now certified with the Safari 7 browser and the JRE 7 plugin on the following Apple Mac OS X desktop configuration:

      • Mac OS X 10.9 ("Mavericks" version 10.9.1 or higher)
      • Safari version 7 (7.0.1 or higher)
      • Oracle JRE 7 plugin (1.7.0_45 or higher)

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

      References

       Related Articles

      Wednesday Jan 08, 2014

      Java (JDK) 7 Certified with E-Business Suite 12.2 Servers

      Java logoOracle E-Business Suite 12.2 shipped with Java SE (JDK) 6 as part of its Rapid Install technology stack. 

      Java (JDK) 7 is now certified for EBS 12.2 application and database tier servers.  See:

      You can apply the Java 7 update on all tier nodes:

      • Java 6.0 either Oracle JRockit (JRockit) or Java SE Development Kit (JDK), on the application tier
      • 32-bit or 64-bit Java 6 for use by Oracle WebLogic Server 11.1.1.6.0 only
      • Non-WebLogic middle tier nodes using 32-bit Java version 6.0 only
      • Java SE Development Kit (JDK) version 6.0 on the OracleAS 10g 10.1.2 application tier hosting Oracle Forms and Reports services
      • Java SE Runtime Environment (JRE) version 6.0 on the database tier

      End-users can use either JRE 6 or 7 on their Windows desktop clients to run Forms-based products in EBS 12.2.

      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 changed 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).

      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 desktop clients can connect to EBS 12.2 environments running JDK 7.

      JRE 6 will be available to Windows users to run with EBS to the end of Java SE 6 Extended Support in June 2017.  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.

      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 to the end of Java SE 6 Extended Support in June 2017.  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 to the end of June 2017.

      Summary of EBS Certifications

      There is a one-page summary of all of the latest E-Business Suite techstack certifications here:

      • http://blogs.oracle.com/stevenChan/resource/certifications.html

      This listing summarizes the official CERTIFY database on My Oracle Support.  The CERTIFY database is the official and authoritative reference for all E-Business Suite certifications.

      Related Articles


      Monday Jan 06, 2014

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

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

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

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

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

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

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

      EM12c AMP 12.1.0.2 screenshot

      Related Articles


      Friday Jan 03, 2014

      Which JDeveloper Version Works With Your EBS Release?

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

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

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

      Related Articles

      Monday Dec 16, 2013

      Oracle E-Business Suite 12.2.3 Now Available

      We are very pleased to announce that Oracle E-Business Suite Release 12.2.3 is generally available for download now:

      EBS 12.2.3 Patch 17020683 download

      Instructions for downloading and applying the patch:

      What Does EBS 12.2.3 Include?

      This Release Update Pack (RUP) for the EBS 12.2 release codeline includes new features as well as statutory and regulatory updates, and error corrections for stability, performance, and security. 

      This is a consolidated suite-wide patch set. Release 12.2.3 is cumulative and includes new updates as well as updates made available in one-off patches on 11.5.10, 12.0, 12.1.3, and the base 12.2 releases.

      User Experience Modernization

      With 12.2.3, the Oracle E-Business Suite incorporates current UI design trends and improves user productivity by including:

      • New look and feel: appears lighter and fresher, with flat rather than dimensional elements, reduced gradients, and white or light colors with splashes of darker color.

      • Rich table interaction: allows an end user to scroll through a table if its width exceeds the browser's width, detach a table and work with it as a separate component with a wider width, and re-size and reorder table columns that an end user can then save as a user personalization.

      • Worklist header icon: displays by default in all HTML-based pages, the worklist header icon is an alternative to including a worklist region in the Oracle E-Business Suite home page. Users can select the icon to view a summarized list of recent notifications, then click to view and respond to notification details.

      For a complete list of new features, see:

      Upgrading to EBS 12.2.3

      Is there a direct upgrade path from EBS 11i to 12.2.3?

      No.  EBS 11i customers must first upgrade to EBS 12.2 before applying 12.2.3.

      Is there a direct upgrade path from EBS 12.0 to 12.2.3?

      No.  EBS 12.0 customers must first upgrade to EBS 12.2 before applying 12.2.3.

      Is there a direct upgrade path from EBS 12.2 to 12.2.3?

      Yes.  EBS 12.2 customers can apply 12.2.3 directly to their environments.  EBS 12.2.3 is an Online Patch -- it may be applied while EBS 12.2 is running.

      How can I prepare for EBS 12.2?

      More technical references

      Related Articles


      Friday Dec 13, 2013

      Automate Testing Using Oracle Application Testing Suite with Flow Builder for E-Business Suite

      Previous articles have discussed the benefits of automated testing with the Oracle Application Testing Suite, a.k.a, "OATS". As a reminder, OATS includes the following components:
      • Oracle Functional Testing Suite for Oracle Applications – for functional and regression testing
      • Oracle Load Testing Suite for Oracle Applications – for load and performance testing
      • Oracle Test Manager – for test process management, test execution and defect tracking

      The latest release of Oracle Application Testing Suite, referred to as 12.3, includes a new "Flow Builder" capability designed to reduce the effort and expertise needed to create and maintain automated test scripts for EBS 12.1.3 and 12.2. This should be welcome news for EBS customers looking to streamline their upgrade projects.

      What is Flow Builder?
      Flow Builder is an automated test generation framework delivered as part of the Oracle Functional Testing Suite for Oracle Applications. It provides an alternative to the traditional "record/playback" method for creating test scripts, which is time-consuming and produces scripts that are difficult to maintain.

      Using Flow Builder, even non-technical testers can generate working test scripts from pre-built components. Each component represents an atomic test operation such as “create an invoice batch” or “apply an invoice hold.” Testers can assemble the pre-built components into test flows, and combine test flows with spreadsheet data to drive the testing of multiple data conditions. To maintain Flow Builder-generated scripts, testers need only know the names of common application functions instead of a complex scripting language.

      Screenshot of Oracle Flow Builder extension for Oracle Application Testing Suite

      Includes a Starter Kit
      The EBS QA team uses the Flow Builder feature to do EBS testing, and provides pre-built test content that customers can use to jump start their own testing projects. Flow Builder includes an EBS starter kit with over 2000 pre-built components and 200 pre-built flows. The Flow Builder framework allows customers to add, modify and extend the pre-built components and flows to address new functionality and customizations to EBS.

      Improves Productivity
      The EBS QA team has improved their productivity by 60% using Flow Builder’s component-based test generation framework instead of a traditional record/playback approach. With Flow Builder, EBS customers can significantly improve their productivity and test coverage while saving on testing expense. Flow Builder content updates will be available for each new EBS major release, allowing customers to reduce maintenance overhead for test scripts. 

      Downloads
      You can download the Oracle Application Testing Suite from the Oracle Software Delivery Cloud or the Oracle Technology Network.

      References

      Related Articles


      Wednesday Dec 11, 2013

      New IBM AIX on Power OS and Tools Requirements for EBS 12

      IBM logoBeginning on February 16th 2014, Oracle E-Business Suite patches for Release 12 (12.0, 12.1, 12.2) on the IBM AIX on Power Systems platform will be built with a newer version of the IBM XL C/C++ compiler (version 11). Customers who plan to patch or upgrade their E-Business Suite environments after February 16th 2014 must meet all the new requirements prior to applying new patches generated after this date.

      IBM has published an end of Support date for the compiler version (XL 9) that is currently used for Release 12 builds and patching.

      We are announcing this to give time for our customers to prepare and to be compliant with all requirements for E-Business Suite patches generated after this February 16th 2014 date.

      Please review the documents below for all new requirements required by the changes in the runtime and utilities packages on IBM AIX on Power Systems.

      Where can I find more information?

      Friday Dec 06, 2013

      11.2.0.4 Database Certified with E-Business Suite on 11 New Platforms

      As a follow up to our prior announcements, Oracle Database 11g Release 2 (11.2.0.4) is now certified with Oracle E-Business Suite Release 11i and Release 12 on the following additional platforms:

      EBS Release 12.1 (12.1.1 or higher):

      • Oracle Solaris on SPARC (64-bit) (10, 11)
      • Oracle Solaris on x86-64 (64-bit) (10)1
      • HP-UX Itanium (11.31)
      • IBM AIX on Power Systems (64-bit) (5.3, 6.1, 7.1)
      EBS Release 12.0 (12.0.4 or higher):
      • Oracle Solaris on SPARC (64-bit) (10)
      • Oracle Solaris on x86-64 (64-bit) (10)1
      • HP-UX Itanium (11.31)
      • IBM AIX on Power Systems (64-bit) (5.3, 6.1, 7.12)

      EBS Release 11i (11.5.10.2 + ATG PF.H RUP 6 and higher):

      • Oracle Solaris on SPARC (64-bit) (10, 111)
      • Oracle Solaris on x86-64 (64-bit) (10)1
      • IBM AIX on Power Systems (64-bit) (5.3, 6.1)

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

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

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

      Related Articles

      Monday Dec 02, 2013

      Office 2010 64-bit Certified with EBS 12

      Office 2010 logoMicrosoft Office 2010 64-bit is now certified with EBS 12.0.6, 12.1.3, and 12.2 with desktop clients using the following configurations:

      The 32-bit equivalents are already certified; details are available here.

      Are any patches required?

      You must apply server-side patches to EBS 12.0.6 and 12.1.3 environments.  Additional server-side patches are not required for EBS 12.2.x.  All required interop patches are documented here:

      What about EBS 11i?

      There are no plans for this certification in E-Business Suite 11i.  This certification primarily affects Web Application Desktop Integrator (a.k.a. WebADI, BNE) and Report Manager (FRM) integration with a 64-bit desktop client configuration.  Architectural constraints in the EBS 11i versions of these components make these certifications infeasible.

      What EBS products are covered by this certification?

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

      Which Office versions are certified?

      We explicitly tested Microsoft Office 2010 64-bit Professional Edition with Oracle E-Business Suite.  We expect that our certification tests also apply to the 64-bit equivalents, if available, to the following editions:

      • Home and Student Edition
      • Home and Business Edition
      • Standard Edition
      • Professional Academic Edition
      • Professional Plus Edition
      We have no plans to certify the following editions with Oracle E-Business Suite:
      • Office Web Apps
      • Starter Edition
      • Mac Edition
      • Office Mobile
      I would not expect the results of our certification with Office 2010 Professional Edition to apply to the four editions above.

      How are these integrations supported?

      You can log Service Requests against the E-Business Suite product that you're trying to integrate with Microsoft Office. 

      For example, you might be trying to take advantage of CRM Marketing (AMS) 12.1.2's integration with Excel 2010.  To get support, you can log an SR against CRM Marketing directly. 

      The Support team for that product will help you diagnose and resolve the problem.  If the issue is isolated to a Microsoft product, then it may be necessary to log a corresponding support ticket with Microsoft, as well.

      Related Articles


      Thursday Nov 21, 2013

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

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

      Our official policy on direct modifications to EBS databases

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

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

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

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

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

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

      Can data corruption really occur?

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

      What about third-party data archiving and purging tools?

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

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

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

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

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

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

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

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

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

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

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

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

      Related Articles


      Tuesday Nov 19, 2013

      Quarterly E-Business Suite Upgrade Recommendations: November 2013 Edition

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

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

      Upgrade Recommendations for November 2013

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

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

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

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

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

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

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

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

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

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

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

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

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

        Related Articles

        Friday Nov 15, 2013

        Oracle VM Templates Available for E-Business Suite Release 12.2.2

        Oracle VM Templates for Oracle E-Business Suite Release 12.2.2 are now available here:

        Templates are available for:

          • Oracle E-Business Suite Release 12.2.2 Vision Demo Database Tier Install (64-bit Linux)
          • Oracle E-Business Suite Release 12.2.2 Production Database Tier Install (64-bit Linux)
          • Oracle E-Business Suite Release 12.2.2 Application Tier Install (64-bit Linux)
          • Oracle E-Business Suite Release 12.2.2 Sparse Application Tier Install (64-bit Linux - Oracle Linux 5.9)
          • Oracle E-Business Suite Release 12.2.2 Sparse Application Tier Install (64-bit Linux - Oracle Linux 6.4)

          These Oracle VM Templates allow you to quickly build E-Business Suite 12.2.2 environments on Oracle Linux virtual machines for demonstration, development or production use.  The templates deliver the full software stack, including the operating system, required technology components, and Oracle E-Business Suite itself.

          Screenshot of Oracle VM template download site


          You can deploy these templates on any industry-standard x86-based hardware certified for Oracle VM and Oracle Linux.

          An Oracle E-Business Suite Release 12.2.2 installation requires two templates, one for the database and one for the primary application tier.   You can choose from two database templates, depending on whether you will deploy a Vision demonstration system or an empty production instance.  In addition to the database template and the primary application tier template, you can optionally deploy a "sparse middle tier" template to add secondary application tiers.

          References

          Related Articles

          About

          Search

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