Monday Feb 22, 2016

Rapid Install StartCD 51 for EBS 12.2 Now Available

We are pleased to announce the availability of Oracle E-Business Suite StartCD 12.2.0.51 (often just called StartCD 51). As the fundamental installation medium for EBS, the startCD is what you begin with when installing or upgrading to Release 12.2.

This latest startCD includes many important updates and fixes, as described in the README for the patch by which it is supplied. Obtaining startCD 51 is highly recommended for all customers who will use Rapid Install to perform an installation or upgrade to Release 12.2.

startCD 51

How Can I Obtain startCD 12.2.0.51?

  • You can download startCD 51 as Patch 22066363.

What's New in this Update?

Among other enhancements, startCD version 12.2.0.51:

  • Includes important fixes for fresh install and upgrade scenarios
  • Introduces EBS use of Oracle Database 12cR1 (12.1.0.2)
  • Introduces EBS use of Oracle Fusion Middleware Web Tier Utilities 11.1.1.9.0
  • Installs additional technology stack patches for Oracle Database 11g and Fusion Middleware

Do I Need A New Stage Area For startCD 12.2.0.51?

Yes, you must create a new stage area to use startCD 12.2.0.51. A stage area created with an earlier startCD will not work. This is because (as noted above) startCD 12.2.0.51 uses Oracle Database 12cR1 (12.1.0.2), while earlier startCDs used 11gR1 (11.2.0.3). In addition, startCD 12.2.0.51 uses a later patch set (11.1.1.9.0)  of Oracle Fusion Middleware Web Tier Utilities than the 11.1.1.7.0 patch set used by earlier startCDs.

How Can I Obtain Oracle Database 12.1.0.2 and Oracle Web Tier Utilities 11.1.1.9.0?

You can download Oracle Database 12.1.0.2 and Oracle Web Tier Utilities 11.1.1.9.0 from the Oracle Software Delivery Cloud as part of the Release 12.2.5 media:

  • Go to the Oracle Software Delivery Cloud and search for Oracle Financials for your platform (EBS is not shown as a product option, so you need to choose a listed product such as Financials).
  • Under Release 12.2.5, download the Zip files for "Oracle Database 12.1.0.2" and "Oracle Web Tier Utilities 11.1.1.9.0".

startCD 51 extras

Where Can I Find More Information About Installing EBS?

Refer to the following Release 12.2 Web Library book for more information about creating the stage area, other installation prerequisites, and the various available installation actions and options:

  • Oracle E-Business Suite Installation Guide: Using Rapid Install (Part No. E22950) (PDF or HTML)

References

As well as the Installation Guide mentioned above, you should refer to the following My Oracle Support knowledge documents as applicable:

Related Articles

Thursday Feb 18, 2016

Do E-Business Suite Users Need to Worry About Java 9?

No, Oracle E-Business Suite users do not need to worry about changes coming in Java 9. The Java team recently published their plans for removing the Java browser plugin in a future version of Java. The announcement states (key words highlighted for emphasis):

Oracle plans to deprecate the Java browser plugin in JDK 9. This technology will be removed from the Oracle JDK and JRE in a future Java SE release.

What does "deprecate" mean?

"Deprecate" means that there will still be a JRE 9 browser plug-in. Users will still be able to run Java-based applications using the JRE 9 browser plug-in.

What does this mean for E-Business Suite users running JRE 9?

The release of Java 9 will not have any effect on E-Business Suite users. JRE 9 will continue to work with the E-Business Suite in browsers that support Java (via the NPAPI protocol). 

What browsers will support the JRE 9 plug-in?

Internet Explorer, Firefox ESR, and Safari will continue to support NPAPI -- and, therefore, Java and Forms.  We recommend that customers who need to use Forms-based products in the E-Business Suite use those browsers.

Alphabet (Google) Chrome and Microsoft Edge do not support NPAPI, so Java-based apps cannot run in those browsers.  

Will E-Business Suite still require Java?

Yes.  Our ongoing use of Forms for high-volume professional users of the E-Business Suite means that power users will continue to have a need to run Java.  We replicate, simplify, or migrate selected Forms-based flows to OA Framework-based (i.e. web-based HTML) equivalents with every EBS update, but I would imagine that Forms will continue to be part of the E-Business Suite technology stack for the foreseeable future.  I expect that this will apply to both the EBS 12.1 and 12.2 release streams.

