APPS Blogs

Oracle Database 11.2.0.4 and 12.1.0.2 New CPU End Dates

With the upcoming on-premise release of Oracle Database 12.2.0.1, Oracle has updated the Critical Patch Update (CPU) security patch end dates for 11.2.0.4 and 12.1.0.2.  Currently (as of January 2017), only 11.2.0.4 and 12.1.0.2 are supported for CPUs.

The CPU end-dates, which correspond with the end of Extended Support, have been extended to October 2020 for 11.2.0.4 and July 2021 for 12.1.0.2.  The first year of extended support for both versions is free until December 2018 for 11.2.0.4 and July 2019 for 12.1.0.2.

All Oracle databases should be updated to either 11.2.0.4 or 12.1.0.2, which provides at least three years of CPU support.  To ensure database security and minimize Oracle support costs, organizations should plan to upgrade 11.2.0.4 and 12.1.0.2 databases in 2018 and move to 12.2 at that time.  All new databases should be 12.1.0.2 and look to begin production use of 12.2 in late 2017 or with the release of 12.2.0.2 in eary 2018.

For databases that are not currently upgraded to 11.2.0.4 or 12.1.0.2, you must mitigate the risk of not applying security patches as there are at least 27 moderate to high risk unpatched security vulnerabilities in unsupported versions.  A number of these vulnerabilities allow any user, even with only CREATE SESSION, to compromise the entire database.  At a minimum, you must harden the database, limit network access as much as possible, review access and privileges, and enable auditing and monitoring in order to potentially identify attacks and compromises.

See MOS Support Note 742060.1 for more information on Oracle Database version support.

Oracle Database, Oracle Critical Patch Updates
Categories: APPS Blogs, Security Blogs

Is EBS Compatible with Microsoft Windows' New Supersedence Approach?

Steven Chan - Fri, 2017-01-27 02:05

Microsoft recently announced a change in how they handle the supersedence behaviour for several Windows releases prior to Windows 10.  Affected releases are:

  • Windows 7
  • Windows 8.1
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2

Windows Supersedence

Microsoft states:

The new supersedence behaviour allows organisations managing updates via WSUS or Configuration Manager to:

  • Selectively install Security Only Quality Updates (bundled by Month) at any time
  • Periodically deploy the Security Monthly Quality Rollup and only deploy the Security Only Quality Updates since then, and;
  • More easily monitor software update compliance using Configuration Manager or WSUS.

Does this affect EBS certifications?

No.  This new behaviour has no impact on EBS certifications with Windows desktop clients.  All current and future EBS desktop client certifications are expected to work with this new supersedence model for Windows security updates.

EBS customers do not have to wait for new certification announcements before rolling out security updates under this new supersedence model to their end-user desktop clients.

Related Articles


Categories: APPS Blogs

Original Windows 10 Release Desupported on March 26, 2017

Steven Chan - Thu, 2017-01-26 02:05

Microsoft recently announced the availability of Windows 10 version 1607, also known as the Windows 10 Anniversary Update.  With this latest release, Microsoft is desupporting the first release of Windows 10 -- version 1507 -- on March 26, 2017. After that date, no new patches will be created for version 1507.

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

What can EBS customers expect after March 2017?

After Microsoft desupports Windows 10 version 1507 in March 2017:

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

What should EBS users do?

Oracle strongly recommends that E-Business Suite upgrade their end-user desktops from Windows 10 version 1057 to the latest certified equivalents.  As of today, Windows 10 version 1607. 

What about EBS desktop-based client/server tools?

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

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

All of the tools still in use are certified with Windows 10 version 1067.

For complete details, see:

Related Articles

Categories: APPS Blogs

Which Windows 10 Service Branches Work with E-Business Suite?

Steven Chan - Wed, 2017-01-25 02:05

Windows 10 logoMicrosoft introduced a new model for updating Windows 10.  Instead of a traditional major upgrade cycle every few years, Microsoft has split their updates into three different "branches":

  • Current Branch (CB)
  • Current Branch for Business (CBB)
  • Long Term Servicing Branch (LTSB)

Microsoft has an overview of this service model here:

