Monday Jan 26, 2015

Database 12.1.0.1 Certified with EBS 12.2 on Itanium and AIX

As a follow up to our original certification announcement, Oracle Database 12c Release 1 (12.1.0.1) is now certified with Oracle E-Business Suite Release 12.2 (12.2.2 and higher) on the following additional platforms:
  • HP-UX Itanium (11.31)
  • IBM AIX on Power Systems (64-bit) (6.1, 7.1)
This announcement includes:
  • Oracle Database 12cR1 Version 12.1.0.1
  • Oracle Database 12cR1 Version 12.1.0.1 Real Application Clusters (RAC)
  • TDE Column Encryption with Oracle Database 12cR1 Version 12.1.0.1
  • TDE Tablespace Encryption with Oracle Database 12cR1 Version 12.1.0.1
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 12cR1 Version 12.1.0.1
  • Export/Import Process with Oracle Database 12cR1 Version 12.1.0.1

Pending Certifications 

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

  • Oracle Multitenant 12cR1 Version 12.1.0.1
  • Oracle Database Vault 12cR1 Version 12.1.0.1
  • Transportable Database and Transportable Tablespaces Data Migration Processes

References

Related Articles



Thursday Jan 22, 2015

Using SHA-2 Signed Certificates with EBS

Secure Hash Algorithms (SHA) are used for a variety of cryptographic purposes including signing of public key infrastructure (PKI) certificates (e.g., code signing cerificates and Secure Socket Layer (SSL) or Transport Layer Security (TLS) server certificates). Currently, the SHA family of functions include SHA-0, SHA-1, SHA-2 and SHA-3. This article and reference notes focus on the use of the SHA256 hash function of SHA-2 with Oracle E-Business Suite.

Why is SHA-2 important to you?

Industry standards for encryption algorithms are constantly under review. Many certificate authorities are recommending or mandating SHA-2 as the minumum signature algorithm for issuing certificates. The time frame for moving to SHA-2 varies depending upon the certificate authority that is used. The requirement for SHA-2 also impacts intermediate certificates which must also be SHA2 in order to chain back to the end-entity SHA-2 certificate issued. Root certificates are not impacted.

When does Oracle E-Business Suite use certificates?

1. HTTPS clients (outbound connections)
HTTPS client connections that originate from Oracle E-Business Suite. For HTTPS clients, you may need to apply product patches to use SHA-2 certificates. Currently, the following products have identified additional requirements to support SHA-2 for HTTPS clients:

  • XML Gateway
    Follow the instructions in the patch README and apply the following patch: 19909850
  • iProcurement
    Follow the instructions for iProcurement in My Oracle Support Note 1937220.1.

In addition to products that initiate outbound connections from java code on the application tier, the Oracle Database may also act as an HTTP client when the UTL_HTTP package is utilized. Some Oracle E-Business Suite products leverage UTL_HTTP for outbound HTTPS connections. You may also use UTL_HTTP for external integrations and customizations.

For the Oracle Database to utilize a PKI (including SHA-2 signed) certificate, SSL/TLS for outgoing connections database connections must be configured.  Our testing in Oracle E-Business Suite development has confirmed that UTL_HTTP is SHA-2 compliant as of Oracle Database 11.1.0.7 (we have not tested with earlier database versions).The steps for enabling and testing SSL/TLS configuration for the Oracle Database are documented in the following:

2. Server Side
In addition to client side (outbound connections), the Oracle E-Business Suite application tier utilizes PKI certificates for code signing by AD Jar Signing and for the (inbound) SSL/TLS termination point using the Oracle HTTP Server.

AD JAR Signing
During patching, Oracle E-Business Suite uses certificates to sign JARs that will be delivered to the browser. As of Java 1.5, Java and its utilities keytool and jarsigner supports SHA-2 certificates. SHA-2 certificates are certified for JAR signing for all versions of Oracle E-Business Suite (11i, 12.0, 12.1 and 12.2) and Java 1.5 and higher.

Oracle HTTP Server (inbound connections)
SHA-2 certificates are also used by the Oracle HTTP server that is delivered with the Oracle E-Business Suite Applications Technology. The requirements for SHA-2 for the Oracle HTTP Server vary per Oracle E-Business Suite version as follows:

  • Oracle E-Business Suite Release 12.2
    SHA-2 certificates are certified with the Oracle HTTP Server delivered with Oracle E-Business Suite 12.2. The wallet management tools that are shipped with EBS 12.2 generate Certificate Signing Requests (CSRs) signed using MD5. The following note has been updated with the steps necessary to create CSRs signed with other algorithms including SHA-2:
  • Oracle E-Business Suite Releases 12.0 and 12.1
    We are currently working on the certification of SHA-2 certificates with the Oracle HTTP Server for Oracle E-Business Suite Release 12.0 and 12.1. As an option while we are working on this certification, you may use an alternate technology (ie, a load balancer, reverse proxy, etc) that supports SHA-2 as the SSL/TLS termination point. Another alternative is to request that your certificate authority issue a SHA-1 certificate.

  • Oracle E-Business Suite Release 11i
    SHA-2 certificates are certified with Oracle E-Business Suite Release 11i when using mod_ssl.so OpenSSL library version 0.98za or later.  To get the minimum mod_ssl.sl library required for EBS 11i and SHA-2, you must apply the July 2014 CPU. Note: We always recommend that you apply the most current CPU available to your environment. You may refer to the following note for additional details:

Related Articles

References