Will E-Business Suite change how it starts Java?

Yes, it's very likely. We're working on what happens in the "future Java SE release" that follows Java 9.  We are actively reviewing options for future updates to Java, EBS, and Forms to address Forms compatibility via Java Web Start right now. 

Oracle will do everything possible to ensure that customers can continue to run all parts of the E-Business Suite.

When will EBS do this?

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

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.

Thursday Feb 11, 2016

ETCC Tool Enhanced for Finding Mandatory EBS 12.2 Patches

Contributing author: Paul Holman

The E-Business Suite Technology Codelevel Checker (ETCC) tool has been provided to help you identify missing database or middle tier patches that may need to be applied to your E-Business Suite Release 12.2 system.

The utility has now been significantly enhanced to map bug fixes to patches, generating a Patch Recommendation Summary that lists the patches (including versions and associated filenames) that are required for your system.

The following example shows part of an ETCC run, where the DB-ETCC script is used to identify missing database patches.

DB-ETCC Example

Why Does This Matter?

As the last section of the above example shows, there is a difference between bug fixes and patches. A bug fix ID for an issue does not change, but the patch ID that delivers the fix might: for example, the original patch could be superseded by another patch. So you need to not only know what bug fix you require, but which patch currently delivers it.

With previous versions of ETCC, the relevant patches (including Patch Set Updates and Exadata patches) had to be identified manually, by referring to the relevant documentation.  In this latest version, bug fix to patch mapping is done for you, avoiding the need for manual identification and the risk of misidentifying the patch needed. That is the principal enhancement in this version of ETCC.

Coverage

This new version of ETCC maps missing bug fixes to corresponding patches for the latest and latest but one quarterly bundles supported by EBS 12.2. You can use this version of ETCC with older bundles, but it will only list missing bug fixes (as previous versions did), and you will see a message saying "Patch mapping not available".

Obtaining ETCC

The ETCC utility can be downloaded via Patch 17537119 from My Oracle Support.

References

Related Articles


Monday Feb 08, 2016

JRE 1.8.0_73/74 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_73 (a.k.a. JRE 8u73-b2) and JRE 1.8.0_74 (8u74-b2) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 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?

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

  • CPU Release:  JRE 1.8.0_73
  • PSU Release:  JRE 1.8.0_74

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

Internet Explorer users are advised to upgrade to the JRE 1.8.0_74 rather than JRE 1.8.0_73 due to a known performance issue.

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

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.

Known Iusses

Internet Explorer Performance Issue

Launching JRE 1.8.0_73 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_74.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue

Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles

JRE 1.7.0_97 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_97 (a.k.a. JRE 7u97-b2) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 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 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?

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:

Known Issues

When using Internet Explorer, JRE 1.7.0_01 had a delay of around 20 seconds before the applet started to load. This issue is fixed in JRE 1.7.0_95.

References

Related Articles

JRE 1.6.0_113 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_113 (a.k.a. JRE 6u113-b1) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 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

Friday Jan 22, 2016

Configuring Oracle XML Gateway for TLS

Oracle XML Gateway uses Oracle Transport Agent (OTA) - a lightweight messaging platform to transmit XML-based business transaction messages over HTTP and Secure HTTP (HTTPS) with trading partners. In general, it supports Server and Mutual Authentication mechanisms for inbound and outbound transactions over HTTPS.  Oracle XML Gateway now supports SHA-2 signed certificates and TLS protocol for XML-based transactions in Oracle E-Business Suite 12.1 and 12.2.

Diagram showing message flow protocols

Oracle E-Business Suite Release 12.2

For information on configuring Oracle XML Gateway for SSL/TLS in Oracle E-Business Suite Release 12.2, see:

Outbound transactions in Oracle E-Business Suite Release 12.2.3 and 12.2.4 require a patch; see the documentation for details.

Outbound transactions in Oracle E-Business Suite Release 12.2.5 and later EBS 12.2 updates do not require any additional patches.

Oracle E-Business Suite Release 12.1

For information on configuring Oracle XML Gateway for SSL/TLS in Oracle E-Business Suite Release 12.1.3, see:

References

Related Articles

Thursday Jan 21, 2016

January 2016 Updates to AD and TXK for EBS 12.2

We have been fine-tuning the administration tools for E-Business Suite 12.2 via a series of regular updates to the Applications DBA (AD) and EBS Technology Stack (TXK) components:

We have now made available an eighth set of critical updates to AD and TXK. If you are on Oracle E-Business Suite Release 12.2, we strongly recommend that you apply both of these two newly-released patch collections at your earliest convenience:

They can be downloaded from My Oracle Support, as shown by this example for AD:

Refer to the following My Oracle Support knowledge document for full installation instructions and associated tasks:

Why should I apply these updates?

These updates provide the latest codelevels for AD-TXK. A codelevel is a collection of patches that implements and provides fixes for a set of features associated with a point release of an EBS product. Codelevels are cumulative, with each subsequent one including the features and fixes in each of its predecessors.

There are several important reasons you should adopt this latest AD-TXK codelevel:

  • It includes a number of significant fixes and improvements.
  • New patches to implement code fixes can only be applied to the latest AD-TXK codelevel.
  • No new code fixes are created for earlier AD-TXK codelevels.
Note that it is essential to keep your AD and TXK codelevels synchronized: that is, you must apply both AD.C.Delta.7 and TXK.C.Delta.7, rather than just one of them.

What's New in this Patchset?

  • Support for database password case sensitivity added to the XDF utilities
  • Application short name length increase to 9 characters in ADSPLICE
  • New ADOP Apply failure validations added to the ADOP phases: Prepare, FS_CLONE, Cleanup and Finalize
  • New validation to the Finalize phase to detect FCET execution failures when column changes are introduced by a patch
  • Improvements to ADOP FS_CLONE restartability
  • New algorithm to identify and preserve non-editioned schema connections during the ADOP Cutover phase execution
  • Rapid clone pairs file support for Windows 64-bit

For a more-detailed list, see Section 6 in:

Related Articles

Wednesday Jan 20, 2016

JRE 1.8.0_71/72 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_71 (a.k.a. JRE 8u71-b15) and JRE 1.8.0_72 (8u66-b15) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 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?

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

  • CPU Release:  JRE 1.8.0_71
  • PSU Release:  JRE 1.8.0_72

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

Internet Explorer users are advised to upgrade to the JRE 1.8.0_72 rather than JRE 1.8.0_71 due to a known performance issue.

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

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.

Known Iusses

Internet Explorer Performance Issue

Launching JRE 1.8.0_71 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_72.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue

Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles

JRE 1.7.0_95 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_95 (a.k.a. JRE 7u95-b14) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 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 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?

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:

Known Issues

When using Internet Explorer, JRE 1.7.0_01 had a delay of around 20 seconds before the applet started to load. This issue is fixed in JRE 1.7.0_95.

References

Related Articles

JRE 1.6.0_111 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_111 (a.k.a. JRE 6u111-b12) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 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

Tuesday Jan 19, 2016

Critical Patch Update for January 2016 Now Available

The  Critical Patch Update (CPU) for January 2016 was released on January 19, 2016.  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 19, 2016
  • July 19, 2016
  • October 18, 2016
  • January 17, 2017
E-Business Suite Releases 11i and 12 Reference

Thursday Jan 14, 2016

Oracle Traffic Director Certified with EBS 12.2 on Exalogic

I'm pleased to announce that Oracle Traffic Director 11gR1 (11.1.1.9) is now certified with Oracle E-Business Suite 12.2 on Oracle Exalogic.

Oracle Traffic Director with Oracle E-Business Suite 12.2 on Exalogic may be configured as follows:
  • as a reverse proxy and load balancer
  • as a TLS accelerator and termination point
  • in DMZ configurations

You may also optionally utilize Oracle Traffic Director features such as content caching and HTTP compression.

For more information regarding Oracle Traffic Director, see:

Deploying and Configuring OTD with EBS 12.2 on Exalogic

For detailed installation and configuration instructions, see:

Related Articles

References

Tuesday Jan 05, 2016

2015 in Review: 13 Things That You Must Upgrade Now

2015 was a busy year for E-Business Suite system administrators.  The following things are now considered to be out of Error Correction Support by Oracle or their respective vendors:

Database Tier

  1. Database 10g Release 2 (ended July 2015)
  2. Database 11g Release 1 (ended August 2015)
  3. Database 12.1.0.1 Patchset (ended July 2015)
  4. Database 11.2.0.3 Patchset (ended August 2015)

Application Tier

  1. Oracle Access Manager / Oracle Internet Directory 11.1.1.5 (ended June 2015)
  2. SHA-1 PKI certificates
  3. Secure Socket Layer (SSL)