What is certified with EBS?

E-Business Suite 12.1 and 12.2 are certified with all three Windows 10 service options: Current Branch, Current Branch for Business, and the Long-Term Servicing Branch. 

All updates on all of those service branches are expected to work with EBS 12.1 and 12.2.  These updates include the Windows 10 Anniversary Update and the upcoming Windows 10 Creators Update. 

EBS 12.1 and 12.2 customers do not have to wait for certification announcements before updating their Windows 10 desktop clients to any of the updates on any of the three Windows 10 service branches.

What about EBS 11i and 12.0?

In 2015 we certified the Current Branch (the version released by that date) of Windows 10 with EBS 11i, 12.0, 12.1, and 12.2.

EBS 11i and 12.0 are now in Sustaining Support. This means that:

  • We have not tested any Windows 10 updates with EBS 11i since December 2015. 
  • We have not tested any Windows 10 updates with EBS 12.0 since January 2015.

Support implications for EBS 11i and 12.0 customers

We do not have any plans to test new Windows 10 updates (e.g. Windows 10 Anniversary Update or Creators Update) with either EBS 11i or 12.0.  We have no plans to release new EBS 11i or 12.0 patches for compatibility issues with new Windows 10 updates.

We will issue new EBS 12.1 and 12.2 patches only to fix issues reported with Windows 10 updates that can be reproduced with EBS 12.1 and 12.2.

If you are concerned about the ongoing compatibility of your Windows 10 desktops with EBS 11i or 12.0, you should:

  1. Upgrade to EBS 12.1 or 12.2
  2. Freeze your Windows 10 desktop configurations at their current working levels
  3. Perform you own testing of new Windows 10 updates before rolling them out to end-user desktops

Related Articles

Categories: APPS Blogs

Troubleshooting EBS 12.2 JDBC Connection Leaks

Steven Chan - Tue, 2017-01-24 02:05

Within Oracle WebLogic Server 10.3.6, Oracle E-Business Suite Release 12.2 employs Java Database Connectivity (JDBC) data sources to maintain a pool of connections for database connectivity. These JDBC data sources are associated with the managed servers (such as oacore and forms) in which Oracle E-Business Suite applications are deployed.

Connections are checked out and then returned to the data source when the request is complete. A connection is said to be leaked if it is not returned, no longer associated with the connection pool, or otherwise recoverable.

If you're seeing an unusual number of database connections or are having database performance issues, you might be experiencing a connection leak.  We've published a white paper that provides a framework for troubleshooting JDBC Data Source connection pool issues:

WLS option to monitor connection leaks

This white paper covers:

  • Using WebLogic Console in WebLogic Server (WLS) to monitor JDBC connections
  • Interpreting output from Level 1 and 2 diagnostics to identify connection leaks
  • Using GV$SESSION to list current JDBC connections and status

Getting support

If you continue to experience database performance issues or a disproportionate number of JDBC connections after going through that Note, you should log a Service Request with Oracle Support for assistance.

Related Articles

Categories: APPS Blogs

Quarterly EBS Upgrade Recommendations: January 2017 Edition

Steven Chan - Mon, 2017-01-23 02:05

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 January 2017


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.6
Sept. 2016

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 8
Sept. 2016

FND
Aug. 2016

EBS 12.2.5 OAF Update 9
Jan. 2017

EBS 12.2.4 OAF Update 14
Jan. 2017

ETCC
Nov. 2016

FMW 11.1.1.9

Daylight Savings Time DSTv28
Nov. 2016

12.1.3 RPC5

OAF Bundle 5
Note 1931412.1
Jun. 2016

JTT Update 4
Oct. 2016

Daylight Savings Time DSTv28
Nov. 2016



Apply the latest security updates

Oct. 2016 Critical Patch Update

SHA-2 PKI Certificates

SHA-2 Update for Web ADI & Report Manager

Migrate from SSL or TLS 1.0 to TLS 1.2

Sign JAR files

Oct. 2016 Critical Patch Update

SHA-2 PKI Certificates

SHA-2 Update for Web ADI & Report Manager

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

Upgrade to IE 11

Upgrade to Firefox ESR 45

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

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

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

