Steven Chan

Subscribe to Steven Chan feed
Oracle Blogs
Updated: 17 hours 36 min ago

August 2018 Update to E-Business Suite Technology Codelevel Checker (ETCC)

Wed, 2018-08-15 11:56

The E-Business Suite Technology Codelevel Checker (ETCC) tool helps you identify application or database tier overlay patches that need to be applied to your Oracle E-Business Suite Release 12.2 system. ETCC maps missing overlay patches to the default corresponding Database Patch Set Update (PSU) patches, and displays them in a patch recommendation summary.

What’s New

ETCC has been updated to include bug fixes and patching combinations for the following recommended versions of the following updates:

  • Oracle Database Proactive BP 12.1.0.2.180717
  • Oracle Database PSU 12.1.0.2.180717
  • Oracle JavaVM Component Database PSU 12.1.0.2.180717
  • Oracle Database Patch for Exadata BP 12.1.0.2.180717
  • Oracle Database PSU 12.1.0.2.180717
  • Oracle JavaVM Component Database PSU 12.1.0.2.180717
  • Microsoft Windows Database BP 12.1.0.2.180717
  • Oracle JavaVM Component 12.1.0.2.180717 on Windows
  • Microsoft Windows Database BP 12.1.0.2.180717
  • Oracle JavaVM Component 12.1.0.2.180717 on Windows

Obtaining ETCC

We recommend always using the latest version of ETCC, as new bugfixes will not be checked by older versions of the utility. The latest version of the ETCC tool can be downloaded via Patch 17537119 from My Oracle Support.

References

Related Articles

Categories: APPS Blogs

JRE 1.8.0_181 Certified with Oracle EBS 12.1 and 12.2

Tue, 2018-08-14 11:29

Java logo

Java Runtime Environment 1.8.0_181 (a.k.a. JRE 8u181-b13) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows clients.

Java Web Start is available

This JRE release may be run with either the Java plug-in or Java Web Start.

Java Web Start is certified with EBS 12.1 and 12.2 for Windows clients.  

Considerations if you're also running JRE 1.6 or 1.7

JRE 1.7 and JRE 1.6 updates included an important change: the Java deployment technology (i.e. the JRE browser plugin) is no longer available for those Java releases. It is expected that Java deployment technology will not be packaged in later Java 6 or 7 updates.

JRE 1.7.0_161 (and later 1.7 updates) and 1.6.0_171 (and later 1.6 updates) can still run Java content.  They cannot launch Java.

End-users who only have JRE 1.7 or JRE 1.6 -- and not JRE 1.8 -- installed on their Windows desktop will be unable to launch Java content.

End-users who need to launch JRE 1.7 or 1.6 for compatibility with other third-party Java applications must also install the JRE 1.8.0_152 or later JRE 1.8 updates on their desktops.

Once JRE 1.8.0_152 or later JRE 1.8 updates are installed on a Windows desktop, it can be used to launch JRE 1.7 and JRE 1.6. 

How do I get help with this change?

EBS customers requiring assistance with this change to Java deployment technology can log a Service Request for assistance from the Java Support group.

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 12.1 & 12.2

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 October 2017.
  • You can obtain JRE 7 updates from My Oracle Support.  See:

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

  • You can continue to do so until the end of Java SE 8 Deployment Technology Premier Support in March 2019
  • You can obtain JRE 8 updates from the Java SE download site or from My Oracle Support. See:

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), 10.10 (Yosemite), and 10.11 (El Capitan) 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 Issues

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
Categories: APPS Blogs

JRE 1.7.0_191 Certified with Oracle E-Business Suite 12.1 and 12.2

Tue, 2018-08-14 11:24

Java logo

Java Runtime Environment 1.7.0_191 (a.k.a. JRE 7u191-b09) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 12.1 and 12.2 for Windows-based desktop clients.

What's new in this update?

This update includes an important change: the Java deployment technology (i.e. the JRE browser plugin) is no longer available as of this Java release. It is expected that Java deployment technology will not be packaged in later Java 7 updates.

JRE 1.7.0_161  and later JRE 1.7 updates can still run Java content.  These releases cannot launch Java.

End-users who only have JRE 1.7.0_161 and later JRE 1.7 updates -- but not JRE 1.8 -- installed on their Windows desktop will be unable to launch Java content.

End-users who need to launch JRE 1.7 for compatibility with other third-party Java applications must also install the October 2017 CPU release JRE 1.8.0_151 or later JRE 1.8 updates on their desktops.

