Steven Chan

Subscribe to Steven Chan feed
Oracle Blogs
Updated: 2 hours 47 min ago

Windows 10-Related EBS Certifications: February 2017 Edition

Fri, 2017-02-10 02:05

Windows 10 logoE-Business Suite certifications with Microsoft Windows 10 have become hard to track.  This is partly due to the number of different things that run with Windows 10, including EBS components and browsers.  In addition, Microsoft is positioning Windows 10 as a "Windows as a service" offering, which has resulted in a series of recent changes to their release vehicles and offerings.

I've been covering these regularly. Here's a recap of everything related to EBS certifications on Windows 10 to date:

Windows 10, Java, and Edge

Microsoft Edge does not support plug-ins, so it cannot run Forms.  We are working on an enhancement request called “Java Web Start” to get around this Edge-limitation:


Categories: APPS Blogs

EBS Technology Codelevel Checker Updated (Feb 2107) for EBS 12.2

Thu, 2017-02-09 02:04

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

What's New

ETCC was recently updated to include bug fixes and patching combinations for the following:

Recommended Versions
  • January 2017 Oracle WebLogic Server PSU
  • Oracle Fusion Middleware 11.1.1.9
  • January 2017 Database 12.1.0.2 PSU and Proactive Bundle Patch
  • October 2016 Database 11.2.0.4 PSU and Engineered Systems Patch
Minimum Versions
  • October 2016 Oracle WebLogic Server PSU
  • Oracle Fusion Middleware 11.1.1.7
  • October 2016 Database 12.1.0.2 PSU and Proactive Bundle Patch
  • July 2016 Database 11.2.0.4 PSU and Engineered Systems Patch

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.

Related Articles

References

Categories: APPS Blogs

Database 12.1 Extended Support Fee Waived through July 2019

Wed, 2017-02-08 02:06

Oracle's Lifetime Support policy has three phases:  Premier Support, Extended Support, and Sustaining Support.  For details about coverage during each phase, see:

You can purchase a support plan for your licensed products to obtain Premier Support.  There is an additional fee for Extended Support. 

Premier Support for Database 12.1 runs to July 31, 2018. Extended Support for Database 12.1 runs to July 31, 2021. The Extended Support fee for Oracle Database 12c 12.1 has been waived to July 31, 2019.  See:

Related Articles


Categories: APPS Blogs

Database 11.2 Extended Support Fee Waived through December 2018

Tue, 2017-02-07 02:06

Oracle's Lifetime Support policy has three phases:  Premier Support, Extended Support, and Sustaining Support.  For details about coverage during each phase, see:

You can purchase a support plan for your licensed products to obtain Premier Support.  There is an additional fee for Extended Support. 

Extended Support for Database 11.2 runs to December 31, 2020. The Extended Support fee for Oracle Database 11gR2 11.2 has been waived to December 31, 2018.  See:

Related Articles


Categories: APPS Blogs

Reminder: Upgrade Oracle Access Manager 11.1.1.7 to 11.1.2.3

Mon, 2017-02-06 02:05

Oracle Access Manager (OAM) is part of a suite of products called "Oracle Identity and Access Management" (IAM).  OAM 11g (11.1.1) was released in 2009. Premier Support for OAM 11.1.1.x ended in June 2015.  Extended Support for OAM 11.1.1.x will end on June 30, 2017.

OAM 11.1.2.3 was released in May 2015 and is certified with E-Business Suite 12.1 and 12.2.  All E-Business Suite users running OAM 11.1.1.7 should upgrade to OAM 11.1.2.3 to remain under Error Correction Support. 

Related Articles

Categories: APPS Blogs

Will EBS Work with Windows 10 Anniversary Update?

Fri, 2017-02-03 02:05

Windows 10 logoMicrosoft recently released a major update to Windows 10 called the Windows 10 Anniversary Update (version 1607):

This update includes a number of features generally aimed at end-users, including updates to Cortana, Edge, etc.

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 applies to the Windows 10 Anniversary Update release. No additional EBS 12.1 or 12.2 certifications are required for Windows 10 Anniversary Update compatibility.

Related Articles


Categories: APPS Blogs

Updated: EBS 12.1 + Transportable Tablespaces with Incremental Backup Option

Thu, 2017-02-02 02:05

Database migration across platforms of different "endian" (byte ordering) formats using the Transportable Tablespaces (TTS) process has been certified for Oracle E-Business Suite Release R12.1 for several years. 

This certification has recently been updated to cover the use of the incremental backup option with Database 11.2.0.4 as a source.