Upgrade to IE 11

Upgrade to Firefox ESR 45

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

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



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), or Discoverer 11.1.1.7. Migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11.1.1.7.

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.



Categories: APPS Blogs

Decipher EBS Product Prefixes with EBS Technical Reference Manual

Steven Chan - Fri, 2017-01-20 02:06

Oracle E-Business Suite is a collection of over 200 individual products.  These products are grouped into product families such as Financials, Supply Chain Management, Human Resources, and so on.  Each product has its own ID, officially called an "Applications Product Prefix." Product prefixes can be either two or three characters in length.

If you're looking at a patch's README or some technical documentation, you might see a product ID that you don't recognize, for example, "BNE."  How do you figure out what this means?

You can look up product prefixes here:

Oracle E-Business Suite Technical Reference Manual eTRM

The eTRM covers the following EBS releases:

  • EBS 12.2
  • EBS 12.1
  • EBS 12.0
  • EBS 11.5.10 and earlier releases to EBS 11.5.7

The eTRM allows you to look up EBS database design and dependency information.  For example, you can enter the name of a database object (e.g. per_people_f) and see all of the information associated with that object.  You can also browse the FND Model or Oracle Data Diction from the FND or DBA tabs.


Categories: APPS Blogs

EBS 12.1 Data Masking Template Certified with EM 13c

Steven Chan - Thu, 2017-01-19 11:56
We're pleased to announce the certification of the E-Business Suite 12.1.3 Data Masking Template for the Data Masking Pack with Enterprise Manager Cloud Control 13c. You can use the Oracle Data Masking Pack with Oracle Enterprise Manager Cloud Control 13c to mask sensitive data in cloned Oracle E-Business Suite environments.  Due to data dependencies, scrambling E-Business Suite data is not a trivial task.  The data needs to be scrubbed in such a way that allows the application to continue to function. 

You may scramble data in E-Business Suite 12.1.3 cloned environments with EM13c using the My Oracle Support Note and template: 

What does masking do in an Oracle E-Business Suite environment?

Based upon the knowledge of the Oracle E-Business Suite architecture and sensitive columns, application data masking does the following:

  • De-identifies the data:  Scramble identifiers of individuals, also known as personally identifiable information (PII).  Examples include information such as name, account, address, location, and driver's license number.
  • Masks sensitive data:  Mask data that, if associated with personally identifiable information (PII), would cause privacy concerns.  Examples include compensation, health and employment information.  
  • Maintains data validity:  Provide a fully functional application.
References

Related Articles

Categories: APPS Blogs

Oracle E-Business Suite: 250 Security Vulnerabilities Fixed in the Last Year

Oracle has fixed 250 security vulnerabilities in the Oracle E-Business Suite from January 2016 to January 2017.  The past five Oracle Critical Update Updates (CPU) have included double or triple digit number of fixes for Oracle E-Business Suite.  Almost all these security vulnerabilities are exploitable in all versions of Oracle E-Business Suite including 11i, 12.0, 12.1, and 12.2.  Many of the 250 security vulnerabilities fixed are high risk vulnerabilities such as SQL injection, cross-site scripting (XSS), XML external entity attacks, and privilege escalation.

Unless your organization is applying the CPU patches immediately and have hardened the application, the Oracle E-Business Suite is extremely vulnerable and easily exploitable.  Significant defensive measures are required to protect Oracle E-Business Suite especially those with Internet facing modules such as iSupplier, iStore, iRecruitment, and iSupport.   A key layer of defense is Integrigy’s web application firewall for Oracle E-Business Suite, AppDefend, which provides virtual patching for these security bugs and additional protection from generic web application attack like SQL injection and cross-site scripting (XSS) and common Oracle E-Business Suite security misconfigurations.

Oracle E-Business Suite, Oracle Critical Patch Updates
Categories: APPS Blogs, Security Blogs

Oracle E-Business Suite 11i - Critical Patch Updates Extended for Tier 1 Support