Client Tier
  1. Internet Explorer (IE) 6, 7, 8, 9, 10 (ended January 2016)
  2. All JRE releases older than 1.6.0_105, 1.7.0_91, and 1.8.0_66

EBS Releases

  1. EBS 11i (Exception to Sustaining Support ended December 2015)
  2. EBS 12.0 (ended January 2015)
  3. EBS 12.1 Recommended Patch Collection 3
  4. EBS 12.2.2 Release Update Pack

What you should do

If you are running any of the things above in your EBS environments, you should click on the respective links to get guidance on your upgrade options. Oracle strongly recommends that you stay on a current product release that gets updates.

If you're confused by the continued listing of a particular combination in Oracle's Certification database after the product release's end of life, see:

Related Articles

Monday Dec 21, 2015

Now Automated: Integrating EBS 12.1 with Oracle Access Manager 11gR2

Contributing Author:  Allison Sparshott

Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate for single sign-on requires the execution of a number of integration steps. The steps can be rather time consuming to perform and tedious to execute manually.

We are pleased to announce that Oracle E-Business Suite Release 12 (12.1.3+) can now be integrated with Oracle Access Manager 11g Release 2 (11.1.2.3.0) using new scripts to facilitate and automate the required integration steps.

The new integration automation scripts can be used to perform a number of the steps that previously needed to be executed manually. The following can be performed when using the integration automation scripts:

  • Configuring Oracle Access Manager WebGate
  • Deploying Oracle E-Business Suite AccessGate
  • Registering Oracle E-Business Suite with Oracle Access Manager.

For information on how to use the automation scripts to integrate Oracle E-Business Suite Release 12 (12.1.3+) with Oracle Access Manager 11gR2 (11.1.2), refer to the following My Oracle Support document:

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.

Note:  Microsoft Windows is not currently certified with the integration automation scripts.

References

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

Related Articles

Friday Dec 18, 2015

Platform Migration Certified for EBS 12.2 Application Tiers

We are pleased to announce that application tier migration for Oracle E-Business Suite Release 12.2 is now certified. You can now migrate an existing EBS 12.2 application (middle) tier server to any other Unix/Linux platform certified for EBS 12.2.  These platform migrations preserve patch levels, configurations, customizations, etc.

The E-Business Suite 12.2 application tier migration process requires EBS Release 12.2.3 or later updates to the 12.2 codeline. This documented process outlines only the process for an application tier migration:

What about application tier servers on the same platform?

For application tier migrations between systems of the same platform, you should follow the Rapid Clone process documented in this Note:

What about database tier platform migrations?

Database tier migration should be considered separately. For migration of the database tier, refer to the 'Database Migrations and Upgrades' section in this Note:

Related Articles

Tuesday Dec 15, 2015

Reminder: Error Correction Support Ended for Database 11.2.0.3

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ended for the 11.2.0.3 Database patchset on August 27, 2015

All EBS customers should upgrade to a later patchset or database release.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles

Monday Dec 14, 2015

Microsoft Office 2016 Certified with E-Business Suite 12.2

We are pleased to announce that Microsoft Office 2013  logoMicrosoft Office 2016 is certified with Oracle E-Business Suite Release 12.2.  For details, see:

This certification covers Office running in 32-bit and 64-bit mode.

Microsoft Office 2016 desktop version is certified for integration with Oracle E-Business Suite Releases 12.1.3 for the following desktop client operating systems:

  • Windows 7 32-bit & 64-bit
  • Windows 8.1 32-bit & 64-bit
  • Windows 10 32-bit & 64-bit
How does the E-Business Suite work with Microsoft Office?

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

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

Examples of these integrations include:

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

We explicitly tested the Office 2016 Professional edition with Oracle E-Business Suite.  We expect that the results of these certification tests apply equally to other desktop-installed editions.

Support implications: We will attempt to reproduce issues reported on other editions on our reference edition -- Office 2016 Professional.  Issues that cannot be reproduced will be handled on a case-by-case basis.  For example, issues that can only be reproduced on, say, Office Home & Student 2016 but cannot be reproduced on Office Professional 2016 will be handled on a case-by-case basis. 

What about OpenOffice, StarOffice, LibreOffice?

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

Related Articles

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 Dec 11, 2015