Once JRE 1.8.0_151 or a later JRE 1.8 update is installed on a Windows desktop, it can be used to launch JRE 1.7.0_161 and later updates on the JRE 1.7 codeline. 

How do I get help with this change?

EBS customers requiring assistance with this change to Java deployment technology can log a Service Request for assistance from the Java Support group.

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

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?

How can EBS customers obtain Java 7?

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 ("Deployment Technology") 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 (excluding Deployment Technology) is covered by Extended Support until December 2018.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 (excluding Deployment Technology) by December 2018. 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
Categories: APPS Blogs

JRE 1.6.0_201 Certified with Oracle E-Business Suite

Tue, 2018-08-14 11:20

Java logThe latest Java Runtime Environment 1.6.0_201 (a.k.a. JRE 6u201-b07) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 12.1 and 12.2 for Windows-based desktop clients.

What's new in this update?

This update includes an important change: the Java deployment technology (i.e. the JRE browser plugin) is no longer available as of the Java 1.6.0_171 release. It is expected that Java deployment technology will not be packaged in later Java 6 updates.

JRE 1.6.0_171 and later JRE 1.6 updates can still run Java content.  These releases cannot launch Java.

End-users who only have JRE 1.6.0_171 and later JRE 1.6 updates -- but not JRE 1.8 -- installed on their Windows desktop will be unable to launch Java content.

End-users who need to launch JRE 1.6 for compatibility with other third-party Java applications must also install the October 2017 PSU release JRE 1.8.0_152 or later JRE 1.8 updates on their desktops.

Once JRE 1.8.0_152 or a later JRE 1.8 update is installed on a Windows desktop, it can be used to launch JRE 1.6.0_171 and later updates on the JRE 1.6 codeline. 

How do I get help with this change?

EBS customers requiring assistance with this change to Java deployment technology can log a Service Request for assistance from the Java Support group.

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 Suiteand 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?
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.

How can EBS customers obtain Java 6 updates?

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 ("Deployment Technology") 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 (excluding Deployment Technology) is covered by Extended Support until December 2018.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by December 2018. 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 the latest Java release certified with E-Business Suite 12 servers.  See:

References

Related Articles
Categories: APPS Blogs

August 2018 Update to Integrated SOA Gateway

Mon, 2018-08-13 11:19

Oracle E-Business Suite Integrated SOA Gateway (ISG) provides an infrastructure to provide, consume, and administer Oracle E-Business Suite web services. It service-enables public integration interfaces registered in Oracle Integration Repository. These interfaces can be deployed as SOAP and/or REST-based web services. ISG also provides a service invocation framework to consume external SOAP based web services.

I am pleased to announce the availability of new consolidated patch for Integrated SOA Gateway in EBS R12.2 and EBS R12.1.3. This patch contains a new feature: REST support for Open Interface Tables. It also includes over four dozen fixes for stability and performance, and is highly recommended for all users. 

You can download the latest ISG consolidated patch here:

Oracle E-Business Suite Integrated SOA Gateway R12.2:
Patch 27949145:R12.OWF.C - ISG Consolidated Patch for Release 12.2 (18_3_3)

This is a cumulative patch update that includes all previously released ISG updates for EBS R12.2.

Oracle E-Business Suite Integrated SOA Gateway R12.1.3:
Patch 27941624:R12.OWF.B - ISG Consolidated Patch for Release 12.1 (18_3_3)

This is a cumulative patch update that includes all previously released ISG updates for EBS R12.1.3.

These patches include critical bug fixes in Integrated SOA Gateway. They include major updates in REST service enablement of Open Interface Tables and Views. If you are using Open Interface Tables and Views as REST based web services with previous ISG consolidated patch, you are required to uptake this new consolidated patch.
 
References

Related Articles

Categories: APPS Blogs

Oracle Access Manager 12c and Oracle Internet Directory 12c Certified with EBS 12.2 and 12.1

Mon, 2018-08-06 14:17

(Contributing Author:  Allison Sparshott)

I am pleased to announce that Oracle Access Manager 12c (12.2.1.3.0) and Oracle Internet Directory 12c (12.2.1.3.0) are now certified with E-Business Suite Releases 12.2.3 and higher and Release 12.1.3 and higher.

Note:  We are currently in the process of certifying Oracle E-Business Suite Release 12.2.7 and higher with Oracle Unified Directory 12c.  You may monitor or subscribe to this blog for the latest EBS technology certification announcements. 

References