Wednesday Jan 21, 2015

JRE 1.8.0_31 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_31 (a.k.a. JRE 8u31-b13) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 12.0, 12.1, and 12.2 for Windows and Mac OS X 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 this 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) and 10.9 (Mavericks) desktops.  For details, see:

The certification of JRE 8 for Mac OS X 10.10 (Yosemite) desktops is planned.  

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

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_75 and 1.7.0_76 Certified with Oracle E-Business Suite

Java logo

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

Effects of new support dates on Java upgrades for EBS environments

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

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

All JRE 6, 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 7.

  • CPU Release is JRE 1.7.0_75
  • PSU Release is JRE 1.7.0_76

It is recommended that Oracle E-Business Suite customers use the CPU release (JRE 1.7.0_75) and only upgrade to the PSU release (JRE 1.7.0_76) 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.

JRE 1.7.0_75  (7u75) 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

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 Extended Support in April 2015.

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 this January 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.9 can run JRE 7 or 8 plug-ins.  See these articles:

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_91 Certified with Oracle E-Business Suite

Java logo

The latest Java Runtime Environment 1.6.0_91 (a.k.a. JRE 6u91-b13) 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.

Effects of new support dates on Java upgrades for EBS environments

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

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

All JRE 6, 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 in this Java release?

JRE 1.6.0_91  (6u91-b13) 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.9 can run JRE 7 or 8 plug-ins.  See these articles:

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

Critical Patch Update for January 2015 Now Available

The  Critical Patch Update (CPU) for January 2015 was released on January 20, 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:

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

Friday Jan 16, 2015

Internet Explorer 11 Certified with E-Business Suite 12.2 and 12.0

Microsoft IE logoMicrosoft Internet Explorer 11 is now certified as a desktop client browser for Oracle E-Business Suite Release 12.2 and 12.0.  This follows our previous certification of IE11 with EBS 12.1.  The certified desktop operating systems are:

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

Certified IE 11 Modes

Internet Explorer 11 can be used in "Desktop Mode" on Windows 8.1.  Running IE 11 from the "Modern" (Metro) Start Screen is not certified.

Due to display issues with certain FWK pages when using IE9 or IE10 we previously recommended running E-Business Suite using the browsers 'compatibility mode'.  These display issues have now been fixed for IE11-- you can now access your E-Business Suite 12.x environments without using 'compatibility mode' in IE 11.

 IE 11 includes an "Enterprise Mode" which can be used to emulated Internet Explorer 8 behaviour and provide compatibility with earlier browser standards.  You should not use "Enterprise Mode" with Oracle E-Business Suite.  EBS compatibility with IE 11 requires server-side patches. Enabling "Enterprise Mode" in IE 11 is not needed and will not resolve all compatibility issues.

EBS 12.2 Prerequisites

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

EBS 12.0 Prerequisites

  • EBS 12.0.6
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher
JRE 6, 7, and 8 are certified with EBS

Java Runtime Environment (JRE) Versions 6, 7, and 8 are certified with EBS. 

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

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

  • From JRE 1.6.0_03 and later updates on the 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

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops. 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.

"JInitiator version too low" errors

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

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

Certifications with EBS 11i still pending

We plan to certify IE 11 with EBS 11i.  This certification us underway now and will be released soon.

If you're running EBS 11i, you must ensure that your mission-critical desktops remain on an earlier certified browsers until this certification is completed.  As of the time this article was published, certified browsers include IE 10 and Firefox ESR 31 for Windows desktops.

You can block automatic updates by using Microsoft's Internet Explorer 11 Blocker Toolkit:

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

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.

Wednesday Jan 14, 2015

Reminder: EBS 12.0 Extended Support Ends January 31, 2015

Extended Support for Oracle E-Business Suite 12.0 ends on January 31, 2015.  See:

Chart displaying EBS Premier and Extended Support dates

EBS 12.0 users should upgrade to EBS 12.1 or 12.2 as soon as possible. You might find this article useful:

What happens after Extended Support ends?

Sustaining Support for EBS 12.0 begins on February 1, 2015.  You can request diagnostic assistance for EBS 12.0 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 12.0 users

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

New versions of desktop components may not work with EBS 12.0.6. 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 12.0.6. 

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, OC4J, Forms, etc.)

Related Articles

Friday Jan 09, 2015

EBS 12.1.3 Certified with Microsoft Windows Server 2012 R2

Microsoft Windows Server logoOracle E-Business Suite Release 12 (12.1.3) is now certified with Microsoft Windows Server 2012 R2 on both the application and database tiers through a certified migration of an existing Release 12 installation. Microsoft Windows Server 2012 R2 is a Windows x64 (64-bit) only operating system and is the latest Windows Server version.

Support of the E-Business Suite on this platform is achieved by a two-step process of migrating the Oracle Database first (as documented in the 11gR2 Database Tier Only Platform note), and then migrating the application tier using the process documented in the R12 Rapid Clone note. These steps and all requirements are outlined here:

The operating systems certified on this platform are:

  • Microsoft Windows Server 2012 R2 Standard
  • Microsoft Windows Server 2012 R2 Datacenter

Pending Certifications 

Certification for Rapid Install of Oracle E-Business Suite Release 12.2 on Microsoft Windows Server 2012 R2 is in progress and will be announced separately.

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

Where can I find more information?

Related Articles

Thursday Jan 08, 2015

Database 12.1.0.2 Certified with E-Business Suite 12.2