As of December 2016, Oracle has extended Critical Patch Update (CPU) support for Oracle E-Business Suite 11.5.10 until October 2017 for additional fee Tier 1 support/Advanced Contract Support (ACS) customers.  Starting with the April 2016 Critical Patch Update (CPU), Oracle E-Business Suite 11.5.10 CPU patches are only available for customers with Tier 1/ACS support contracts.  See My Oracle Support Note ID 1596629.1 for more information.

Almost all security vulnerabilities discovered and patched in Oracle E-Business Suite 12.x are also present and exploitable in 11i.  A significant number of these security bugs are SQL injection bugs allow an attacker to execute SQL as the Oracle E-Business Suite APPS database account.  These attacks can easily compromise the entire application and database.  In the past year, Oracle has fixed 250 security vulnerabilities in Oracle E-Business Suite 11i and R12.

Oracle E-Business Suite 11i customers without Tier 1 support, as well as 12.0 customers, should take immediate take immediate defensive steps to protect the Oracle E-Business Suite 11i, especially those with Internet facing modules such as iSupplier, iStore, iRecruitment, and iSupport.  A key layer of defense is Integrigy’s web application firewall for Oracle E-Business Suite, AppDefend, which provides virtual patching for these security bugs and additional protection from generic web application attack like SQL injection and cross-site scripting (XSS) and common Oracle E-Business Suite security misconfigurations.

Oracle E-Business Suite, Oracle Critical Patch Updates
Categories: APPS Blogs, Security Blogs

JRE 1.8.0_121 Certified with Oracle EBS 12.1 and 12.2

Steven Chan - Wed, 2017-01-18 15:59

Java logo

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

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 12.1 & 12.2

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), 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 Iusses

Internet Explorer Performance Issue

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

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

Form Focus Issue

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

References

Related Articles
Categories: APPS Blogs

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

Steven Chan - Wed, 2017-01-18 15:54

Java logo

Java Runtime Environment 1.7.0_131 (a.k.a. JRE 7u131-b12) 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.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

EBS + Discoverer 11g Users

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

Known Issues

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

References

Related Articles
Categories: APPS Blogs

JRE 1.6.0_141 Certified with Oracle E-Business Suite 12.1 and 12.2

Steven Chan - Wed, 2017-01-18 15:53
Java logThe latest Java Runtime Environment 1.6.0_141 (a.k.a. JRE 6u141-b12) 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.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

New EBS installation scripts

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

32-bit and 64-bit versions certified

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Categories: APPS Blogs

Critical Patch Update for January 2017 Now Available

Steven Chan - Tue, 2017-01-17 02:05
The Critical Patch Update (CPU) for January 2017 was released on January 17, 2017. 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:

  • April 18, 2017
  • July 18, 2017
  • October 17, 2017
  • January 16, 2018
References Related Articles
Categories: APPS Blogs

Which Oracle Web Tier Utilities Patchsets Can Be Used with EBS 12.2?

Steven Chan - Mon, 2017-01-16 02:05
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)
The fifth-level digit in the Oracle Web Tier Utilities version is not relevant to E-Business Suite certifications.  In other words, you can apply any Oracle Web Tier Utilities patchsets that have been certified at the fourth-level digit. 