If you are implementing single sign-on for the first time, or are an existing Oracle Access Manager user, you may now integrate with Oracle Access Manager 12c using Oracle Access Manager WebGate and Oracle E-Business Suite AccessGate.

Refer to the following documents for instructions:

Related Articles

Categories: APPS Blogs

Oracle Grid 12c Release 2 (12.2) Certified with RAC 12.1 and EBS 12.2

Tue, 2018-07-31 19:45

I'm pleased to announce Oracle Grid 12c Release 2 (12.2) is now certified when using Oracle 12c Release 12.1 Real Application Clusters (RAC) with Oracle E-Business Suite Release12.2.  When using Oracle RAC 12.1 with Oracle E-Business Suite 12.2, you now have the option to use either Oracle Grid 12c Release 12.2 or 12.1. 

Configuring Oracle Grid and shared storage is a mandatory requirement for deploying Oracle Real Application Clusters (RAC). Note that the Cluster Ready Services (CSR) ORACLE_HOME, other locations and commands may differ between the two Oracle Grid 12c Releases. 

References

Categories: APPS Blogs

Quarterly EBS Upgrade Recommendations: July 2018 Edition

Mon, 2018-07-30 12:01

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

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

You can research these yourself using this Note:

Upgrade Recommendations for July 2018

  EBS 12.2  EBS 12.1  EBS 12.0  EBS 11.5.10 Check your EBS support status and patching baseline

Apply the minimum 12.2 patching baseline
(EBS 12.2.3 + latest technology stack updates listed below)

In Premier Support to September 30, 2023

Apply the minimum 12.1 patching baseline
(12.1.3 Family Packs for products in use + latest technology stack updates listed below)

In Premier Support to December 31, 2021

In Sustaining Support. No new patches available.

Upgrade to 12.1.3 or 12.2

Before upgrading, 12.0 users should be on the minimum 12.0 patching baseline

In Sustaining Support. No new patches available.

Upgrade to 12.1.3 or 12.2

Before upgrading, 11i users should be on the minimum 11i patching baseline

Apply the latest EBS suite-wide RPC or RUP

12.2.7
Sept. 2017

12.1.3 RPC5
Aug. 2016

12.0.6

11.5.10.2
Use the latest Rapid Install

StartCD 51
Feb. 2016

StartCD 13
Aug. 2011

12.0.6


11.5.10.2

Apply the latest EBS technology stack, tools, and libraries

AD/TXK Delta 10
Sept. 2017

FND
Apr. 2017

EBS 12.2.6 OAF Update 13
July 2018

EBS 12.2.5 OAF Update 20
July 2018

EBS 12.2.4 OAF Update 19
May 2017

ETCC
Apr. 2018

Web Tier Utilities 11.1.1.9

Daylight Savings Time DSTv28
Nov. 2016

Upgrade to JDK 7

Web ADI Bundle 5
Jan. 2018

Report Manager Bundle 5
Jan. 2018

FND
Apr. 2017

OAF Bundle 5
Jun. 2016

JTT Update 4
Oct. 2016

Daylight Savings Time DSTv28
Nov. 2016

Upgrade to JDK 7

 

 

Apply the latest security updates

July 2018 Critical Patch Update

SHA-2 PKI Certificates

SHA-2 Update for Web ADI & Report Manager to Feb 2020

Migrate from SSL or TLS 1.0 to TLS 1.2

Sign JAR files

July 2018 Critical Patch Update

SHA-2 PKI Certificates

SHA-2 Update for Web ADI & Report Manager to Feb 2020

Migrate from SSL or TLS 1.0 to TLS 1.2

Sign JAR files

Oct. 2015 Critical Patch Update April 2016 Critical Patch Update Use the latest certified desktop components

Use the latest JRE 1.8, 1.7, or 1.6 release that meets your requirements.

Switch to Java Web Start

Upgrade to IE 11

Upgrade to Firefox ESR 60

Upgrade Office 2003 and Office 2007 to later Office versions (e.g. Office 2016)

Upgrade Windows XP and Vista and Win 10v1507 to later versions (e.g. Windows 10v1607)

Use the latest JRE 1.8, 1.7, or 1.6 release that meets your requirements

Switch to Java Web Start

Upgrade to IE 11

Upgrade to Firefox ESR 60

Upgrade Office 2003 and Office 2007 to later Office versions (e.g. Office 2016)

Upgrade Windows XP and Vista and Win 10v1507 to later versions (e.g. Windows 10v1607)

    Upgrade to the latest database Database 11.2.0.4 or 12.1.0.2 Database 11.2.0.4 or 12.1.0.2 Database 11.2.0.4 or 12.1.0.2 Database 11.2.0.4 or 12.1.0.2 If you're using Oracle Identity Management