I’m pleased to announce that 12.1.0.2, the first patchset for the 12c Database, is now certified with E-Business Suite 12.2.2 and higher. 

Database support implications may also be reviewed in this database patching and support article.

Oracle E-Business Suite Release 12.2.x
Certified Platforms
  • Linux x86-64 (Oracle Linux 5, 6)
  • Linux x86-64 (RHEL 5, 6)
  • Linux x86-64 (SLES 11)
  • Oracle Solaris on SPARC (64-bit) (10, 11) 
  • Oracle Solaris on x86-64 (10, 11)*
*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.
Pending Platform Certifications
  • Microsoft Windows x64 (64-bit) 
  • IBM AIX on Power Systems (64-bit)
  • HP-UX Itanium
  • IBM: Linux on System z 
Database Feature and Option Certifications
The following database options and features are supported for use:

Pending Feature/Option Certifications

  • Oracle Multitenant
  • Oracle Database Vault
  • TDE Tablespace Encryption
  • Transportable Database and Transportable Tablespaces data migration processes

About the pending certifications

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

EBS 12.2 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.

Wednesday Jan 07, 2015

Oracle VM Templates For EBS 12.2.4 For Exalogic Now Available

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

12.2.4 Exalogic

These VM templates can be imported into the Enterprise Manager Ops Center to deploy E-Business Suite Linux 64-bit environments on Exalogic servers.

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

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

Available Templates

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

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

Usage Tips

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

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

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

Technology Components

Operating System

  • Oracle Linux 6 Update 5 operating system

Oracle E-Business Suite Release 12.2.4 VM templates utilize the base Oracle Linux image (OL) 6.5, which requires Oracle Exalogic Elastic Cloud Software (EECS) July 2014 PSU version 2.0.6.1.2 or 2.0.6.0.2 or higher for Exalogic Virtual platforms (Note 1937272.1).

Database

The Vision Demo Database Tier and Production (PROD) Database Tier templates include the following:

  • Database: 11.2.0.4
  • CPU Level: July 2014

Application Tier

The Application Tier template include the following components:

  • Application Tier Code Level: AD and TXK Delta 5 plus Bundle Fixes
  • Oracle Forms and Reports: 10.1.2.3.0
  • Oracle WebLogic Server: 10.3.6.0
  • Web Tier Components: 11.1.1.6
  • JDK: JDK 1.7 build 1.7.0_67-b01
  • Java Plugin: J2SE 1.7
  • CPU Level: July 2014

For additional details and installation instructions, see:

References

Related Articles

Monday Jan 05, 2015

Enhance E-Business Suite Security By Switching to TLS

It seems fitting to start 2015 with a security-related blog post about Secure Socket Layer (SSL) and Transport Layer Security (TLS).  TLS is the successor to SSL. TLS, like SSL, is a protocol that encrypts traffic between applications and servers. TLS is based on SSL 3.0. TLS 1.0 is sometimes referred to as SSL 3.1. Going forward you will hear us talk more about TLS and less about SSL.

TLS is considered to be more secure than SSL.  All systems that use SSL 3.0 may be vulnerable to a design vulnerability in SSL’s handling of block cipher mode padding.  The Padding Oracle on Downgraded Legacy Encryption (POODLE) attack is one possible attack vector for web browsers and web servers.

Oracle E-Business Suite customers can migrate to TLS and mitigate the effects of POODLE attacks by following:

Happy 2015!

.Related Articles

References

Wednesday Dec 31, 2014

2014: A Year in Review for Oracle E-Business Suite

Happy New Year.  2014 was another big year for the Oracle E-Business Suite. 

Did you miss any of the most-important articles of the year?

Upgrading to EBS 12.2

Updates to EBS 12.2

Updates to EBS 12.1

Java

Important Technology Stack Updates

Virtualization

Maintaining and Extending EBS

Support Policies

Tuesday Dec 30, 2014

Java Auto-Update Upgrades JRE 7 to 8 in January 2015

This notice is posted on the Java SE Download site:

JRE 7 Auto Update Notice screenshot

If your users are running JRE 7 with auto-update enabled, they will be automatically upgraded to JRE 8 with the January 2015 CPU release on January 20, 2015.  This affects Windows and Mac desktops. 

For more details, see:

Will do EBS sysadmins need to do?

If you do not have Auto-Update enabled on your end-users' desktops, you don't need to do anything.

JRE 8 is certified with all current EBS releases: EBS 11i, 12.0, 12.1, and 12.2.  If you have Auto-Update enabled, you need to apply server-side patches to make your EBS environment compatible with JRE 8.  For details, see:  

See that article for answers to common questions, including:

  • Where are the official patch requirements documented?
  • What are the known issues with JRE 8 and EBS?
  • Does JRE 8 work with Discoverer 11g?
  • What are the implications for EBS users of Java 6 and 7 End of Public Updates?
  • Will EBS users be forced to upgrade to JRE 8?
  • What are the impacts of enabling JRE Auto-Update?
  • Can multiple JRE releases coexist on the same desktop?
  • What do Mac users need?
  • Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

Related Articles

Monday Dec 29, 2014

Quarterly EBS Upgrade Recommendations: December 2014 Edition

