Friday Aug 28, 2015

"Certified" vs. "Error Correction Support": What's the Difference?

We've recently gotten a string of questions about the support status of obsolete products listed in the Certifications system on My Oracle Support.  This is really important: everyone working with Oracle products should know how to determine the support status of their products.

The existence of a listing in the Certifications system doesn't necessarily mean that a product release is covered by Error Correction Support. 

To determine the support status of a particular combination:

  1. Check if the combination is listed in the Certifications system
  2. Check the support status of the product releases
  3. Check the support status of the product patch sets
  4. Interpret this information
Let's walk through these steps in more detail.

Understanding the three phases of support

We produce new patches and certifications for Oracle products while they are covered by either Premier or Extended Support.  Those two support phases are collectively known as the Error Correction Support period. 

After that period, products are covered by Sustaining Support.  You can download existing patches and documentation for products in Sustaining Support.  You cannot request new patches or certifications for these products.

See the Oracle Lifetime Support Policy site for more details about Premier, Extended, and Sustaining Support levels.

Step 1. Check if the combination is listed in the Certifications system

The Certifications system on My Oracle Support lists all of the combinations that we've tested for the E-Business Suite. Certifications are generally retained for reference purposes after the Error Correction Support phase has ended for those products. The existence of an historical listing in the Certifications system doesn't necessarily mean that that is still covered by Error Correction Support.

For example, the Certifications system includes historical listings for:

  • EBS 11.5.3 (Error Correction Support ended July 2006)
  • EBS 12.0.6 (Error Correction Support ended January 2015)
  • Oracle Single Sign-On 10.1.2.0.2 (Error Correction Support ended December 2011)
  • Oracle Database 8.1.7.4 (Error Correction Support ended December 2006)

You cannot request new patches or certifications for any products after their Error Correction Support ends.

Step 2: Check the support status of a product release

A product release is the major version.  For example, Database 11gR2 is the product release.


You should always check the Oracle Lifetime Support documents for a product release's Premier and Support dates to determine whether the release is covered by Error Correction Support. 

See:

Step 3: Check the the support status of a product patch set

Product releases have patch sets. For example: the Database 11gR2 release has 11.2.0.3 and 11.2.0.4 patch sets.

Individual patch sets have their own Error Correction Support dates. You should always check the following documents for the support status of a given patch set:

Step 4: Interpret this information 

You can ask for new patches for a given combination only if all products within that combination are still covered by Error Correction Support. 

Example 1:

  • It is August 1, 2015.
  • You see a listing in the Certifications system for EBS 12.0.6 + Database 11.2.0.4
  • Error Correction Support for E-Business Suite 12.0.6 ended January 2015
  • Error Correction Support for Database 11.2.0.4 continues to January 2018
  • You cannot request new patches for this combination

Example 2:

  • It is August 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Oracle Access Manager 10.4.3.2
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Error Correction Support for Oracle Access Manager 10.1.4.3 ended December 2011
  • You cannot request new patches for this combination

Example 3:

  • It is August 1, 2015
  • You see a listing in the Certifications system for EBS 12.1.3 + Oracle Database 11.2.0.2
  • Error Correction Support for EBS 12.1.3 continues to December 2019
  • Error Correction Support for Database 11.2.0.2 ended October 2013
  • You cannot request new patches for this combination

Still confused?

If you're still having trouble, log a Service Request with Oracle Support.  A Support Engineer can help with these types of questions.

Related Articles

Monday Aug 24, 2015

JRE 1.8.0_60 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

No.

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

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

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

References

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


Friday Aug 07, 2015

Windows 10 Certified with Oracle E-Business Suite

Windows 10 logoMicrosoft Windows 10 (32-bit and 64-bit) is certified as a desktop client operating system for end-users accessing Oracle E-Business Suite 11.5.10.2, 12.1, and 12.2 with the following components.

EBS 12.1 and 12.2

  • Browsers
  • Microsoft Internet Explorer 11
  • Mozilla Firefox ESR 38
  • Chrome 44 and higher (HTML/OA Framework modules only)
  • Java client plug-ins
  • JRE 1.8.0_51 and higher
  • JRE 1.7.0_85 and higher