Upgrade to Oracle Access Manager 11.1.2.3

Upgrade to Oracle Internet Directory 11.1.1.9

Migrate from Oracle SSO to OAM 11.1.2.3

Upgrade to Oracle Internet Directory 11.1.1.9

    If you're using Oracle Discoverer

Migrate to Oracle
Business Intelligence Enterprise Edition (OBIEE), Oracle Business
Intelligence Applications (OBIA).

Discoverer 11.1.1.7 is in Sustaining Support as of June 2017

Migrate to Oracle
Business Intelligence Enterprise Edition (OBIEE), Oracle Business
Intelligence Applications (OBIA).

Discoverer 11.1.1.7 is in Sustaining Support as of June 2017

    If you're using Oracle Portal Migrate to Oracle WebCenter  11.1.1.9 Migrate to Oracle WebCenter 11.1.1.9 or upgrade to Portal 11.1.1.6 (End of Life Jun. 2017).

 

 
Categories: APPS Blogs

Critical Patch Update for July 2018 Now Available

Wed, 2018-07-18 10:09

The Critical Patch Update (CPU) for July 2018 was released on July 17, 2018. 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.

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

It is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches.

The next four Critical Patch Update release dates are:

  • October 16, 2018
  • January 15, 2019
  • April 16, 2019
  • July 16, 2019
References Related Articles
Categories: APPS Blogs

Elliptic Curve Cryptography Certificates Now Certified with EBS Release 12.1

Tue, 2018-07-10 09:17

We are pleased to announce that Elliptic Curve Cryptography (ECC) certificates are now certified for use with Oracle E-Business Suite Release 12.1.

Key Points

Related Articles

References

Categories: APPS Blogs

SAN and Wildcard Certificates Certified with EBS 12.2

Mon, 2018-07-09 08:30

We are pleased to announce that Subject Alternative Name (SAN) and Wildcard Certificates are now certified with Oracle E-Business Suite 12.2 when enabling TLS.

Note: We previously announced certification of SAN and Wildcard Certificates with Oracle E-Business Suite Release 12.1.

What are SAN and Wildcard Certificates?

The use of the SAN field in a certificate request (CSR) allows you to specify multiple host names to be protected by a single public key certificate. Use of SAN will also allow using a single certificate for multiple domains.

A Wildcard Certificate is a public key certificate that can be used with multiple sub-domains of a domain.

Note: The latest releases of some browsers (e.g. Google Chrome) now require a SAN extension. Check your browser to determine if SAN is required.

How do you deploy SAN or Wildcard Certificates?

In the CSR SAN field, you may use the subjectAltName value, and optionally also use the wildcard character:

  • Example 1: SAN field entry for the CSR:

subjectAltName = DNS:www.example.com,DNS:example.com

  • Example 2: SAN field entry with a wildcard for the CSR:

subjectAltName = DNS:*.example.com

If you have already enabled TLS, you may need to redo your CSR using the SAN field. Check with your CA regarding their specific requirements for adding SAN. If you have not enabled TLS, simply follow the instructions for doing so, using the SAN field accordingly.

Note: We highly recommend that all customers migrate to TLS. If you have not already migrated to TLS, please do so as soon as possible.

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

Related Articles References
Categories: APPS Blogs

New OA Framework 12.2.6 Update 13 Now Available

Fri, 2018-07-06 09:03

Web-based content in Oracle E-Business Suite Release 12 runs on the Oracle Application Framework (also known as OA Framework, OAF, or FWK) user interface libraries and infrastructure.

We periodically release updates to Oracle Application Framework to fix performance, security, and stability issues.

These updates are provided in cumulative Release Update Packs, and cumulative Bundle Patches that can be applied on top of the Release Update Packs. In this context, cumulative means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for Oracle E-Business Suite Release 12.2.6 is now available:

Oracle Application Framework (FWK) Release 12.2.6 Bundle 13 (Patch 27948803:R12.FWK.C)

Where is this update documented?

Instructions for installing this OAF Release Update Pack are in the following My Oracle Support knowledge document:

Who should apply this patch?

All Oracle E-Business Suite Release 12.2.6 users should apply this patch. Future OAF patches for EBS Release 12.2.6 will require this patch as a prerequisite. 

What's new in this update?

This bundle patch is cumulative: it includes all fixes released in previous EBS Release 12.2.6 bundle patches.