(16-Jan-2015 Update to recommendation number 5:  Removed 11i from 12.1.0.2 and added to 12.1.0.1.  Removed 12.2 from 12.1.0.1 and added to 12.1.0.2)

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

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

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

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

  4. EBS 12.2 users should upgrade to 12.2.4 or the latest AD/TXK tools and StartCD 49.

  5. Oracle Database 10gR2, 11gR1, and 11gR2 users should upgrade to 12.1.0.1 (11i) or 12.1.0.2 (12.0/12.1, 12.2)

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

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

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

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

  10. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_85 or later 1.6 updates or JRE 1.7.0_72 or later 1.7 updates or JRE 1.8.0_25 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 31.

  13. All EBS 11i, 12.0, 12.1, 12.2 users should apply the latest 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.

Related Articles

Friday Dec 26, 2014

Oracle WebTier Utilities 11.1.1.7 Now Certified with EBS 12.2

The Oracle E-Business Suite Release 12.2's Rapid Install delivers three Fusion Middleware (FMW) components:
  1. Oracle WebLogic Server 10.3.6 (this is the "$FMW_HOME") 
  2. Oracle WebTier Utilities 11.1.1.6
  3. Oracle Common Home (Part of Oracle WebTier Utilities 11.1.1.6)

EBS 12.2 technology stack architecture diagram

The Oracle WebTier Utilities and the Oracle Common Home should be upgraded by EBS sysadmins to get the latest updates for security, performance, and stability.

If you'd like to upgrade these two components, you can download the latest update here: 

For instructions on how to apply this update to your EBS 12.2 environment, see:

Related Articles

Wednesday Dec 24, 2014

New Rapid Install StartCD 12.2.0.49 for EBS 12.2 Now Available

We are pleased to announce the availability of the latest Oracle E-Business Suite startCD, 12.2.0.49. As the fundamental installation medium for EBS, the startCD is what you begin with when installing or upgrading to Release 12.2.

This latest version includes many important fixes, which are described in the readme of the startCD patch (listed below). The new startCD is highly recommended for all customers who will use Rapid Install to perform an installation or upgrade to Release 12.2:

Rapid Install Welcome Screen

How to Obtain startCD 12.2.0.49

You can download the startCD as Patch 19378467.

Using Rapid Install

Full instructions for Rapid Install can be found in Oracle E-Business Suite Installation Guide: Using Rapid Install (Part No. E22950_18). This book is available in the EBS Web Library in both PDF and HTML formats.

Additonal References

You should also refer to the following My Oracle Support knowledge documents:

Related Articles

Tuesday Dec 23, 2014

Running E-Business Suite on Exalogic and Exadata

Exalogic serverPrior articles have noted that you can run the E-Business Suite on Oracle Engineered Systems such as Exalogic Elastic Cloud and Exadata Database Machine

What EBS combinations can you run on Exalogic and Exadata?

We certify E-Business Suite releases on operating systems and database releases (e.g. EBS 12.1.3 is certified on Database 12.1.0.2 on Linux 6 x86-64), not specific configurations of hardware such as Exadata or Exalogic.  This means that you can run the E-Business Suite on Exadata and Exalogic with any of the certified combinations listed in the Certifications database on My Oracle Support.

Srini Chavali, my colleague in the Exalogic division, has published a nice summary of all of the latest resources:

Srini gives an overview of the process for getting EBS onto these systems, discusses VM templates and Maximum Availability Architectures, and points to other useful best practices and reference documents. 

Related Articles

Friday Dec 19, 2014

Preparing Your Customizations for EBS 12.2

EBS 12.2 comes with Online Patching, a fresh new user interface, updated EBS product modules, and new mobile apps.  If you've customized your EBS environment or are using third-party extensions from other vendors, you'll need to ensure that they work with EBS 12.2.

EBS 12.2 New Home Page screenshot

Review the updated development standards

Coding standards, OA Framework capabilities, and, of course, database object development standards  have all been updated in EBS 12.2.  Making your extensions and customizations work with Online Patching is crucial.  Check this comprehensive guide:

Also, if you're interested in taking advantage of the latest user interface (UI) enhancements in EBS 12.2.4, check this Note:

Check your file, data model, and seed data dependencies

The following tools generate detailed reports of the differences between a specific EBS release for files, tables, and seed data. You can drill into the E-Business Suite Technical Reference Manual (eTRM) for details on the database model, database objects, and their relationships, too.

Verify your third-party extensions and tools

Contact your third-party software providers to confirm whether they have updated their EBS extensions or tools to be compatible with EBS 12.2.  This is critical for extensions or tools that are tightly-coupled with the E-Business Suite, i.e. those extensions that modify EBS tables directly. 

Another option is to check whether your Oracle partner has put their software through the Oracle Validated Integration program for EBS 12.2.

Review Guidance for Integrating Custom and Third-Party Products With Oracle E-Business Suite Release 12.2 (Note 1916149.1).  

Related Articles


Thursday Dec 18, 2014

DB 12.1.0.1 Certified with EBS 11i & R12 on Linux on IBM System z

IBM LogoOracle Database 12c Release 1 (12.1.0.1) is now certified with Oracle E-Business Suite Release 11i, 12.0, and 12.1 on the following Linux on IBM System z operating systems as 'database tier only' platforms:

Release 11i (11.5.10.2 + ATG PF.H.delta.7 (RUP 7) or higher), Release 12.0 (12.0.6 or higher), 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.1
  • Oracle Database 12cR1 version 12.1.0.1 Real Application Clusters (RAC)
  • Transparent Data Encryption (TDE) Column Encryption using Oracle Database 12cR1 version 12.1.0.1
  • Transparent Data Encryption (TDE) Tablespace Encryption using Oracle Database 12cR1 version 12.1.0.1
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 12cR1 version 12.1.0.1
  • Export/Import Process for Oracle E-Business Suite Release 11i with Oracle Database 12cR1 version 12.1.0.1
  • Export/Import Process for Oracle E-Business Suite Release 12.0 or 12.1 with Oracle Database 12cR1 version 12.1.0.1