Oracle Unified Directory 11.1.2.3 Certified with EBS 12.2

Oracle Unified Directory 11gR2 Patchset 3 (11.1.2.3) is now certified with E-Business Suite 12.2.  Oracle Unified Directory can be used when enabling single sign-on capabilities for the E-Business Suite via Oracle Access Manager 11gR2.

This certification also includes Directory Integration Platform 11gR1 Patchset 7 (11.1.1.9), which is used to synchronize users between OUD and the E-Business Suite.  

See:

How does this relate to Oracle Internet Directory?

EBS 12.2 users now have the option of using either Oracle Internet Directory or Oracle Unified Directory when enabling single sign-on in their environments. 

Which one should I use?

From the perspective on an E-Business Suite end-user, both directories offer the same functionality, namely, end-users can log on to the E-Business Suite.  The choice really depends upon your user directory administrators.  You should use the one that meets your user administration requirements the best.

Here are the options.  If you're:

  • Running EBS 12.1, you can only use Oracle Internet Directory
  • Running EBS 12.2: you can use Oracle Internet Directory or Oracle Unified Directory

Do I need to switch from OID to OUD?

No.  You can continue to use Oracle Internet Directory with EBS 12.1 and 12.2.  There is no need to switch from Oracle Internet Directory to Oracle Unified Directory.

Can I eliminate both OID and OUD?

No.  When integrating E-Business Suite with Oracle Access Manager, EBS has hardcoded dependencies that require either OID or OUD.  You must have one of these two directories.

This article discusses OID but applies equally to OUD now.  The same technical dependencies exist for Oracle Unified Directory and Oracle Internet Directory when integrating the E-Business Suite with Oracle Access Manager. 

Certified Platforms

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

Integration with Oracle Unified 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. 

Related Articles


Thursday Dec 10, 2015

Configuring Oracle Workflow with Cloud E-Mail Servers

It is now possible to configure Oracle Workflow Notification Mailer with any cloud-based email server that supports SSL/TLS protocols.  This includes cloud-based email servers such as Microsoft Office 365 and GMail. You can configure cloud-based SMTP and IMAP email servers to handle inbound and outbound Workflow mailer processing. 

Patches are available for E-Business Suite Release 12.1.3 and 12.2.  For complete details, see:

Workflow Office 365 Gmail setup table

The notification mailer configuration wizard within Oracle Applications Manager currently does not support these new security protocol parameters, so you must perform the required configuration steps manually. You should configure outbound processing for your notification mailer first, and then configure inbound processing.

After you configure a notification mailer to use a cloud e-mail server, you must no longer use the notification mailer configuration wizard for that mailer. Instead, continue using the manual configuration scripts to update the mailer configuration as needed.

Related Articles

Wednesday Dec 09, 2015

Reminder: EBS 11i Reverts to Sustaining Support on January 1, 2016

E-Business Suite 11.5.10.2 has been in Sustaining Support since December 1, 2013.  We have offered a one-time Exception to Sustaining Support (covering only Severity 1 issues) until December 31, 2015. 

This means that we will revert to Sustaining Support for Oracle E-Business Suite 11i 11.5.10.2 on January 1, 2016.  See:

Updated EBS Support timelines

EBS 11i users should upgrade to EBS 12.2 as soon as possible.

What happens after Extended Support ends?

The Exception to Sustaining Support coverage ends and we revert to the normal mode of Sustaining Support on January 1, 2016.  You can request diagnostic assistance for EBS 11i issues and download existing patches and documentation. Sustaining Support does not include:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For more specifics on Premier Support, Extended Support, and Sustaining Support, see:

Implications for EBS 11i users

You may need to freeze your desktop and server configurations while you upgrade to EBS 12.2. 

New versions of desktop components may not work with EBS 11i. These include new releases of:

  • Windows
  • Mac OS X
  • Internet Explorer (IE)
  • Firefox
  • Safari
  • Office
  • Desktop-based Java Runtime Environment (JRE)  

New versions of server-based components may not work with EBS 11i. 

These include new releases of:

  • Server-based operating systems (Linux, AIX, HP-UX, Solaris, etc.)
  • Oracle Database
  • Java JDK
  • Fusion Middleware components (Oracle HTTP Server, JServ, Forms, etc.)

Related Articles

Tuesday Dec 08, 2015

Updated: EBS Upgrade Performance Diagnostics White Paper