EBS 11.5.10.2

  • Browsers
  • Microsoft Internet Explorer 11
  • Mozilla Firefox ESR 38
  • Java client plug-ins
  • JRE 1.8.0_51 and higher
  • JRE 1.7.0_85 and higher
Later JRE 7 and 8 releases on Windows 10

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops.  This applies to Windows 10 desktops, too, for the JRE releases list above.

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

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

Pending certifications 

Desktop Client/Server Products

The certification of our various Client/Server products, for example JDeveloper OA Extensions, Forms Developer and Workflow Builder against Windows 10 are in progress. For a full list of products see  Recommended Set Up for Client/Server Products with Oracle E-Business Suite 11i & R12 (Note 277535.1). The certification matrix within this document will be updated as these are completed.

Microsoft Edge Browser

The certification of Microsoft Edge on Windows 10 with Oracle E-Business Suite 12.1 and 12.2 is currently in progress. There are no plans to certify this browser for Oracle E-Business Suite 11i.

Oracle E-Business Suite R12 has two interfaces: a web-based (OA Framework/HTML) model for modules like iProcurement and iStore, and Oracle Forms/Java based model for our professional services modules like Oracle Financials. Microsoft Edge does not support Java and will therefore only be certified for E-Business Suite customers running web-based (HTML / OA Framework) EBS products. Running Java-based EBS products with Edge will not feasible.

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

References

Related Articles


Wednesday Aug 05, 2015

Using Oracle Database In-Memory with Oracle E-Business Suite

Authors: Andy Tremayne and Deepak Bhatnagar, Oracle Development

Database In-Memory is one of a number of options that can be deployed to address Oracle E-Business Suite performance concerns and scalability requirements without the need for any application changes.

We are pleased to announce the publication of a new white paper that can help with this (including links to patches that you will need to apply):

The paper starts by providing strategic advice and guidelines that help you decide which objects to populate into Database In-Memory (DBIM), and how to size the In-Memory Column Store (IMCS). It provides a list of best practices and explains the complexities and limitations of using DISTRIBUTE/DUPLICATE with Oracle RAC.

Database In-Memory diagram

The examples in this paper take a step away from the classic headline feature of analytical reports that you might have been expecting. Instead, they show how DBIM can be applied to three novel use cases:

  • The Order Organizer Form has a huge number of queryable fields that would all need to be indexed for optimal performance. DBIM provides a 10X improvement in the end-user response time.
  • The Initialize Credit Summaries concurrent program is unusual the optimization is based on an INSERT statement. It is also interesting as the example shows why simply populating objects into the IMCS can result in a performance reduction – in this case spilling to disk. Simply populating the objects into DBIM improved the time by 1.5X; further tuning improved on this to provide an overall gain of 3.5X.
  • The Receiving Transaction Processor had two long-running queries that reduced from 7.8 hrs to 4.85 mins representing about a 100X increase in performance. The overall runtime was about 4X faster.

One of the key aspects in the paper is describing how to use Oracle E-Business Suite Application Affinity with Oracle RAC. It describes how to overcome some of the limitations of Non-Engineered Systems (commodity hardware), and explains how it can also be used to benefit Oracle Engineered Systems.

Other References

The Oracle Database In-Memory blog contains a wealth of generic information, technical details, ideas and news on Oracle Database In-Memory from the author of the Oracle White Paper on Oracle Database In-Memory.

Related Articles

Friday Jul 24, 2015

Quarterly EBS Upgrade Recommendations: July 2015 Edition

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

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

You can research these yourself using this Note:

Upgrade Recommendations for July 2015

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Wednesday Jul 22, 2015

Can You Use IE 11 Enterprise Mode or Compatibility View With EBS?

Microsoft IE LogoMicrosoft Internet Explorer 11 offers two options for enabling backwards-compatibility:

You should not use either of these with Oracle E-Business Suite.  These two modes have no benefit for EBS end-users. 

These two methods are not needed for EBS compatibility.  You should ensure that you have applied all of the latest EBS server-side patches to avoid any compatibility issues:

Related Articles

Monday Jul 20, 2015

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

I'm pleased to announce that Oracle Internet Directory 11gR1 Patchset 7 (11.1.1.9) is now certified for use in the Oracle Access Manager integration with Oracle E-Business Suite Release 11i (11.5.10.2) and 12 (12.1.3+, 12.2.2+). 

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 and Windows Kerberos. 


For details about third-party integration architectures, see:

Supported Configurations

Oracle Internet Directory 11.1.1.9.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 7 (11.1.1.9.0) with Oracle Access Manager 11gR2 (11.1.2.0) with an Oracle E-Business Suite system (Release 11i (11.5.10.2), 12.1.3+ or 12.2.2+).
  • 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.1.3+).
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.

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 Jul 17, 2015

Oracle Access Manager 11.1.2.3 Certified with E-Business Suite

I am pleased to announce that Oracle Access Manager 11gR2 Patchset 3 (11.1.2.3.0) is now certified with Oracle E-Business Suite Release 11i (11.5.10.2) and 12 (12.1.3+, 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.


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.  You may refer to the Oracle Fusion Middleware Release 11g (11.1.1.x) Certification Matrix for more details.

For information on supported platforms for Oracle Access Manager 11gR2 and its components, you may refer to the Oracle Identity and Access Management 11g Release 2 (11.1.2.3.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.

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

Thursday Jul 16, 2015

Using Logical Hostnames in E-Business Suite Release 12.x

We've recently received many inquiries on how to configure Oracle E-Business Suite application and database tiers to use logical hostnames. To help with this, we have just published a new Note:

Logical hostname screenshot

This new Note describes how to configure a machine to use a logical hostname, and the subsequent use of Rapid Install or Rapid Clone to configure the file system.  There is also a discussion of the different scenarios in which logical hostnames can be employed.

Many of the examples shown depict E-Business Suite Release 12.2 on Linux 64-bit, but the fundamental concepts also apply to Releases 12.0 and 12.1, and to other operating systems.

Employing logical hostnames offers several distinct advantages:

  • Hides from the end users the physical servers that host the applications software
  • Reduces configuration changes needed in network reconfiguration, data center migration, and disaster recovery
  • Facilitates the creation of an identical copy (clone) if needed
  • Avoids the need to clone a system just to change the hostname

The Note covers three different scenarios:

  1. Using logical host names in creation of an identical clone - How using logical hostnames can aid in the creation of a system that is identical to the original system in every way except for the different physical hostname and network address.

  2. Using logical host names to avoid rewiring after changes in network configuration - How logical hostnames can minimize the impact of necessary host name and IP address changes.

  3. Using logical host names to faciliate enabling Oracle WebLogic Administration Server high availability - How either a standby virtual machine or standby physical server can be used to achieve high availability of the Admin Server if the Admin Server and the standby system share the same logical hostname. 

Wednesday Jul 15, 2015

JRE 1.8.0_51 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

What's new in this release?

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

No.

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

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

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

References

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


JRE 1.7.0_85 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in this release?

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.6.0_101 Certified with Oracle E-Business Suite

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

New EBS installation scripts

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

32-bit and 64-bit versions certified

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Critical Patch Update for July 2015 Now Available

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

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

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

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

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

The next four Critical Patch Update release dates are:

  • October 20, 2015
  • January 19, 2016
  • April 19, 2016
  • July 19, 2016
E-Business Suite Releases 11i and 12 Reference

Tuesday Jul 14, 2015

Accessing Oracle E-Business Suite from Mobile Apps

Oracle E-Business Suite users need to have access to the Oracle E-Business Suite server URL. This URL represents the web entry point of your environment. By default, the web entry point is set to the hostname of the application server where Oracle E-Business Suite is installed. If a load-balancer is used, the web entry point becomes the load-balancer's hostname.

If the web entry point URL is not reachable, then users won't be able to connect. This applies to both desktop and mobile Users.

If your mobile users want to use Oracle E-Business Suite mobile apps from outside of your organization's firewall, your Oracle E-Business Suite environment must be set up in a DMZ configuration. Alternately, users may access the Oracle E-Business Suite mobile apps through an intranet connection such as a virtual private network (VPN).

DMZ access for mobile apps requires a mobile app client version of 1.1.0 or higher, with Oracle E-Business Suite Mobile Foundation Release 2.1 or later on the Oracle E-Business Suite server.

References

Related Articles

Monday Jul 13, 2015

Oracle Active Data Guard 11.2.0.4, 12.1.01 Certified with EBS 12.1.3

I'm pleased to announce the recent certification of Oracle Active Data Guard 11.2.0.4 and 12.1.0.1 with Oracle E-Business Suite 12.1.3.  Oracle E-Business Suite 12.1.3 certification with Oracle Active Data Guard 11.2.0.4 and 12.1.0.1 provides you the ability to offload some production reporting. We've certified the use of Oracle Discoverer and some Concurrent Manager reporting to run against the Oracle Active Data Guard database instance. 

Detailed steps for setting up Active Data Guard 11.2.0.4 or 12.1.0.1 with Oracle E-Business Suite 12.1.3 are provided in the following My Oracle Support Note:

In addition to Discoverer and Concurrent Manager, you may have other reporting tools that you would like to use with the Oracle Active Data Guard database instance.  In general, you should be able to use the reporting tool if it does not require write access to the Active Data Guard instance. 


Oracle E-Business Suite Active Data Guard Certifications

The following matrix provides an overview of what's currently certified and what's planned for Oracle E-Business Suite 12.2 and 12.1.3 and Oracle Active Data Guard 11.2.0.4, 12.1.0.1 and 12.1.0.2: 


 Active Data Guard 11.2.0.4
 Active Data Guard 12.1.0.1
 Active Data Guard 12.1.0.2
Oracle E-Business Suite 12.1.3
Certified*,MOS Note 1070491.1
Certified*, MOS Note 1070491.1
Pending certification**
Oracle E-Business Suite 12.2.3, 12.2.2
Certified*, MOS Note 1944539.1
Not currently planned for certification
Pending certification**
Oracle E-Business Suite 12.2.4 Pending Certification** Not currently planned for certification Pending certification**

  *For single node databases only.  Certification with Oracle RAC configurations is pending.

**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 the latest in cert.

How to Find the Latest Certification Information

This blog is great for announcing certifications as they happen, but for ongoing updates and the latest information on certifications, your single source of truth is the Certifications tab in My Oracle Support.  From the Certifications tab on My Oracle Support, you can search for certified combinations of products with specific Oracle E-Business Suite versions.  For example:

Step 1.  Log in to My Oracle Support

Step 2. Click on the Certifications tab

Step 3.  Add your search criteria.  For example:  Add Oracle E-Business Suite to the Product List, add Release 12.1.3 to the Release List and optionally add your platform to the Platform List.

Step 4.Click Check certifications with another product

Step 5.  Add Oracle Active Data Guard to the Product List and optionally add the version to the Release List

The above search will list all versions of Oracle Active Data Guard currently certified as shown in the following screenshot:

References

Related Articles

Thursday Jul 02, 2015

Oracle Data Guard 12.1.0.2 Certified with EBS 12.1.3

I'm pleased to announce the certification of Oracle Data Guard 12.1.0.2 with Oracle E-Business Suite 12.1.3.  Certification with Oracle Data Guard 12.1.0.2 provides you the ability to create a Physical Standby Database for Oracle E-Business Suite 12.1.3 environments.  The creation of a Physical Standby Database is a key component of creating a disaster recovery site for Oracle E-Business Suite.

Detailed steps for setting up a 12.1.0.2 Physical Standby Database for Oracle E-Business Suite 12.1.3 are provided in the following My Oracle Support Note:

Oracle E-Business Suite Data Guard Certifications

The following matrix provides an overview of what's currently certified and what's planned for Oracle E-Business Suite 12.1.3 and 12.2 and Oracle Data Guard 11.2.0.4 and 12.1.0.2:


Oracle Data Guard 11.2.0.4 Oracle Data Guard 12.1.0.2
Oracle E-Business Suite 12.1.3 Certified, MOS Note 1070033.1 Certified*, MOS Note 1900663.1
Oracle E-Business Suite 12.2 Certified*, MOS Note 1491855.1 Pending Certification**

*For single node databases only.  Certification with RAC configurations is pending .

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

How to Find the Latest Certification Information

This blog is great for announcing certifications as they happen, but for ongoing updates and the latest information on certifications, your single source of truth is the Certifications tab in My Oracle Support.  From the Certifications tab on My Oracle Support, you can search for certified combinations of products with specific Oracle E-Business Suite versions.  For example:

Step 1.  Log in to My Oracle Support

Step 2. Click on the Certifications tab

Step 3.  Add your search criteria.  For example:  Add Oracle E-Business Suite to the Product List, add Release 12.1.3 to the Release List and optionally add your platform to the Platform List.

Step 4.Click Check certifications with another product

Step 5.  Add Data Guard to the Product List and optionally add the version to the Release List

The above search will list all versions of data guard currently certified as shown in the following screenshot:


References

Related Articles

Thursday Jun 25, 2015

DB 12.1.0.2 Certified with EBS 12.1.3 on Linux on IBM System z

IBM logoOracle Database 12c Release 1 (12.1.0.2) is now certified with Oracle E-Business Suite Release 12.1 (12.1.3) on the following Linux on IBM System z operating systems as a 'database tier only' platform:

Release 12.1 (12.1.3 or higher):

  • 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 11 (64-bit)

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 (see My Oracle Support Certifications for more information). IBM's z systems fully support a mixed platform architecture with distributed Unix and Linux certified application tier servers for customers looking to run Oracle E-Business Suite on System z.
This announcement includes:

  • Oracle Database 12cR1 version 12.1.0.2
  • Oracle Database 12cR1 version 12.1.0.2 Real Application Clusters (RAC)
  • Oracle Database 12cR1 Version 12.1.0.2 Database In-Memory Option
  • Transparent Data Encryption (TDE) Column Encryption using Oracle Database 12cR1 version 12.1.0.2
  • Transparent Data Encryption (TDE) Tablespace Encryption using Oracle Database 12cR1 version 12.1.0.2
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 12cR1 version 12.1.0.2
  • Export/Import Process for Oracle E-Business Suite Release 12.0 or 12.1 with Oracle Database 12cR1 version 12.1.0.2

The following are not yet certified and will be announced on a later date once completed.

  • Oracle Multitenant 12cR1 version 12.1.0.2
  • Oracle Database Vault 12cR1 version 12.1.0.2
  • Transportable Database Data Migration Processes

References

Related Articles


Tuesday Jun 23, 2015

Using a Reverse Proxy as an SSL/TLS Termination Point for EBS 12.1.3

[Contributing Author:  Madhu Majari]

We are currently working on the certification of SHA-2 with the Oracle HTTP Server (OHS) delivered with Oracle E-Business Suite 12.1.3.  As described in this blog article, a reverse proxy or load balancer can be used until that certification is available.  You can use a reverse proxy or load balancer as the end-point for the encrypted connection that is initiated by a client (for example, a browser). In other words, the reverse proxy or load balancer -- not Oracle HTTP Server -- acts as the TLS termination point.

Since that article was published, many customers have requested that we certify a reverse proxy for use as the TLS termination point with Oracle E-Business Suite Release 12.1. I’m pleased to announce that we have completed the certification of HAProxy 1.5.2 with Oracle E-Business Suite 12.1.3. HAProxy is an open source offering that provides load balancing and proxy solutions.

The certification of HAProxy 1.5.2 with Oracle E-Business Suite 12.1.3 provides the following configuration options:

  • Certificates signed with SHA-2 for inbound HTTP connections
  • TLS 1.2 with stronger cipher suites

Note: There are many reverse proxies and load balancers that can be used as an TLS termination point for Oracle E-Business Suite. If you already have a reverse proxy or load balancer deployed you may configure it as the TLS termination point for your Oracle E-Business Suite 12.1.3 environment. 

Deploying and Configuring HAProxy

For detailed installation instructions, refer to the following My Oracle Support Knowledge Document:

You may deploy HAProxy as follows:

  • On an existing Oracle E-Business Suite application tier
  • On a separate server or virtual machine

HAProxy is available as an installable RPM package as part of the Oracle Linux distribution. You can also download HAProxy and compile it for other operating systems (refer to the installation note for more details). On Oracle Linux you may install it as the root user with the following command: 

#yum install haproxy

The main configuration file is located here:

/etc/haproxy/haproxy.cfg

A summary of the configuration steps for HAProxy includes the following:

  • Define the IP address and and port for the Oracle E-Business Suite 12.1.3 environment.
  • Setup TLS protocols and avoid SSL 3.0. (This will the mitigate POODLE vulnerability.)
  • Enable strong cipher suites. (This will mitigate the FREAK vulnerability.)
  • Define the certificate (chain) with PEM files.
Example Deployment of HAProxy with Oracle E-Business Suite 12.1.3

If you have an existing Oracle E-Business Suite 12.1.3 environment configured with SSL/TLS per Enabling SSL in Oracle E-Business Suite Release 12 (Note 376700.1), then you may easily configure HAProxy to serve as the TLS termination point.

For example, given the following conditions for your Oracle E-Business Suite Oracle HTTP Server listener configuration:

  1. HTTP requests use port 8000
  2. HTTPS requests use port 4443


 Then, you may perform the following:

  1. Shutdown the Oracle HTTP Server HTTPS listener (port 4443)
  2. Install, configure and start HAProxy to listen on port 4443

Related Articles

References

Tuesday Jun 16, 2015

DSTv24 Timezone Patches Available for E-Business Suite

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

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

Is Your Apps Environment Affected?

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

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

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

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

What Patches Are Required?

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

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

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

Friday Jun 12, 2015

Are We Replacing Workflow in EBS with BPEL Process Manager?

A customer asked, "When are you going to replace Oracle Workflow in the E-Business Suite with Oracle BPEL Process Manager?"

I thought that I'd covered this long ago, but it turns out that that's because I've answered it so often via email.  Here's our standard answer to that question.

Workflow is an essential and tightly-integrated part of the E-Business Suite.  It continues to grow in power and flexibility and is the foundation for our latest Mobile Approvals app. We have no plans to remove it or replace it with Oracle BPEL Process Manager (BPM).

Mobile Approvals app screenshot

If you'd like more background on the relationship between the version of Oracle Workflow that's embedded in the E-Business Suite and the standalone version, see this article:

How does Workflow compare to BPEL Process Manager? 

Workflow and BPM complement each other in environments that include EBS and other systems.  We position Workflow vs. BPM as follows:

  • Workflow is used within EBS for process orchestration between EBS products (e.g. between EBS Financials and EBS Procurement)
  • BPM is used for process orchestration between EBS and other systems (e.g. between EBS Financials and PeopleSoft)

Related Articles

Wednesday Jun 10, 2015

Does the Leap Second Affect the E-Business Suite?

Earth blue marbleBack in my salad days, I once took a university-level astronomy course, where I was surprised to learn that the earth's rotational speed varies due to climactic and geologic events.  These speed variations mean that the Coordinated Universal Time (UTC) occasionally needs to be adjusted by a leap second to remain synchronized with the mean solar time (UT1).

The next leap second is scheduled for June 30, 2015.

E-Business Suite users do not need to worry about the impact of leap seconds.  These time adjustment events do not have any impact on EBS operations or data integrity.


Tuesday May 19, 2015

Firefox ESR 38 Certified with EBS 12.2 and 11i

Firefox ESR logo

Mozilla Firefox 38 Extended Support Release (ESR) is certified as a Windows-based client browser for Oracle E-Business Suite 11i and 12.2.

The certification with EBS 12.1 is pending; see below.

What is Mozilla Firefox ESR?

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

What does the Mozilla Firefox ESR life cycle look like?

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

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

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

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

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

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

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

EBS patching policy for Firefox compatibility issues

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

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

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

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

Certified desktop operating systems
  • Windows 8.1 (32-bit and 64-bit)
  • Windows 7 SP1 (32-bit and 64-bit)
  • Windows Vista SP2

References

Pending Certification

The certification of Firefox ESR 38 with Oracle E-Business Suite 12.1 is still in progress. An interoperability patch is required for this certification; this patch is being prepared. 

EBS 12.1 users should remain on Firefox ESR 31 for now. This certification will be announced in a separate blog article.

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


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. 


Monday May 04, 2015

EBS 12.1 Certified on Oracle Linux 7 and Red Hat Enterprise Linux 7

Linux Tux logoOracle E-Business Suite Release 12.1 (12.1.3) is now certified on Oracle Linux 7 (64-bit) and Red Hat Enterprise Linux 7 (64-bit).

Installations of the E-Business Suite 12.1 on these operating systems require the application of the 12.1 RUP 3 (12.1.3). Cloning of existing EBS 12.1.3 Linux environments to these operating systems is also certified using the standard Rapid Clone process.

There are specific requirements to upgrade technology components such as the Oracle Database (to 11.2.0.4 or 12.1.0.2) and Fusion Middleware components as necessary. Other requirements, known issues, patches needed, etc. are noted in the Installation and Upgrade Notes (IUN) below and must be reviewed and implemented.

Pending Certifications

Certification of EBS Release 12.2 is in progress and will be announced at a later time when completed.

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

References

Wednesday Apr 29, 2015

Database Migration Using 12cR1 Transportable Tablespaces Now Certified for EBS 12.1.3

As a follow up to a prior announcement, database migration across platforms of different "endian" or byte ordering formats using the Transportable Tablespaces (TTS) process is now certified for Oracle E-Business Suite Release R12 (12.1.3) with Oracle Database 12c Release 1 (12.1.0) as both the source and target database. The previous announcement covered the use of 11gR2 as the source and 12cR1 as the target database.

Furthermore, this TTS migration process uses the new 12c feature of full transportable export/import to move the entire database to further speed up the migration process. Also, users have the option to use cross platform incremental backup, a way to minimize database downtime and data transfer times.

This migration process requires a patch delivered by EBS Development that is 'Controlled', i.e. it requires a password obtainable through Oracle Support subject to approval. We released the required patch in this manner to assess suitability, potentially monitor customer issues due to the nature of this technology and to gauge uptake.

 The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba):

    SQL> select platform_name, endian_format from v$transportable_platform;

Here's a list of relevant platforms certified for the EBS R12 with 12cR1 on the database tier:

 Big Endian Platforms
 Little Endian Platforms
 Oracle Solaris on SPARC
 Linux x86-64
 HP-UX Itanium
 Oracle Solaris on x86-64
 IBM AIX on Power Systems
 MS Windows x64

For more information, please review the following:

Related Articles


Wednesday Apr 22, 2015

Quarterly EBS Upgrade Recommendations: April 2015 Edition

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

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

You can research these yourself using this Note:

Upgrade Recommendations for April 2015

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related Articles

Tuesday Apr 21, 2015

Best Practices for Testing EBS Endeca Applications

[Editor: This article was contributed by Prasanti Madireddi, Sr. Director, EBS Quality Assurance]

We introduced Oracle E-Business Suite Extensions for Oracle Endeca in 2013.  These EBS Extensions  provide selected EBS applications with Oracle Endeca-based capabilities. What is the best approach for testing your Endeca-based content for the E-Business Suite?

Endeca screenshot

Overall testing strategy

The primary goal is to test Endeca's integration with the EBS application. Customers should be able to use EBS products alongside the Endeca search features to search and summarize EBS data. 

Testing access to Endeca Applications

You must complete Endeca's role based access control (RBAC) before testing Endeca applications. You must create users, responsibilities and roles after the Endeca installation. After the RBAC setup is run, users can open Endeca pages and search for EBS data.

Testing Endeca integration with EBS products

Open Endeca pages from EBS. Verify the navigation from Endeca pages to self service pages and other windows, and also check the navigation back to the Endeca pages. Verify if the context is being set appropriately while navigating from one page to another.

Test key flows

Test all key flows in the Endeca products that you've integrated with the E-Business Suite. For example, if you've installed the Endeca extensions for iProcurement, the key flow in Oracle iProcurement would be to search for items in the Endeca page, compare the items, select some items and add them to cart and create a requisition.

Test data synchronization

Endeca maintains its own operational data store.  This database needs to be synchronized with the E-Business Suite database. Data synchronization is key to the functioning of Endeca pages. Run the full data synchronization for your installed Endeca extensions and verify that the data is loaded appropriately. Open Endeca pages to verify that the synchronized data is accurate and is displayed properly.

Some of the products control the data to be loaded through a profile option wherein a cut-off date can be specified. The full load process pulls in data entered after the cut-off date specified.

For example: in the Project Procurement - Supplier & Item Analysis dashboard, you can use the profile "PO: Item and Supplier Analysis Data-load Cut-off" to restrict the data that is sent to Endeca.

Test your full load processes to verify that the data is synchronized based on product-specific profiles.

You can run the Incremental Synchronization tools to keep the Endeca database updated after new changes have been made to the EBS database. Test this by creating, updating, or deleting data from EBS and then running the incremental graph to verify that the changes are reflected in Endeca pages.

Test all search components and capabilities

Endeca provides several options for filtering and searching data.

  • Search Box
  • Breadcrumbs
  • Guided Navigation
  • Range Filters
  • Tag Cloud
  • Book Marks

Use these search features to verify that your data is filtered appropriately.  Choose a small well-defined set of data for testing.

After you enter the search criteria, check that all Endeca components are refreshed appropriately with the queried data. This includes metric bars, result tables, record details and charts.

Most components have additional search capabilities, e.g. clicking on a value in a chart will further filter the data based on the clicked value. Check that those additional search features also show the latest synchronized data.

Additional Features

Endeca provides additional features: Metrics, Compare, and Export. The Metrics component provides a summary of the selected data. This component can be configured to highlight the data in different colors based on some specific conditions.  Test Metrics to verify the accuracy and the format of the summarized data.

The Compare feature is used to compare two objects, for example, to compare two items before adding them to a cart in iProcurement. Test the Compare feature to verify that the selected objects are compared appropriately.

Test the Export option to verify that the displayed data can be exported and saved in Excel spreadsheets.

Security Testing

Test your RBAC setup by verifying that only authorized users can access Endeca pages.

Test your RBAC setup by verifying that only authorized users can see the data that they're authorized to access in Endeca. For example, if a user is allowed to see data from Organization A but not  Organization B, verify that the appropriate Endeca pages also honor this data security check.

Descriptive Flex fields

Descriptive Flex fields (DFF) provide customizable expansion space on the EBS Endeca user interfaces and are used to track additional information. Endeca allows users to search on DFF attributes.

Test DFFs by creating new DFF definitions and then running the full load process to populate the DFF details. Search for the DFF values in the guided navigation.

Browser and mobile device compatibility

Test Endeca pages in the certified browsers that you've deployed in your organization.

Endeca pages should open in desktop clients, tablets, and mobile devices. Some components behave differently when opened in mobile devices. For example, the Guided Navigator is not rendered automatically in tablets and mobile devices; users open the Guided Navigator by clicking a button.

References

Thursday Apr 16, 2015

JRE 1.8.0_45 Certified with Oracle E-Business Suite

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

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

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

No.

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

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

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

References

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


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

Java logo

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in this release?

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

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

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

Worried about the 'mismanaged session cookie' issue?

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

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Java JRE 1.6.0_95 Certified with Oracle E-Business Suite

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

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in in this Java release?

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

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

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

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

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Wednesday Apr 15, 2015

Critical Patch Update for April 2015 Now Available

The  Critical Patch Update (CPU) for April 2015 was released on April 14, 2015.  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 14, 2015
  • October 20, 2015
  • January 19, 2016
  • April 19, 2016
E-Business Suite Releases 11i and 12 Reference
About

Search

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