Pending Certifications

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

  • Oracle Multitenant 12cR1 version 12.1.0.1
  • Oracle Database Vault 12cR1 version 12.1.0.1
  • Transportable Database and Transportable Tablespaces Data Migration Processes

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

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

Related Articles

Tuesday Dec 16, 2014

Updated: Using Third-Party Identity Managers with E-Business Suite Release 12

This article is an updated version of two earlier articles: one written for EBS 11i + SSO + OID, and another written for EBS 12 + SSO + OID.  Oracle Single Sign-On has been superceded by Oracle Access Manager (OAM).  This latest article covers the latest options for using EBS Release 12.x (12.0, 12.1, and 12.2) and Oracle Access Manager with third-party authentication systems.

Like most of our customers, you probably already have a corporate identity management system in place. And, you've probably not been enjoying the experience of redundantly administering the same user in your corporate identity management system as well as the E-Business Suite. If this describes your environment, this in-depth article about integrating Oracle E-Business Suite Release 12, Oracle Access Manager, and Oracle Internet Directory with third-party identity management systems will show you a better way of managing your EBS users.

No More Redundant User Administration

It is possible to integrate the E-Business Suite with existing third-party LDAP and single sign-on solutions via Oracle Internet Directory and Oracle Access Manager and Oracle Internet Directory, respectively:

Architecture diagram EBS + Oracle Access Manager + OID + third party ldap

Third-party single sign-on solutions can be integrated with Oracle Access Manager, and third-party LDAP directories can be integrated with Oracle Internet Directory. Oracle Access Manager and Oracle Internet Directory are integrated, in turn, with the E-Business Suite.

Example Scenario: The Deluxe "Zero Sign-On" Approach

A user logs on their PC using their Windows userid and password. The user decides to file an expense report for attending the OpenWorld conference. He starts Internet Explorer, opens Favorites, and selects a bookmarked link for the E-Business Suite's Self-Service Expenses.  Self-Service Expenses starts and the user begins the entering their expense report.

We sometimes call this "zero sign-on" because the user never actually logged on to any Oracle systems at all; the user's Windows Kerberos ticket from the Windows Primary Domain Controller (PDC) gave him access to the E-Business Suite automatically.

Magic? What Really Happened?

Brace yourself: some of the following material might require a couple of passes to sink in.

The "deluxe" scenario above illustrates the following integrations:

  • Microsoft Active Directory with Oracle Internet Directory
  • Microsoft Kerberos Authentication with Oracle Access Manager
  • Oracle Access Manager and Oracle Internet Directory integration with the E-Business Suite

Microsoft Active Directory MSAD integration with EBS and Windows Kerberos

The user logged on to their PC, which authenticated them against Microsoft Active Directory. As part of that logon process, the Windows Primary Domain Controller (PDC) issued a valid Kerberos ticket to the user.

When the user attempted to access Self-Service Expenses via his bookmarked link, he was redirected to Oracle Access Manager. Oracle Access Manager checked the user's credentials against the Windows Key Domain Controller (KDC), issued its own Oracle security tokens to the user, and redirected the user back to the E-Business Suite.

The E-Business Suite recognized the Oracle Access Manager security tokens and looked up the user's assigned Applications Responsibilities to ensure that he was authorized to access Self-Service Expenses. That done, it issued its own E-Business Suite security tokens and then passed the user through to Self-Service Expenses without requiring any additional logons.

Integration with Microsoft Active Directory Only

Not everyone uses Microsoft Kerberos Authentication. A simpler integration option omits Kerberos and includes only Microsoft Active Directory and Oracle Internet Directory, like this:

Microsoft Active Directory MSAD integration with EBS

In this simpler architecture, when the user attempts to access Self-Service Expenses via his bookmarked link, he's redirected to Oracle Access Manager. Oracle Access Manager displays a login screen and collects the user's ID and password.

Oracle Access Manager passes the user's credentials to Oracle Internet Directory.  Oracle Internet Directory uses the Microsoft Active Directory External Authentication Plug-In to pass the user's credentials to Microsoft Active Directory.

Microsoft Active Directory looks up the user's ID and password in its database, and informs Oracle Internet Directory that this is an authenticated user. Oracle Internet Directory informs Oracle Access Manager that the user was successfully authenticated.

Oracle Access Manager issues the user a set of security tokens and redirects the user to the E-Business Suite. The E-Business Suite recognizes the Oracle Access Manager security tokens and looks up the user's assigned Applications Responsibilities to ensure that he's authorized to access Self-Service Expenses. That done, it issues its own E-Business Suite security tokens and then passes the user through to Self-Service Expenses.

Synchronization of User Credentials with Third-Party LDAP Directories

If you've been paying close attention so far, you have gathered that user credentials need to be synchronized between the third-party LDAP, Oracle Internet Directory, and the E-Business Suite. The synchronization architecture looks like this:

Architecture diagram third-party LDAP directory integration with EBS

In this configuration, only the user name needs to be synchronized; the user's password is stored in the third-party LDAP directory. None of the Oracle products need to store the user's password, since they delegate user authentication to the third-party LDAP solutions.