We've updated our white paper that describes methods and tools for diagnosing performance-related issues with your EBS 12.x upgrades:

This is a companion Note to:

Both Notes are written by by Jim Machin, a senior member of our Applications Performance group. The companion Note describes a framework and tools for obtaining:

  • Actual statistics: So that you can see exactly which execution plan steps are inefficient, rather than those that you think might be inefficient. You can also estimate the likely impact of a performance fix.
  • Diagnostics that are quick and easy to run, so that you can obtain diagnostics on more jobs/SQL, and obtain them faster.
  • Diagnostics that have very little impact on the performance of the Release 12 upgrade: if they can be run during the upgrade, you will get the diagnostics sooner and be able to resolve the issue more quickly.

There is an extensive range of diagnostics available, which include:

  • Identifying the top SQL in cursor cache or AWR
  • Displaying cursor reports for long-running SQL
  • Matching long-running SQL to jobs
  • Reporting on CBO statistics for all EBS tables
  • Reviewing the AD job timing report
  • Identifying long-running upgrade jobs
  • Specific diagnostics for Online Patching enablement performance

This white paper is updated regularly with new tips and recommendations based upon our Application Performance group's work with actual EBS 12.2 customers and their Service Requests.  All EBS 12.2 sysadmins should monitor this white paper regularly.

Related Articles

Monday Dec 07, 2015

Updated: Minimizing EBS 12.2 Upgrade Downtimes White Paper

We have updated our recommendations for minimizing downtimes when upgrading to EBS 12.2:

Written by Jim Machin, a senior member of our Applications Performance group, this white paper contains a wealth of detailed technical recommendations for reducing the amount of time needed for an EBS 12.2 upgrade. 

Events vs. sessions bottlenecks diagram

It covers:

  • Technical preparation and planning activities
  • Diagnostics for monitoring and troubleshooting performance issues
  • Common solutions to performance issues
  • Oracle Applications Tablespace Model (OATM) considerations
  • Methods for purging old data
  • Gathering statistics
  • Detailed recommendations for improving resource management, sizing, and workloads

This white paper is updated regularly with new tips and recommendations based upon our Application Performance group's work with actual EBS 12.2 customers and their Service Requests.  All EBS 12.2 sysadmins should monitor this white paper regularly.

Related Articles

Friday Dec 04, 2015

Reminder: Upgrade to IE 11 Before January 12, 2016

Microsoft IE LogoMicrosoft has published this reminder to all customers:

Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical supports (sic) and security updates. Internet Explorer 11 is the last version of Internet Explorer, and will continue to receive security updates, compatibility fixes, and technical support on Windows 7, Windows 8.1, and Windows 10.

What does this mean for EBS users?

This notice applies to all Oracle E-Business Suite users.  After January 12, 2016, Oracle will no longer certify older versions of IE with any updates to Oracle E-Business Suite, including EBS releases 11i, 12.0, 12.1, and 12.2.

All EBS customers must follow Microsoft's guidance and upgrade to IE 11. See:

What are the EBS support implications of staying on an older IE version?

You will continue to have access to existing EBS patches and documentation for older IE releases via My Oracle Support.

Oracle may attempt to assist with questions about older IE releases.  Oracle's ability to assist may be limited by lack of access to desktops running those older releases.

Oracle will issue new patches only for issues that can be reproduced on IE 11.

References

Related Articles

Monday Nov 30, 2015

Database 11.2.0.4 Certified with HP-UX and EBS 12.1.3

HP logoAs a follow up to the prior announcements on November 20th 2013, Oracle Database 11g Release 2 (11.2.0.4) is now certified with Oracle E-Business Suite Release 12.1.1 or later updates to the 12.1 code line on the following additional platform:

  • HP-UX PA-RISC (64-bit) (11.31)
This announcement for Oracle E-Business Suite R12 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 12 Database Instances
  • Transportable

References

Related Articles



Thursday Nov 26, 2015

SHA-2 PKI Certificates Certified with EBS 12.1.3 on Windows

As a follow-up to a prior announcement, SHA-2 signed PKI certificates are now certified for inbound connections to the Oracle HTTP Server (OHS) delivered with Oracle E-Business Suite 12.1.3 on Windows.  

As published in a prior blog article, SHA-2 signed PKI certificates are already certified for outbound connections from Oracle E-Business Suite 12.1.3.

Required Steps