In addition, this latest bundle patch includes fixes for the following three issues:

  • If a user accesses a nonexistent function via OA.jsp just after an application services restart, any Oracle E-Business Suite URL shows an error page.
  • When a user exports table data using the BNE Export button, a NullPointer exception is raised if the table has a dynamic poplist.
  • If BNE Export is enabled, an InvalidObjAccessException is raised when loading a product page.

Related Articles

Categories: APPS Blogs

New OA Framework 12.2.5 Update 20 Now Available

Mon, 2018-07-02 11:10

Web-based content in Oracle E-Business Suite Release 12 runs on the Oracle Application Framework (also known as OA Framework, OAF, or FWK) user interface libraries and infrastructure. Since the initial release of Oracle E-Business Suite Release 12.2 in 2013, we have released a number of cumulative updates to Oracle Application Framework to fix performance, security, and stability issues.

These updates are provided in cumulative Release Update Packs, and cumulative Bundle Patches that can be applied on top of the Release Update Packs. In this context, cumulative means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for Oracle E-Business Suite Release 12.2.5 is now available:

Where is this update documented?

Instructions for installing this OAF Release Update Pack are in the following My Oracle Support knowledge document:

Who should apply this patch?

All Oracle E-Business Suite Release 12.2.5 users should apply this patch.  Future OAF patches for EBS Release 12.2.5 will require this patch as a prerequisite. 

What's new in this update?

OAF bundle patches are cumulative: they include all fixes released in previous bundle patches.

This latest patch also provides fixes for the following issues:

  • In attachment image style, adding an attachment fails when a primary key of an entity map has a null value.
  • There is no warning message when a user navigates to the preferences page after making changes to a page that has the property 'Warn About Changes' set to true.
  • FND_STATE_LOSS_ERROR is displayed for Oracle Configurator flow when diagnostic logging is enabled.

Related Articles

Categories: APPS Blogs

EBS 12.2 Rapid Install Guide Updated and Streamlined

Thu, 2018-06-07 12:02

A significant number of customers have successfully installed Oracle E-Business Suite 12.2. In doing so, many have provided feedback on how we could improve the installation process and documentation.

I'm pleased to announce that in conjunction with our efforts to improve the EBS 12.2 Upgrade Guides, we have also incorporated customer feedback into the latest published Oracle E-Business Suite 12.2:  Using Rapid Install Guide available in the Oracle E-Business Suite Web Library.

What's New?

The following enhancements have been made to the Oracle E-Business Suite Release 12.2:  Using Rapid Install Guide:

  • Reorganized and simplified chapters and steps
  • Removed the Upgrade chapter which is now incorporated directly in the related Oracle E-Business Suite Release 12.2 Upgrade Guide
  • Reduced the number of self references and external references and confirmed all remaining references
  • Leveraged new documentation tags for actionable references and steps

If you are already working on a Oracle E-Business Suite 12.2 installation, there's no need to switch to the recently updated Rapid Install Guide. If you are getting ready to start an installation, be sure to use the latest updated guide.

References

Related Articles

Categories: APPS Blogs

New OA Framework 12.2.4 Update 19 Now Available

Thu, 2018-05-24 10:54

Web-based content in Oracle E-Business Suite Release 12 runs on the Oracle Application Framework (also known as OA Framework, OAF, or FWK) user interface libraries and infrastructure. Since the initial release of Oracle E-Business Suite Release 12.2 in 2013, we have released a number of cumulative updates to Oracle Application Framework to fix performance, security, and stability issues.

These updates are provided in cumulative Release Update Packs, and cumulative Bundle Patches that can be applied on top of the Release Update Packs. In this context, cumulative means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for Oracle E-Business Suite Release 12.2.4 is now available:

Where is this update documented?

Instructions for installing this OAF Release Update Pack are in the following My Oracle Support knowledge document:

Who should apply this patch?

All Oracle E-Business Suite Release 12.2.4 users should apply this patch. Future OAF patches for EBS Release 12.2.4 will require this patch as a prerequisite. 

What's new in this update?

This bundle patch is cumulative: it includes all fixes released in previous EBS Release 12.2.4 bundle patches.

This latest bundle patch includes a fix for the following issues:

  • In the IE11 browser, selecting a value from a LOV causes the page to scroll to the top.

Related Articles

Categories: APPS Blogs

Four Enhancements for Concurrent Processing in EBS 12.1 Now Available

Wed, 2018-05-23 12:15