Architecture diagram showing how passwords are stored in third-party LDAPs and not Oracle Internet Directory or E-Business Suite

The key concept here is that user authentication is still separated from user authorization even when a third-party LDAP is in place.

Architecture diagram distinguishing Authentication%20vs%20Authorization.png

So, the E-Business Suite still grants authenticated users access to E-Business Suite protected content based on the users' Applications Responsibilities, which are managed in the E-Business Suite exclusively.

Integration With Other Single Sign-On Solutions

It is also possible to integrate Oracle Access Manager with other single sign-on solutions, including:

  • CA Netegrity SiteMinder
  • Biometric devices like fingerprint readers
  • Smartcards
  • PKI X.509 digital certificates

When integrated with other single sign-on solutions, a chain of trust is established between the third-party, Oracle Access Manager, and the E-Business Suite. Users logging on via the third-party single sign-on solution are passed through transparently to Oracle Access Manager and the E-Business Suite.

Relax, It's Easy and Fun

Well, maybe not... but at least it's technically feasible. You might find it reassuring to note that a number of E-Business Suite customers are running this configuration in production already.

This is about as much detail as I think is appropriate for now. Feel free to post comments if you have questions about this topic.

References

For a survey of options for integrating Oracle Access Manager and Oracle Internet Directory with Oracle E-Business Suite Release 12, see:

Related Articles

Thursday Dec 11, 2014

Top 9 Frequently-Asked Questions About Online Patching

Online Patching allows you to apply patches to an EBS 12.2 system while it is still up and  running.  If you're just getting started with Online Patching, you'll find this document useful:

We update this document regularly.  It currently covers frequently asked questions about core Online Patching concepts, resource requirements, functionality, patch application, and handling of customizations and third-party integrations.  We intend to add troubleshooting information to this document soon.

As a preview of that document, here are the top 9 frequently-asked questions about Online Patching:

Which Oracle E-Business Suite releases can Online Patching be used with?
Online patching is used with Oracle E-Business Suite 12.2 and higher.

What types of patch are applied online?
All Oracle E-Business Suite Release 12.2 patches are applied online. This includes one-off patches, patch rollups, consolidated updates and security patches.

What is the Online Patching cycle?
The Online Patching cycle is a sequence of inter-related steps (phases) used to apply patches to an Oracle E-Business Suite system.

EBS 12.2 online patching cycle

What tool is used to apply online patches?
The AD Online Patching (adop) command-line utility is used to manage the Online Patching cycle.

Is there any downtime in Online Patching?
There is a short period of downtime when the application tier services are shut down and restarted. The database remains open all the time.

Do I upgrade to Release 12.2 with Online Patching?
No. After you upgrade to Oracle E-Business Suite Release 12.2, you will enable Online Patching.

Once I upgrade to Release 12.2, can I still apply patches in the traditional way?
No. All patches for Release 12.2 will be online patches. The traditional, pre-12.2 method of applying patches will not work.

Can I still use adpatch in the Release 12.2 Online Patching environment?
No. While the Oracle tools may internally invoke the adpatch utility, direct user invocation of adpatch is not allowed.

Are there any plans to make Online Patching available with pre-12.2 releases?
No. Online patching can only be used with Release 12.2.

Related Articles

Wednesday Dec 10, 2014

Top Three EBS 12.2 Online Patching Resources

Oracle E-Business Suite Release 12.2 introduced Online Patching, a feature that greatly reduces the downtime that was needed in previous releases to apply patches and updates. Online Patching minimizes downtime by allowing patching operations to be performed while users remain on the system.

Online Patching features

  • In Release 12.2, all patching operations are carried out while the applications are in use and users are online. 
  • Patching is performed using the new adop (AD Online Patching) utility.
  • A short period of downtime is required to restart application tier services; the E-Business Suite database does not need to be restarted.

Online Patching EBR editions

Here's the official Online Patching documentation:

Here's our official webcast with a primer on Online Patching:

Here's what you need to do to ensure that your customizations work with Online Patching:

Related Articles

Tuesday Dec 09, 2014

Database 12c 12.1.0.2 Certified With 12.1 On Oracle Solaris on x86-64

As a follow up to our earlier announcement, Oracle Database 12cR1 Version 12.1.0.2 is now certified with Oracle E-Business Suite Release 12 for 12.1 on the following additional platform:

Release 12.1 (12.1.3 and higher):

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

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.

Data12.1.0.2 download screenshot

In addition, the Export/Import process for EBS release 12.0 or 12.1 with Oracle Database 12cR1 Version 12.1.0.2 is now certified.

Certification data in My Oracle Support (http://support.oracle.com) is being updated with this information - please review the documents below for all requirements and additional details:

Related Articles

Monday Dec 08, 2014

Last Stop For Oracle Applications Tablespace Migration

The Oracle Applications Tablespace Model (OATM) -- sometimes also called the Oracle E-Business Suite Tablespace Model) -- organizes the EBS database by object type rather than by products.  Prior to OATM, the EBS database had two tablespaces for each product, resulting in hundreds of tablespaces.  OATM contains only twelve locally-managed tablespaces.  This simplifies management and requires fewer operating system files.

Whether you're already using the Oracle Applications Tablespace Model depends on which version of the E-Business Suite you initially installed. If you started on an older EBS release, you have the option of migrating to the Oracle Applications Tablespace Model.

Is OATM mandatory?