If you are enabling SSL/TLS for the first time for Oracle E-Business Suite 12.1.3, refer to the following for all prerequisite requirements and post steps:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 3 (Note 376700.1)

If you have already enabled SSL or TLS and are updating to a SHA-2 signed PKI certificate with the OHS for Oracle E-Business Suite 12.1.3, refer to the following for all prerequisite requirements and post steps:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 11 (Note 376700.1)

Overview of the Requirements

The following is a summary of the requirements for deploying a SHA-2 signed PKI certificate for inbound connections to the OHS for Oracle E-Business Suite 12.1.3 include the following:

  • Update OPatch

If you have not already updated to the OPatch 9i, 10.1 version 1.0.0.0.63 or later, download and install it. For the latest OPatch information, refer to the following:

OPatch for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4), (Note 283367.1)
  • Apply the minimum required patch level for the Oracle Fusion Middleware 10.1.3 Oracle Home

The minimum requirement is to upgrade the Oracle Fusion Middleware 10.1.3 Oracle Home to 10.1.3.5 per the following:

Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12 (Note 454811.1)

  • Apply the October 2015 CPU to the Oracle Fusion Middleware 10.1.3 Oracle Home

The minimum CPU requirement for the Oracle Fusion Middleware 10.1.3.5 is the October 2015 CPU level (Patch 21845960) per the following:

Oracle E-Business Suite Releases 11i and 12 Critical Patch Update Knowledge Document (October 2015) (Note 2051000.1)

Note: Testing is performed with all CPU patches applied across the technology stack components and the Oracle E-Business Suite. It is possible to apply the October 2015 CPU (Patch 21845960) to FMW 10g without applying the Oracle E-Business Suite October 2015 CPU or Oracle Database October 2015 CPU/PSU; however, we recommend that customers apply the latest CPU across all technology stack components and the Oracle E-Business Suite.

  • Apply platform-related patch to the Oracle Fusion Middleware 10.1.3 Oracle Home

For Windows, apply patch 22251660 to the Oracle Fusion Middleware 10.1.3.5 Oracle Home.

  • Perform all necessary post steps.

Post steps include generating the CSR to obtain the SHA-2 signed PKI certificate from your certificate authority (CA). Once you have the certificate, you will import it using Oracle Wallet.

Refer to the appropriate section in the following My Oracle Support note for the complete list of post-steps for your environment:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 11 (Note 376700.1)

Pending Platform Certifications

None. All platforms are now certified.

References

Related Articles

Wednesday Nov 25, 2015

WebCenter Portal 11.1.1.9 Certified with E-Business Suite 12.2

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

WebCenter Development Framework

WebCenter Portal 11.1.1.9 is now certified with Oracle E-Business Suite Release 12.2.  WebCenter Portal 11.1.1.9 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.9.0, also known as FMW 11gR1 Patchset 8. 

Certified Platforms

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

Integration with Oracle WebCenter Portal 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.

Migrating to Oracle WebCenter

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

References

Related Articles

Tuesday Nov 24, 2015

How to Download Oracle E-Business Suite Release 12.2.5

Oracle E-Business Suite Release 12.2.5 was released in October 2015. This consolidated, suite-wide release update pack includes:

  • New features
  • Statutory and regulatory updates
  • Stability, performance, and security enhancements

Like other recent EBS releases, 12.2.5 is available by download from the Oracle Software Delivery Cloud (OSDC). Unlike with earlier releases, however, you do not specify EBS itself as a product to download. Here's what to do instead:

  1. Specify an EBS product you'll be using. For example, you might choose Oracle Financials.
  2. Go on to specify your platform, such as Linux x86-64.
  3. OSDC will display the EBS software distribution for the product you specified.
  4. Accept the license agreements.
  5. OSDC displays the appropriate Zip files for you to download.

OSDC

Note: You only need to specify one Oracle E-Business Suite product, even if you are going to use more than one.

References

  • Oracle E-Business Suite Installation Guide: Using Rapid Install, Release 12.2 (Part No. E22950-22), available from the Release 12.2 Web Library in PDF and HTML formats

Related Articles

Monday Nov 23, 2015

SHA-2 PKI Certificates Certified with EBS 12.1.3 on AIX and Itanium

As a follow-up to a prior announcement, SHA-2 signed PKI certificates are now certified for inbound connections to the Oracle HTTP Server (OHS) delivered with Oracle E-Business Suite 12.1.3 on AIX and Itanium.  