We have just released four new enhancements for Concurrent Processing in E-Business Suite 12.1.3:

  1. Storage Strategies for Log and Output File Locations: Create custom storage strategies for management of large numbers of concurrent processing log and output files. Customers can specify the strategy that best suits their particular needs. These strategies are called schemes.
  2. Output File Naming Strategies: The output file naming conventions are now based on USER.REQID and REQID.OUT. The old USER format is desupported.
  3. Timed Shutdown: submit a normal, graceful shutdown and also specify a number of minutes after which an Abort command will be executed. After this number of minutes has passed, and Concurrent Processing has not yet shut down, the graceful shutdown will be converted to an Abort, and all remaining Concurrent Processing processes will be aborted.
  4. 64-bit Java Support for the Output Post-Processor Service: A 64-bit Java Virtual Machine (JVM) is now supported for the Output Post Processor (OPP). This support allows for a larger heap size to be set, compared to the 2G heap size that 32-bit Java allows. This larger heap size will decrease out-of-memory errors. Note that the 64-bit JVM can be run for the OPP service only.

Details about these four new enhancements are published here:

You can download these enhancements here:

Related Articles

 

Categories: APPS Blogs

Where Did the EBS Certifications Summary Go?

Tue, 2018-05-22 11:46

The official word on all EBS certifications is the Certifications database on My Oracle Support (MOS):

Since I announce all of my team's certifications here on this blog, I've also created a one-page summary of all blog articles covering EBS technology stack certifications. This summary page is maintained manually, so if there's any gap between the MOS Certifications database and this summary, the Certifications database wins.

Our blogging engine has changed multiple times over the years, so the URL for the Certifications summary has also changed periodically. The Certifications summary lives here now - update your bookmarks:

You can also navigate to it from this blog's home page by clicking on the "Check Your Certifications" button:

 

Categories: APPS Blogs

New Oracle E-Business Suite Person Data Removal Tool Now Available

Mon, 2018-05-21 10:27

Oracle is pleased to announce the availability of the Oracle E-Business Suite Person Data Removal Tool, designed to remove (obfuscate) data associated with people in E-Business Suite systems. Customers can apply the tool to select information in their E-Business Suite production systems to help address internal operational and external regulatory requirements, such as the EU General Data Protection Regulation (GDPR).

For more details, see:

Categories: APPS Blogs

Firefox Quantum ESR 60 Certified with EBS 12.1 and 12.2

Fri, 2018-05-18 12:08

Firefox ESR logo

Mozilla Firefox Quantum Extended Support Release 60 is certified as a Windows-based client browser for Oracle E-Business Suite 12.1 and 12.2. This includes 32-bit and 64-bit versions of Firefox Quantum.

What is Mozilla Firefox ESR?

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

E-Business Suite certified with Firefox Extended Support Releases Only

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

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

Plug-in Support removed in Firefox ESR 60

Mozilla has removed plug-in support in Firefox ESR 60. This means Firefox ESR 60 cannot run Forms-based content in EBS using the Java plugin method. 

If your Firefox ESR 60 end-users run Forms-based content in EBS, you must switch from the JRE plugin to Java Web Start

EBS patching policy for Firefox compatibility issues

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

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

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

EBS Compatibility with Firefox ESR security updates

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

Certified desktop operating systems

  • Windows 10 (32-bit and 64-bit)
  • Windows 8.1 (32-bit and 64-bit)
  • Windows 7 SP1 (32-bit and 64-bit)

References

Related Articles

Categories: APPS Blogs

Enabling Automatic EBS Application Tier Failover Between Physical Nodes on Oracle Solaris Clusters

Tue, 2018-05-15 15:28

This is a long-overdue tip of the hat to my colleagues in the Oracle Solaris group. I recently learned about an article they posted a couple of years ago about E-Business Suite 12.2 running on Oracle Solaris Cluster:

It is possible to install an EBS primary application tier and the associated WebLogic Administration Server on a logical host using Oracle Solaris Clusters. If the physical node hosting these EBS services fail, then Oracle Solaris Cluster will automatically failover to another physical node in the cluster.

This is very cool! In a traditional EBS multinode environment, any user sessions on an affected failed node that were in-flight (meaning, in the middle of a transaction) would be lost. Users would need to redo any transactions that were not saved when their node when down. Deploying EBS on Oracle Solaris Clusters allow for the failover without any impact to those in-flight transactions.

If you're already running EBS on Solaris, you should definitely monitor this blog.

Related Articles

Categories: APPS Blogs

Pages