No, it's optional, but we recommend that you use OATM.  It's more-efficient and easier to manage.  You can use the OATM Tablespace Migration Utility to migrate to the new model.

Can I use OATM with EBS 12.2?

The OATM Tablespace Migration Utility cannot be used after you enable Online Patching in EBS 12.2.  If you wish to migrate to OATM, you must do so before you enable Online Patching.

If you do not migrate to OATM, you must continue to manage your tablespaces separately after enabling Online Patching.

References


Friday Dec 05, 2014

Oracle Functional Testing Suite Advanced Pack for EBS 12.2.4 Now Available

E-Business Suite Development is pleased to announce the availability of the Oracle Functional Testing Suite Advanced Pack for Oracle E-Business Suite 12.2.4, a forward-port of the 12.1.3 Advanced Pack announced earlier this year. Designed for use with the Oracle Functional Testing Suite and its Oracle Flow Builder capability, the pack provides pre-built test components and flows for in-depth testing of the following Oracle E-Business Suite products:
  • Oracle Asset Lifecycle Management
  • Oracle Channel Revenue Management
  • Oracle Discrete Manufacturing
  • Oracle Incentive Compensation
  • Oracle Lease and Finance Management
  • Oracle Process Manufacturing
  • Oracle Procurement
  • Oracle Project Management
  • Oracle Property Manager
  • Oracle Service

OATS Flow Builder screenshot

The Oracle Functional Testing Suite Advanced Pack for Oracle E-Business Suite 12.2.4 complements and extends the starter pack of 3,600 test components and 230 test flows delivered with the Oracle Functional Testing Suite and its Oracle Flow Builder capability. The starter pack components and flows also have been forward-ported to 12.2.4.

Some Background on Automating Testing with Oracle Application Testing Suite and Oracle Flow Builder     

Testing complex packaged applications like Oracle E-Business Suite can be time-consuming and challenging for organizations, hampering their ability to upgrade to latest releases or apply latest patches. Oracle Functional Testing Suite, the functional and regression testing component of the Oracle Application Testing Suite, offers a unique and powerful testing platform for Oracle E-Business Suite and other Oracle applications.

Starting with the 12.3.0.1 release of Oracle Application Testing Suite, we introduced the Oracle Flow Builder testing framework and accompanying starter pack of pre-built test components and flows. Using Oracle Flow Builder, even non-technical testers can create working test scripts using the pre-built components that Oracle provides. Each component represents an atomic test operation such as “create an invoice batch” or “apply an invoice hold.” Testers can assemble the pre-built components into test flows, and combine test flows with spreadsheet data to drive the testing of multiple data conditions. The Oracle Flow Builder framework allows customers to add, modify and extend the pre-built components to address new functionality and customizations of the Oracle E-Business Suite.

Using Oracle Flow Builder’s component-based test generation framework instead of a traditional record/playback approach has allowed the EBS Quality Assurance team to reduce their test automation effort by 60%. E-Business Suite customers can significantly reduce their test automation effort using Oracle Application Testing Suite with Oracle Flow Builder and the pre-built test components and flows that Oracle provides.

Oracle Functional Testing Suite Advanced Pack for Oracle E-Business Suite Improves Test Coverage

With the new Oracle Functional Testing Suite Advanced Pack for Oracle E-Business Suite 12.2.4, we are delivering a significant number of additional test components and flows beyond those contained in the Oracle Flow Builder starter pack for 12.2.4. These additional test components and flows provide 70-80% test coverage and enable the automation of detailed and complex test flows across the Oracle E-Business Suite products.

Downloads

You can download the Oracle Functional Testing Suite Advanced Pack for Oracle E-Business Suite from the Oracle Technology Network.

References


Related Articles

Thursday Dec 04, 2014

JRE Support Ends Earlier than JDK Support

One of our Applications Technology Group architects recently drew my attention to an important change in Java support policies that I'd missed: support for client-based Java Runtime Environment (JRE) plug-ins now ends earlier than the support dates for server-based Java Development Kit (JDK) components.

Screenshot from Java Lifetime Support Policy document JDK JRE different dates

These dates are published here:

The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology (Java Web Start & Java Plug-in technologies) 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:

Related Articles

Tuesday Dec 02, 2014

EBS VMs: Appliances, Templates, and Assemblies Explained

This article describes the different types of Oracle E-Business Suite virtual machine software packages available, and how they are appropriate for different situations.