As published in a prior blog article, SHA-2 signed PKI certificates are already certified for outbound connections from Oracle E-Business Suite 12.1.3.

Required Steps

If you are enabling SSL/TLS for the first time for Oracle E-Business Suite 12.1.3, refer to the following for all prerequisite requirements and post steps:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 3 (Note 376700.1)

If you have already enabled SSL or TLS and are updating to a SHA-2 signed PKI certificate with the OHS for Oracle E-Business Suite 12.1.3, refer to the following for all prerequisite requirements and post steps:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 11 (Note 376700.1)

Overview of the Requirements

The following is a summary of the requirements for deploying a SHA-2 signed PKI certificate for inbound connections to the OHS for Oracle E-Business Suite 12.1.3 include the following:

  • Update OPatch

If you have not already updated to the OPatch 9i, 10.1 version 1.0.0.0.63 or later, download and install it. For the latest OPatch information, refer to the following:

OPatch for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4), (Note 283367.1)
  • Apply the minimum required patch level for the Oracle Fusion Middleware 10.1.3 Oracle Home

The minimum requirement is to upgrade the Oracle Fusion Middleware 10.1.3 Oracle Home to 10.1.3.5 per the following:

Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12 (Note 454811.1)

  • Apply the October 2015 CPU to the Oracle Fusion Middleware 10.1.3 Oracle Home

The minimum CPU requirement for the Oracle Fusion Middleware 10.1.3.5 is the October 2015 CPU level (Patch 21845960) per the following:

Oracle E-Business Suite Releases 11i and 12 Critical Patch Update Knowledge Document (October 2015) (Note 2051000.1)

Note: Testing is performed with all CPU patches applied across the technology stack components and the Oracle E-Business Suite. It is possible to apply the October 2015 CPU (Patch 21845960) to FMW 10g without applying the Oracle E-Business Suite October 2015 CPU or Oracle Database October 2015 CPU/PSU; however, we recommend that customers apply the latest CPU across all technology stack components and the Oracle E-Business Suite.

  • Apply platform-related patch to the Oracle Fusion Middleware 10.1.3 Oracle Home

For AIX and HP Itanium, apply patch 21948197 to the Oracle Fusion Middleware 10.1.3.5 Oracle Home.

  • Perform all necessary post steps.

Post steps include generating the CSR to obtain the SHA-2 signed PKI certificate from your certificate authority (CA). Once you have the certificate, you will import it using Oracle Wallet.

Refer to the appropriate section in the following My Oracle Support note for the complete list of post-steps for your environment:

Enabling SSL/TLS in Oracle E-Business Suite Release 12, Section 11 (Note 376700.1)

Pending Platform Certifications

There will be an additional patch required on top of the FMW 10g Oracle Home October 2015 CPU for Windows. The required patch is currently in development.

Oracle's revenue recognition policy prohibits us from providing time lines and dates for future certifications and releases. Please monitor this blog for the latest in certification announcements.

Related Articles

References

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 Nov 20, 2015

Mobile Approvals 1.3 for EBS Now Available for iOS and Android

Oracle Mobile Approvals for Oracle E-Business Suite lets you respond to pending Workflow approval requests via an app for iOS and Android. It allows you to handle approval requests for expenses, requisitions, purchase orders, recruitment vacancies and offers, timecards, item changes, Supplier Invoices, and more.

Oracle Mobile Approvals for Oracle E-Business Suite is compatible with Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a authorized user of Oracle E-Business Suite, with mobile services configured on the server side by your EBS system administrator. 

What's New in Version 1.3.0

  • Support for enterprise distribution
  • Customization support for corporate branding
  • Mobile application management (MAM) support with Oracle Mobile Security Suite (OMSS), including single sign-on
  • Support for Web SSO authentication to delegate authentication to Oracle Access Manager (OAM)
  • New approval types: Timecards, Item Changes, and Supplier Invoices
  • Enhanced data layout
  • Improved approvals filtering
  • Translations in 10 additional languages including Brazilian Portuguese, Canadian French, Dutch, French, German, Italian, Japanese, Latin American Spanish, Simplified Chinese, and Spanish.

For more information on how to use Mobile Approvals, please refer to the following document:

References

Related Articles

About

Search

Categories
  • Oracle
Archives
« July 2016
SunMonTueWedThuFriSat
     1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today