For example, we have certified EBS 12.2 with Web Tier Utilities 11.1.1.9. All of the following Web Tier Utilities patchsets will work with EBS 12.2:

  • Oracle Web Tier Utilities 11.1.1.9.0 (documented certification)
  • Oracle Web Tier Utilities 11.1.1.9.161225 (Fictitious future Bundle Patch for example purposes only-- this has not been released

This is sometimes shown in our documentation in either of the following ways:

  • Oracle Web Tier Utilities 11.1.1.9
  • Oracle Web Tier Utilities 11.1.1.9.x

The absence of a fifth-digit or the presence of an 'X' in the fifth digit's place means any fifth-digit level updates may be applied to an EBS 12.2 environment without requiring a new certification.  This applies to all environments, including test and production environments.

What is NOT certified

The Oracle Web Tier Downloads page has several listings for other things, including:

  • Oracle Web Tier 12cR2
  • Oracle HTTP Server 12.2.1.2
  • Oracle HTTP Server 12.2.1.1
  • Oracle HTTP Server 12.2.1

These have not been certified with Oracle E-Business Suite 12.2.  You should not apply these to your EBS 12.2 environment.

Related Articles

Categories: APPS Blogs

Will EBS Work with Windows 10 Creators Update?

Steven Chan - Fri, 2017-01-13 02:05

Windows 10 logoMicrosoft is releasing a major update to Windows 10 called the Windows 10 Creators Update:

This new update includes a number of features specifically aimed at enterprise and business users.  These include:

  • Windows Security Center
  • Windows Defender Advanced Threat Protection
  • In-place UEFI conversion

Differential downloads for Windows 10

Microsoft is also changing their packaging of major Windows 10 updates from full operating system downloads to smaller, incremental downloads.  This new delivery method is called the Unified Update Platform (UUP).

The new UUP delivery method will provide only the Windows 10 patches that have been released since the last time a desktop was updated.  

Will this work with EBS?

Yes.  Windows 10 is certified with all current EBS releases, including EBS 12.1 and 12.2. This existing certification is expected to apply to the upcoming Windows 10 Creators Update release.

The Unified Update Platform is not expected to require an additional certification.  Microsoft emphasizes that nothing changes with Windows 10 itself -- this only modifies the way that Win10 patches are delivered:

It’s important to note that with UUP, nothing will look or behave differently on the surface, UUP is all underlying platform and service optimization that happens behind the scenes.

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.

Categories: APPS Blogs

GoldenGate 12c Certified with E-Business Suite 12.2

Steven Chan - Thu, 2017-01-12 13:37

Oracle GoldenGate provides real-time capture, transformation, routing, and delivery of database transactions across heterogeneous systems.  The GoldenGate Administrator's Guide shows six supported topologies for generic databases.  Oracle GoldenGate 12c is now certified for a subset of three of those methods in Oracle E-Business Suite Release 12.2 environments:

  1. Unidirectional (Reporting Instance):  From the E-Business Suite to a reporting instance
  2. Broadcast (Data Distribution): From the E-Business Suite to multiple external databases
  3. Consolidation (Data Warehouse/Mart/Store): From multiple sources, including the E-Business Suite, into a single external database
Three supported GoldenGate topologies in E-Business Suite environments

Procedures for replicating information from E-Business Suite 12.2 using GoldenGate to a secondary system are documented in:

Unidirectional  reporting only

Certified Combinations

  • EBS 12.2.5 and later 12.2.x releases
  • Database 12.1.0.2 or 11.2.0.4
  • GoldenGate 12.1.2 and later 12.x releases

Replication to a Non-Editioned Target Database

EBS 12.2's Online Patching architecture has significant implications for data replication solutions implemented using Oracle GoldenGate. The Note above describes how to set up a unidirectional configuration of Oracle GoldenGate replication from an Oracle E-Business Suite Release 12.2 source database to a non-editioned target database.

Using GoldenGate with EBS 12.2 environments is significantly different from previous EBS releases.  If you are upgrading your GoldenGate + EBS 12.1 environment to EBS 12.2, and you must plan carefully for the new integration steps detailed in the documentation above.

Only Unidirectional replication for EBS

GoldenGate is an extremely powerful solution, and one of its most-interesting features is the ability to provide data replication in both directions.  In some generic scenarios, you can choose to make alterations to replicated data on the external instance and have those changes updated back in the source database.

Bidirectional replication is not permitted for E-Business Suite environments.  You can use GoldenGate to replicate EBS data to an external database, but you cannot move that altered data back into the EBS database.  GoldenGate's ability to read data in EBS databases is certified, but it must not be used to write to EBS databases.

"How" But Not "What"

GoldenGate is akin to a scalpel.  You're free to use it, but you must learn how to perform open heart surgery yourself.

The document above describes how to use GoldenGate to replicate data from the E-Business Suite to another system.  It doesn't provide any guidance about which database objects to replicate.

The E-Business Suite data model is vast, as you'd expect of something that has supports the integrated functioning of over 200 functional product modules.  GoldenGate is a development tool, and like all development tools, requires an expert-level understanding of the E-Business Suite data model for successful use.  Here's a good EBS data model resource:

Not Certified for EBS Migrations and Upgrades

GoldenGate is not certified for:

  • Upgrading E-Business Suite databases from one version to another
  • Migrating E-Business Suite databases from one operating system platform to another

Why not?  Oracle GoldenGate does not currently support the replication of all of the datatypes that are used by the E-Business Suite.  In addition, GoldenGate relies upon tables with primary keys for replication. EBS has over 10,000 tables without primary keys.  That means that attempting to use GoldenGate to migrate or upgrade an entire E-Business Suite database requires a combination of GoldenGate and other manual steps to preserve referential integrity.

Oracle does not currently have any plans to produce a certified or automated method of using GoldenGate for E-Business Suite upgrades or platform migrations.

EBS 12.2 customers should use our documented procedures for upgrades and migrations.  

Related Articles
Categories: APPS Blogs

New OA Framework 12.2.4 Update 14 Now Available

Steven Chan - Wed, 2017-01-11 02:03

Web-based content in Oracle E-Business Suite 12 runs on the Oracle Application Framework (OAF or "OA Framework") user interface libraries and infrastructure.   Since the release of Oracle E-Business Suite 12.2 in 2013, we have released several 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 Pack. "Cumulative" means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for EBS 12.2.4 is now available:

Screenshot EBS 12.2.4 OAF Bundle Patch 14

Where is the documentation for this update?

Instructions for installing this OAF Release Update Pack are here:

Who should apply this patch?

All EBS 12.2.4 users should apply this patch.  Future OAF patches for EBS 12.2.4 will require this patch as a prerequisite. 

What's new in this update?

Fixes are included for following critical issues:

  • Line separator for each row in table is missing in Workflow notification e-mail when viewed in Outlook mail client
  • Application menu entry in the Preferences sidebar was seen multiple times
  • Favorite created to open in a new window is opening in the same window from Framework Simplified Home page

This is a cumulative patch for EBS 12.2.4.  It includes updates previously released as Bundle 13 and patch 24618945.

This Bundle Patch requires the R12.ATG_PF.C.Delta.4 Release Update Pack as a mandatory prerequisite.

Related Articles


Categories: APPS Blogs

New OA Framework 12.2.5 Update 9 Now Available

Steven Chan - Tue, 2017-01-10 02:00

Web-based content in Oracle E-Business Suite 12 runs on the Oracle Application Framework (OAF or "OA Framework") user interface libraries and infrastructure.  Since the release of Oracle E-Business Suite 12.2 in 2013, we have released several 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 Pack. "Cumulative" means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for EBS 12.2.5 is now available:


Where is this update documented?

Instructions for installing this OAF Release Update Pack are here:

Who should apply this patch?

All EBS 12.2.5 users should apply this patch.  Future OAF patches for EBS 12.2.5 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 12.2.5 bundle patches.

This latest bundle patch also includes new fixes for several critical issues:

  • Partial Page Rendering event queuing fails in Internet Explorer 11 and Chrome browsers
  • Inability to reset the value of a read-only text input bean mapped to a list of values
  • Columns selected while creating a view are not displayed after running a query against the view
  • An error message is displayed when trying to import a personalization
Related Articles
Categories: APPS Blogs

Reminder: Upgrade Oracle Access Manager 11.1.2.2 to 11.1.2.3

Steven Chan - Mon, 2017-01-09 02:05

Oracle Fusion Middleware products get new Patch Set updates.  When a new Patch Set has been released, a 12 month Grace Period for the previous Patch Set begins.  Once that Grace Period ends, no new patches for the previous Patch Set will be released.

For more details, see:

Oracle Access Manager is part of a suite of products called "Oracle Identity and Access Management" (IAM).  OAM 11.1.2.2 was released in January 2014.  OAM 11.1.2.3 was released in May 2015, which means that the Grace Period for OAM 11.1.2.2 ended after May 2016. 

All E-Business Suite users running OAM 11.1.2.2 should upgrade to OAM 11.1.2.3 to remain under Error Correction Support. 

Related Articles

Categories: APPS Blogs

Pages

Subscribe to Oracle FAQ aggregator - APPS Blogs