The appliances, templates, and assemblies provided on the Oracle Software Delivery Cloud (https://edelivery.oracle.com/linux) all contain virtual machine images. These are intended for different purposes, but all allow you to install EBS rapidly and create an EBS virtual machine.

Here are some important terms related to Oracle’s VM offerings:

  • Oracle VM is Oracle's own server virtualization platform. An Oracle VM template is one media format -- the original media format -- used to deliver a virtual machine within the Oracle VM framework.
  • Oracle VirtualBox is Oracle's own desktop virtualization platform. An Oracle VM appliance uses an industry-standard media format to deliver a virtual machine on top of VirtualBox. Because appliances use an industry standard format, they can in principle be deployed on third party virtualization platforms, but Oracle does not test those platforms.
  • An Oracle VM Virtual Assembly is a format developed specifically for deployment using Enterprise Manager Cloud Control (EMCC). An assembly is powerful in that a single assembly contains multiple VM's (not just a single VM like an appliance or a template) as well as the logic to connect those VM's, allowing EMCC to install a multi-node system at the touch of a button. Customers who use Enterprise Manager and run Oracle VM can take advantage of these.
Note that Oracle VM Manager can now import Oracle VM appliances, so we have switched over to producing appliances wherever possible, giving a single set of virtual machine images that can be installed on a server, desktop or laptop. We do still produce VM templates for Exalogic (ex.: Oracle VM Templates For EBS 12.2.3 For Exalogic) because Enterprise Manager Operations Center (EMOC) currently only supports VM templates.

Summary of Usage

Virtual Appliances
  • Deploy an EBS VM on a desktop or laptop using Virtual Box
  • Deploy an EBS VM on a server using Oracle VM Manager
  • Manual setup required to add nodes and configure multi-node
VM Templates
  • Deploy an EBS VM on a server using Oracle VM Manager
  • Deploy an EBS VM on Exalogic using Enterprise Manager Operations Center
  • Manual setup required to add nodes and configure multi-node
Virtual Assemblies
  • Deploy EBS VM's on a server or servers using Oracle Enterprise Manager Cloud Control
  • Automated installation of single or multi-node

Available Releases

Virtual Appliances


Single Node Multi-Node MOS Doc ID
Oracle VM Virtual Appliances for Oracle E-Business Suite 12.2.4
VIS
PROD, VIS
1928303.1
Oracle VM Virtual Appliances for Oracle  E-Business Suite 12.2.3
VIS
PROD, VIS
1620448.1
Oracle VM Virtual Appliances  for Oracle E-Business Suite 12.1.3
VIS
PROD, VIS
1906691.1


VM Templates


Single Node Multi-Node MOS Doc ID

Oracle VM Templates for Oracle E-Business Suite 12.2.3 for Exalogic

n/a
PROD, VIS
1633952.1
Oracle VM Templates for Oracle E-Business Suite 12.2.2
n/a
PROD, VIS
1590941.1
Oracle VM Templates  for Oracle  E-Business Suite 12.1.3 for Exalogic
n/a
VIS
1499132.1


Virtual Assemblies


Single Node Multi-Node MOS Doc ID
Oracle Virtual Assemblies for Oracle E-Business Suite 12.2.3
PROD
PROD
1904928.1
Oracle Virtual Assemblies for Oracle E-Business Suite 12.1.3
PROD
PROD
1904928.1


Related Articles

Monday Dec 01, 2014

November 2014 Updates to AD and TXK for EBS 12.2

We continue to release updates to EBS 12.2 technology stack (TXK) and Applications Database (AD) components.  We released the first set of updates in March 2014, the second set in May 2014, the third set in July 2014, the fourth set in October 2014, and have now made available a fifth set of critical updates.

If you are on Oracle E-Business Suite Release 12.2, we strongly recommend that you apply these two newly-released patch collections (November 2014 bundle fixes) at your earliest convenience:

Patch 20034256

Applying these on top of AD Delta 5 and TXK Delta 5 respectively will bring you to the recommended codelevel for AD and TXK:

  • AD Delta 5 (Patch 18283295) + November 2014 Bundle Fixes (Patch 20034256)
  • TXK Delta 5 (Patch 18288881) + November 2014 Bundle Fixes (Patch 20043910)

 You must always keep your AD and TXK codelevels synchronized.

Important: As well as providing additional fixes, the November 2014 bundle fixes include all the fixes provided in the October 2014 set. So if you have not yet applied the October set, you can just apply the November set instead.

What Is a Codelevel?

Oracle E-Business Suite Release 12 patches are grouped into codelines. A codeline begins with a point release (for example, Release 12.0) and progresses to include all the patches created to maintain that point release.

Patches associated with codelines implement a set of features for a point release, and also provide fixes for that set of features. Such a unique set of product features for a point release is referred to as a a codelevel. You can think of it as the code you get when you apply a set of patches: in other words, it is defined by the patches that deliver it. Codelevels are cumulative, with each containing the initial set of features plus all the fixes created for that product.

Benefits of the Latest Codelevel

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

  • It includes a number of significant fixes and improvements.
  • New patches to implement code fixes will only be appliable to the latest AD/TXK codelevel.
  • No code fixes will be created for earlier AD/TXK codelevels.

How Can I Get To the Latest Codelevel?

Installation instructions are here:

Further information about these bundle fixes can be found in:

Related Articles

Wednesday Nov 26, 2014

Oracle EBS Adapter for Oracle SOA Suite 12c Now Available

Oracle E-Business Suite Adapter for Oracle SOA Suite 12c (12.1.3) is now available for use with the E-Business Suite.  Previous releases of this product were called Oracle Applications Adapter for Oracle SOA Suite.

Architecture diagram for EBS Adapter for SOA Suite

You can use the Oracle E-Business Suite Adapter for Oracle SOA Suite to integrate EBS 11i, 12.1, and 12.2 with external systems.  The EBS Adapter allows you to build bidirectional standards-based real-time integrations with the E-Business Suite.  The Adapter supports JCA and web service standards for creating service-oriented applications (SOA). 

What's new in this release?

  • Adapter configuration reports: You can now view Adapter configuration reports in Oracle Fusion Middleware Control. 
  • Flexfield support for Open Interface Tables:  In addition to its existing support for PL/SQL APIs, this release provides flexfield support for Open Interface Tables by displaying flexfield data and mapping if configured in Open Interface Tables at design and run time

References

Related Articles


About

Search

Categories
Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
5
6
7
8
9
10
12
13
14
15
16
17
18
20
21
22
23
24
25
26
27
28
29
30
31
      
Today