Transportable Tablespaces

Does it meet your requirements?

Note that for migration across platforms of the same "endian" format, users are advised to use the Transportable Database (TDB) migration process instead for large databases. The "endian-ness" target platforms can be verified by querying the view V$DB_TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba) on the source platform:

SQL> select platform_name from v$db_transportable_platform;
If the intended target platform does not appear in the output, it means that it is of a different endian format from the source and Transportable Tablespaces (for large databases) or export/import should be used for database migration.

The use of Transportable Tablespaces can greatly speed up the migration of the data portion of the database - it does not affect metadata which must still be migrated using export/import. We recommend that users initially perform a test migration with export/import on their database with the 'metrics=y' parameter to find out the relative size of data vs metadata in their database and to have a basis to compare any gains in timing. Generally speaking, the larger the relative size of data (as compared to metadata), the more likely it would be that XTTS is suitable to reduce downtime.

Categories: APPS Blogs

MD5 Signed JAR Files Treated as Unsigned in April 2017

Wed, 2017-02-01 02:05

Oracle currently plans to disable MD5 signed JARs in the upcoming Critical Patch Update slated for April 18, 2017.  JAR files signed with MD5 algorithms will be treated as unsigned JARs.

MD5 JAR file signing screenshot

Does this affect EBS environments?

Yes. This applies to Java 6, 7, and 8 used in EBS 12.1 and 12.2.  Oracle E-Business Suite uses Java, notably for running Forms-based content via the Java Runtime Environment (JRE) browser plug-in.  Java-based content is delivered in JAR files.  Customers must sign E-Business Suite JAR files with a code signing certificate from a trusted Certificate Authority (CA). 

A code signing certificate from a Trusted CA is required to sign your Java content securely. It allows you to deliver signed code from your server (e.g. JAR files) to users desktops and verifying you as the publisher and trusted provider of that code and also verifies that the code has not been altered. A single code signing certificate allows you to verify any amount of code across multiple EBS environments. This is a different type of certificate to the commonly used SSL certificate which is used to authorize a server on a per environment basis. You cannot use an SSL certificate for the purpose of signing jar files. 

Instructions on how to sign EBS JARs are published here:

Where can I get more information?

Oracle's plans for changes to the security algorithms and associated policies/settings in the Oracle Java Runtime Environment (JRE) and Java SE Development Kit (JDK) are published here:

More information about Java security is available here:

Getting help

If you have questions about Java Security, please log a Service Request with Java Support.

If you need assistance with the steps for signing EBS JAR files, please log a Service Request against the "Oracle Applications Technology Stack (TXK)" > "Java."

Disclaimer

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

EBS 12.2.6 OA Extensions for Jdeveloper 10g Updated

Tue, 2017-01-31 02:04
Jdeveloper logoWhen you create extensions to Oracle E-Business Suite OA Framework pages, you must use the version of Oracle JDeveloper shipped by the Oracle E-Business Suite product team. 

The version of Oracle JDeveloper is specific to the Oracle E-Business Suite Applications Technology patch level, so there is a new version of Oracle JDeveloper with each new release of the Oracle E-Business Suite Applications Technology patchset.

The Oracle Applications (OA) Extensions for JDeveloper 10g for E-Business Suite Release 12.2.6 have recently been updated.  For details, see:

The same Note also lists the latest OA Extension updates for EBS 11i, 12.0, 12.1, and 12.2.

Related Articles

Categories: APPS Blogs

Cloning EBS 12.2 Environments Integrated with Oracle Access Manager

Mon, 2017-01-30 02:05

We have documented procedures for cloning EBS 12.2 environments.  We also have documented procedures for integrating EBS 12.2 environments with Oracle Access Manager (OAM) and Oracle Internet Directory (OID).  The next logical question would be: do we have documented procedures for cloning EBS 12.2 environments that have been integrated with OAM and OID?

Yes, we have published this here:

EBS OAM architecture

This Note provides a certified process and detailed steps to:

  • Clone EBS using Rapid Clone
  • Deregister the cloned EBS instance from OAM and remove AccessGate
  • Remove OID from the cloned EBS instance
  • Integrate the cloned EBS instance with OID
  • Integrate the cloned EBS instance with OAM
  • Reconfigure SSL

Related Articles

Categories: APPS Blogs

Is EBS Compatible with Microsoft Windows' New Supersedence Approach?

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

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?

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

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

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

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

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

JRE 1.8.0_121 Certified with Oracle EBS 12.1 and 12.2

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

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

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

Pages