Friday Jul 01, 2016

New OA Framework 12.2 Update 4 Now Available

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 is now available:

EBS 12.2.5 Bundle Patch 4

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 users should apply this patch.  Future OAF patches for EBS 12.2 will require this patch as a prerequisite. 

What's new in this update?

Fixes are included for following critical issues:

  • Users intermittently getting FND_SESSION_MGR_INST_ERROR. On session timeout, clicking on any responsibility on the homepage throws error "Error while invoking main menu: Application: FND, Message Name:FND_SESSION_MGR_INST_ERROR.
  • Spacing and alignment issues for read only message Choice and text areas.
  • JAWS is not reading the confirmation message which appears after adding an attachment inline, successfully.
  • When the query string of a view object is modified in the controller to remove unused where clause parameter conditions, using 'export' results in an exception.
  • Reverted fix which enabled caching of errors for beans on which server validation was disabled.

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

Related Articles


Thursday Jun 30, 2016

EBS 12.2 Data Masking Template Certified with EM 13c

(Contributing author:  Nirzari Raichura)

We're pleased to announce the certification of the E-Business Suite 12.2 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.2 cloned environments with EM13c using the My Oracle Support Note and template: 

What's New with Data Masking for EBS 12.2 and EM13c?

Online Patching with Oracle E-Business Suite 12.2 introduces the use of the Oracle Database feature Edition-Based Redefinition and editioning views.  The following updates occurred as part of this certification effort for compatibility with editioning views:

  • A new data masking template for Oracle E-Business Suite 12.2
  • New enhancements to the Data Masking Pack delivered with Oracle Enterprise Manager Cloud Control 13c
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

Wednesday Jun 29, 2016

Quarterly EBS Upgrade Recommendations: June 2016 Edition

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 June 2016

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

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

  3. EBS 12.1 users should upgrade to 12.1.3 RPC4 or 12.2.  Before upgrading, 12.1 users should be on the minimum minimum 12.1 patching baseline.

  4. EBS 12.1 users should switch their PKI certificates to SHA-2.

  5. EBS 12.2 users should upgrade to EBS 12.2.5, Database 11.2.0.4 or 12.1.0.2, the April 2016 AD tools, StartCD 51, and FMW 11.1.1.9.

  6. EBS 11i and 12.1 users should upgrade to Database 11.2.0.4 or 12.1.0.2.

  7. EBS 11i, 12.0, 12.1, and 12.2 customers should switch from Secure Socket Layer (SSL) to Transport Layer Security (TLS).

  8. EBS 11i, 12.0, 12.1, and 12.2 users must sign their environment's JAR files now.

  9. EBS 11i, 12.0, 12.1, 12.2 users should apply the April 2016 Critical Patch Update.

  10. Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 3 11.1.2.3.0.

  11. Oracle Internet Directory users should upgrade to Oracle Internet Directory 11g 11.1.1.9.

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

  13. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.9 or upgrade to Portal 11g 11.1.1.6.

  14. Firefox users should upgrade to Firefox Extended Support Release 45.

  15. Windows desktop users should migrate from older Java releases (including JInitiator) to JRE 1.8.0_91/92 (or later JRE 1.8 updates), JRE 1.7.0_101 (or later 1.7 updates), or JRE 1.6.0_115 (or later 1.6 updates).

  16. Windows XP and Office 2003 users should upgrade to later versions.

  17. Windows Vista users should upgrade to a later version of Windows.

  18. Windows Internet Explorer users should upgrade to IE 11.

  19. EBS customers on Exalogic and Exadata should follow the latest recommendations.

Tuesday Jun 28, 2016

TLS 1.2 Certified with E-Business Suite 12.2

I'm pleased to announce that Oracle E-Business Suite 12.2 inbound, outbound, and loopback connections are now certified with TLS 1.2, 1.1, and 1.0. If you have not already migrated from SSL to TLS, you should begin planning the migration for your environment. 

For more information on patching and configuration requirements when migrating to TLS 1.2 from TLS 1.0 or SSL, refer to the following My Oracle Support Knowledge Document:

The steps and configuration outlined in MOS Note 1367293.1 will address recent security vulnerabilities (e.g. Weak Cipher Suites/FREAK, POODLE, DROWN).

Configuration Options

  • Certification with TLS 1.2, 1.1 and 1.0

    The default Oracle E-Business Suite 12.2 configuration allows for the handshake between the client and server to negotiate and use the highest version of TLS (either 1.2, 1.1, or 1.0) supported end-to-end by all parties.

For example, if the outbound connection used by iProcurement is by default configured for TLS 1.2, 1.1 and 1.0 and if a call is made from Oracle E-Business Suite iProcurement to an external site that supports TLS 1.2 and a common cipher suite is found, then TLS 1.2 will be used end-to-end. If a call is made from Oracle E-Business Suite iProcurement to an external site that supports TLS 1.1 and a common cipher suite is found, then the handshake negotiation will resolve to use TLS 1.1 for the connection encryption.

  • Restricting the TLS Protocol (Optional Configuration)

You may optionally configure Oracle E-Business Suite to use the highest level of TLS certified with Oracle E-Business Suite Release 12.2. This option currently allows you configure TLS 1.2 for all inbound, outbound and loopback connections. 

Warning: If you restrict Oracle E-Business Suite 12.2 to use only TLS 1.2, this configuration could result in the inability to connect to other sites or browsers that do not support TLS 1.2.

  • Restricting Connections to HTTPS Only (Optional Configuration)

You also may optionally configure Oracle E-Business Suite to disable the HTTP port and use the HTTPS port only. 

Where can I learn more?
There are several guides and documents that cover Oracle E-Business Suite 12.2 secure configuration and encryption. You can learn more by reading the following:

SSL or TLS 1.0 Reference Note

If you are using SSL or TLS 1.0 and need to review your current configuration or renew your certificate, you may refer to the following:

Related Articles

Tuesday Jun 14, 2016

Frequently Asked Questions about EBS Security

We often receive questions about Oracle E-Business Suite security.  To assist with answering the most frequently asked questions about Oracle E-Business Suite security including secure configuration, auditing and encryption and others, the following new document is now available:

The questions in the FAQ are organized in the following sections:

  • Section 1: Secure Configuration and Architecture
  • Section 2: Auditing
  • Section 3: Access and Authentication
  • Section 4: Encryption and Masking             
  • Section 5: Connection Encryption

 Examples of questions answered in the new FAQ include:

  • What features are available for auditing Oracle E-Business Suite?
  • Do all DBAs require the APPS password?
  • Why should you migrate from SSL to TLS?
  • What versions of TLS are currently certified with Oracle E-Business Suite?
  • How do you configure HTTPs for Oracle E-Business Suite?
  • Can you use SHA-2 signed PKI certificates with Oracle E-Business Suite?

We plan to update this document on a regular basis.  As you read through the new document, please let us know if there are additional questions that we should consider adding.

Where can I learn more?

There are several guides and documents that cover Oracle E-Business Suite secure configuration and encryption for Release 12.1 and 12.2. You can learn more by reading the following:

Related Articles

Tuesday Jun 07, 2016

Tutorial: Using Oracle EBS Adapter in Integration Cloud Service

Oracle Integration Cloud Service (ICS) is Oracle’s integration Platform as a Service (iPaaS). It provides a web-based interface to integrate Software as a Service (SaaS) and on-premise applications. It includes various technology and application adapters.

Oracle E-Business Suite Adapter from Integration Cloud Service provides native and secure connectivity to Oracle E-Business Suite instance. It lets you create integrations with EBS public integration interfaces. As of ECS 16.2.5, the EBS Adapter supports: 

  • EBS R12.1.3, R12.2.3, R12.2.4 and R12.2.5.
  • PL/SQL-based REST Services for outbound integrations from ICS (also called inbound integrations to EBS).
  • Business Events and XML Gateway Messages for inbound integrations to ICS (also called outbound integrations from EBS).
  • Custom interfaces registered in Integration Repository.
  • Connectivity via an on-premise Agent. If EBS REST Services are directly accessible from ICS, on-premise Agent need not be configured. 

Screenshot of Adapter video

Here is a tutorial on using EBS Adapter for integrations in Integration Cloud Service:

It highlights the steps required to utilize the Business Event information from EBS. It is based on an Order-to-Manual Invoice scenario. When a Sales Order is booked in EBS Order Management, EBS raises a business event with Header Id and Status of the corresponding Sales Order. This information is used to retrieve details of the Sales Order. A manual invoice is created in EBS Accounts Receivable for this Sales Order.

This tutorial uses EBS Adapter as a Trigger (Source) as well as an Invoke (Target) connection. A Business Event is used to trigger the ICS integration whereas, PL/SQL-based REST Service is used to retrieve or fetch Sales Order details from EBS Order Management. It uses a REST Adapter to create manual invoice in EBS Accounts Receivables.

Tutorial Resources

References

Related Articles

Monday Jun 06, 2016

OCFS2 Certified with EBS 12.2 Shared File System Configurations

Oracle Cluster File System 2 (OCFS2) is now certified for use with E-Business Suite 12.2 when sharing a single file system between multiple application tier server nodes. 

Load-balancing E-Business Suite 12.2

You can improve your E-Business Suite 12.2 environment's fault tolerance, availability, and performance by distributing traffic across multiple application tier server nodes. For information about using multinode configurations, see:

EBS 12.2 load-balanced multinode architecture

Reducing your patching requirements with a shared file system

If you have multiple application tier server nodes, you need to apply an identical set of patches to each of them.  You can reduce your patching overhead by sharing a single file system between the individual application tier servers. Applying a patch to the shared file system allows it to be used by all application tier server nodes.  For information about using shared file system configurations in EBS 12.2, see:

What file system should you use for EBS 12.2?

Generally speaking, any fast, standards-compliant file system should work with Oracle E-Business Suite.  "Standards-compliant" can be interpreted to mean "any file systems that do not require code-level changes to the E-Business Suite." 

We do not test specific file systems with EBS 12.2, so we lack the data needed to recommend specific file systems.  For related information about NFS, GFS, ACFS, and what we use internally at Oracle, see: 

Why are we specifically certifying OCFS2?

EBS 12.2 uses two different file systems as part of its Online Patching infrastructure.  We have found that EBS 12.2 is sensitive to the performance characteristics of the underlying file system.

File system performance can sometimes be optimized by changing a few key mount options. We don't have the resources to test all of the available third-party file systems, but we can test Oracle's own file systems to ensure that you have the smoothest experience using them.  

What did we find when we tested OCFS2?

We tested EBS 12.2 under a variety of conditions, including applying patches using Online Patching while the EBS environment was under load.  We found that you should use the default block size for OCFS2, but aside from that, we didn't find any requirements for special mount options for OCFS2. 

Customers should also follow:

Related Articles

Wednesday Jun 01, 2016

New Blog: E-Business Suite and Oracle Cloud

Our team has just launched a new blog that will cover all aspects of running E-Business Suite on Oracle Cloud, including what you can do right now, and what you can plan for as our offerings evolve:

Cliff Godwin pictureThis new blog starts with an article from Cliff Godwin, Senior Vice President, Oracle E-Business Suite Development, that describes how this new blog will help E-Business Suite customers find a practical path to the cloud.

This new blog provides an excellent way of sharing your requirements and feedback with our teams focusing on this rapidly-evolving area.  I encourage everyone to monitor this blog for the latest updates on running E-Business Suite on the Oracle Cloud.  You can subscribe by email, too!

Wednesday May 18, 2016

XML Gateway Message Designer 2.6.3 Certified on Windows 10 for EBS 12.x

Windows 10 logoXML Gateway Message Designer 2.6.3 is certified on Windows 10 for E-Business Suite 12.1 and 12.2.  See:

Windows Compatibility Mode

XML Gateway Message Designer 2.6.3 is a 32-bit application that can be installed on 32-bit and 64-bit Windows 10 versions.  It must be installed with "Windows compatibility mode" set to "Windows XP (Service Pack 2)" or "Windows XP (Service Pack 3)".

Related Articles

Tuesday May 17, 2016

Workflow Builder 2.6.3 Certified on Windows 10 for EBS 12.x

Windows 10 logoWorkflow Builder 2.6.3 is now certified on Windows 10 desktops for Oracle E-Business Suite 12.1 and 12.2.  See:

Windows Compatibility Mode

Workflow Builder 2.6.3 is a 32-bit application that can be installed on 32-bit and 64-bit Windows 10 versions.  Workflow Builder 2.6.3 must be installed with "Windows compatibility mode" set to "Windows XP (Service Pack 2)" or "Windows XP (Service Pack 3)".

Related Articles

Monday May 16, 2016

Forms and Reports Developer 10g Certified on Windows 10 for EBS 12.x

Windows 10 logoForms Developer 10g and Reports Developer 10g are now certified on Windows 10 desktops for E-Business Suite 12.1 and 12.2. See:

Windows Compatibility Mode

The Forms Developer 10g and Reports Developer 10g applications are part of Oracle Developer Suite 10g.  These two tools are 32-bit applications that can be installed on 32-bit and 64-bit Windows 10 versions.  They must be installed with "Windows compatibility mode" set to "Windows XP (Service Pack 2)" or "Windows XP (Service Pack 3)".

EBS Server-side updates for Forms & Reports

For the latest Forms and Reports server-side updates for your E-Business Suite 12.1 environments, see:

E-Business Suite 12.2 already contains the latest Forms and Reports server-side updates. No additional server-side patches are required.

Related Articles


Friday May 13, 2016

JDeveloper 10g Certified on Windows 10 for EBS 12.1

Jdeveloper logoJDeveloper 10g is now certified for Windows 10 desktops for Oracle E-Business Suite 12.1.  See:

When 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.

This Note lists the JDeveloper with OA Extension updates for EBS 11i, 12.0, 12.1, and 12.2:

Pending Certification 

Our certification of JDeveloper 10g on Windows 10 for EBS 12.2 is still underway. 

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

Related Articles

The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Friday May 06, 2016

Oracle Linux 7 Pre-Install RPM available for EBS 12.1 and 12.2

The Linux Pre-Install RPM for Oracle E-Business Suite Release 12.1 and 12.2 on Oracle Linux 7 is now available for use by customers.

The package (oracle-ebs-server-R12-preinstall) is available on the 'addons' channel on the Oracle Unbreakable Linux Network (ULN, which requires a support contract) or from the Oracle public yum repository. It is recommended that this x86_64 Pre-Install RPM be installed on top of a 'minimal' installation of Oracle Linux to provide just the necessary packages to install and run Oracle E-Business Suite Release 12.

As with the Oracle Database Pre-Install RPMs, this RPM provides all required E-Business Suite packages for both the application and database tiers, while configuring the systems with particular kernel and other values to meet requirements published in our Linux x86-64 Installation and Upgrade Notes (see below).

This Pre-Install RPM will significantly reduce the preparation time of an environment prior to installing, upgrading or cloning an E-Business Suite R12 instance by performing the following tasks:

  • Downloading and installing all software package versions and dependencies required for installing E-Business Suite R12 (12.1, 12.2)
  • Creating the users oracle and applmgr for use as owners of the database and application tiers respectively, while setting hard and soft shell resource limits
  • Updating kernel parameters in /etc/sysctl.conf to recommended values
  • Sets DNS resolver parameters in /etc/resolv.conf to minimum recommended values
  • Sets 'numa=off' in the kernel in the kernel commandline
  • Disables 'Transparent Huge Pages (THP)' if enabled

For more information and details, please review the following documents:

Monday Apr 25, 2016

Part 2: Oracle E-Business Suite on Cloud FAQ

Contributing Author: Terri Noyes

Running Oracle E-Business Suite on Oracle Cloud is simple, but it doesn't take too much effort to come up with several great questions about this new set of options.  We have published a document that answers those questions:

This document is being updated regularly, so it's worth checking it periodically.  The latest version covers the following common questions:

EBS environments on cloudWhat is Oracle E-Business Suite on Oracle Cloud?

What capabilities are currently provided?

What are the key benefits to using Oracle E-Business Suite on Oracle Cloud?

Is Oracle releasing Oracle E-Business Suite as a SaaS application?

Does Oracle provide managed services for Oracle E-Business Suite on Oracle Cloud?

Are there additional fees for using Oracle E-Business Suite with Oracle Cloud?

Do I need to purchase Oracle E-Business Suite product licenses in order to use E-Business Suite on Oracle Cloud?

How do I deploy Oracle E-Business Suite on Oracle Cloud?

How do I restrict access to my Oracle E-Business Suite instances on Oracle Cloud?

Can I customize and extend Oracle E-Business Suite on Oracle Cloud?

How do I migrate customizations of Oracle E-Business Suite on the cloud to my on-premises production system?

Can we use our own custom data with Oracle E-Business Suite on Oracle Cloud?

Can we use the same certified third-party products we currently use on-premises with Oracle E-Business Suite on Oracle Cloud?

Can I use the Database Cloud Service with Oracle E-Business Suite?

Can I use the Exadata Cloud Service with Oracle E-Business Suite?

What tools are used for managing Oracle E-Business Suite environments on Oracle Cloud?

Does Oracle support deploying production instances of Oracle E-Business Suite on the Oracle Compute Cloud Service?

In addition to the FAQ, I'll cover some of these questions in more detail in future articles on this blog.  Stay tuned!

Related Articles

Friday Apr 22, 2016

Part 1: Running Oracle E-Business Suite on Oracle Cloud

[Contributing authors: Terri Noyes]

You can now run Oracle E-Business Suite on Oracle Cloud.  EBS customers can take advantage of rapid environment provisioning, elastic infrastructure that scales up on demand, and a pay-as-you-go model to reduce capital expenditures.

EBS customers have the option of deploying their EBS 12.1.3 and 12.2 environments on the Oracle Compute Cloud Service, and optionally in combination with the Oracle Database Cloud Service (DBCS), or the Exadata Cloud Service.

ebs on cloud

What EBS customers can do on the cloud

  • Provision new instances of E-Business Suite
  • Clone your own E-Business Suite environments to the cloud
  • Deploy development tools for E-Business Suite
  • Customize and extend your cloud-based E-Business Suite environments
  • Migrate those customizations to other cloud-based or on-premise EBS environments
  • Manage cloud and on-premise EBS environments using Oracle Application Management Suite
  • Use your certified third-party products with EBS cloud-based environments

What additional fees are required for EBS customers?

Oracle Cloud resources and services are available for subscription by Oracle customers. Customers who already own Oracle E-Business Suite product licenses may use their Oracle Cloud subscription to provision and deploy Oracle E-Business Suite instances on the Oracle Cloud. The deployed instances may be used for development, testing, training, production, etc. Once a customer acquires a subscription to Oracle Cloud, no additional Oracle E-Business Suite license or usage license is required.

Do I need to purchase EBS product licenses?

Oracle customers who already own Oracle E-Business Suite licenses may use the Oracle Cloud to host instances of their applications. Oracle’s Compute Cloud uses a “Bring your Own License” model, so customers who wish to use the Oracle Compute Cloud must already own a valid license to the software deployed on virtual machines in Oracle Compute Cloud.

Where can I get more details?

Related Articles


Wednesday Apr 20, 2016

Microsoft Ending Support for Vista in April 2017

Vista logoMicrosoft is ending support for Windows Vista on April 11, 2017.  The official support dates are published here:

Windows Vista is certified for desktop clients accessing the E-Business Suite today.  Our general policy is that we support certified third-party products as long as the third-party vendor supports them.  When the third-party vendor retires a product, we consider that to be an historical certification for EBS.

What can EBS customers expect after April 2017?

After Microsoft desupports Vista in April 2017:

  • Oracle Support will continue to assist, where possible, in investigating issues that involve Windows Vista.
  • Oracle's ability to assist may be limited due to limited access to PCs running Windows Vista.
  • Oracle will continue to provide access to existing EBS patches for Windows Vista.
  • 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 7, Windows 10)

What should EBS customers do?

Oracle strongly recommends that E-Business Suite customers upgrade their desktops from Windows Vista to the latest certified equivalents.  As of today, those are Windows 7, 8.1, and 10

Related Articles

Tuesday Apr 19, 2016

JRE 1.8.0.91/92 Certified with Oracle EBS 12.x

Java logo

Java Runtime Environment 1.8.0_91 (a.k.a. JRE 8u91-b14) and its corresponding Patch Set Update (PSU) JRE 1.8.0_92 and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows desktop clients.

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

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

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

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

What's new in this release?

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 12.1 & 12.2

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) desktops.  For details, see:

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

No.

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

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

Known Iusses

Internet Explorer Performance Issue

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

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

Form Focus Issue

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

References

Related Articles

JRE 1.7.0_101 Certified with Oracle E-Business Suite 12.x

Java logo

Java Runtime Environment 1.7.0_101 (a.k.a. JRE 7u101-b14) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 12.x for Windows-based desktop clients.

This certification addresses Oracle Security Alert for CVE-2016-0636.

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

JRE 1.6.0_115 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_115 (a.k.a. JRE 6u115-b12) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 12.x for Windows-based desktop clients.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

New EBS installation scripts

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

32-bit and 64-bit versions certified

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles

Friday Apr 08, 2016

April 2016 Updates to AD for EBS 12.2

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

We have now made available a ninth set of critical updates to AD (TXK is unchanged). If you are on Oracle E-Business Suite Release 12.2, we strongly recommend that you apply this new patch at your earliest convenience:



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

What's New in this Patchset?

This patchset includes six important updates for the following issues:

  • 22700342 - ADOP doesn't allow cutover if standby database is detected
  • 22861407 - Increase the variable size for L_PATCH_SERVICE in AD_ZD_ADOP
  • 22777440 - Grant privileges only if required while splicing
  • 22664007 - ORA-04068 error during patching
  • 22503374 - Script to grant unlimited quota privileges on 'SYSTEM' tablespace
  • 22530842/22567833 - Cannot drop table partition in run edition when patch edition exists

Related Articles

Monday Apr 04, 2016

Approvals for EBS 1.4 Now Available

Approvals for EBS mobile screenshotIf you haven't been following the excellent Workflow blog, you might have missed the announcement about the latest update to our Approvals for EBS mobile app.

Approvals for EBS 1.4 is part of a coordinated release of 17 E-Business Suite mobile apps.  These apps are designed to work with EBS 12.1.3 and 12.2 and are available for iOS and Android. 

This is our fifth set of updates to this family of EBS smartphone apps. For details about the entire set of EBS mobile apps, see:

What's New?

Updates to our Approvals for EBS 1.4 app include:

  • New approval types for:
    • Channel Revenue Management (claims, budgets, and offers)
    • Human Resources (absences and learning including class enrollments and certification subscriptions)
    • Inventory (move orders)
    • Maintenance (work orders, work requests, and work permits)
    • Order Management (RMAs, sales agreements, and quotes)
    • Quoting (quotes)
  • Ability to view attachments for approval requests
  • Ability to add custom workflows
  • Enhanced Pending Approvals by Type page
  • Improved subject card view in the Details page
  • Enhanced refresh interaction using a Pull to Refresh gesture in place of the Sync icon
  • Mobile Foundation
    • User installation and usage metrics for administrators
    • Updated look and feel for selected app interactions
    • Use of Oracle Mobile Application Framework (MAF) 2.2.2

Some of these new features require EBS server-side patches.  See the documentation above for details.


Monday Mar 28, 2016

JRE 1.8.0.77 Certified with Oracle EBS 12.x

Java logo

Java Runtime Environment 1.8.0_77 (a.k.a. JRE 8u77-b3) 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.

This certification addresses Oracle Security Alert for CVE-2016-0636.

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), and 10.10 (Yosemite) desktops.  For details, see:

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

No.

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

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

Known Iusses

Internet Explorer Performance Issue

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

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

Form Focus Issue

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

References

Related Articles

JRE 1.7.0_99 Certified with Oracle E-Business Suite 12.x

Java logo

Java Runtime Environment 1.7.0_99 (a.k.a. JRE 7u99-b4) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 12.x for Windows-based desktop clients.

This certification addresses Oracle Security Alert for CVE-2016-0636.

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

Wednesday Mar 16, 2016

Firefox ESR 45 Certified with EBS 12.1 and 12.2

Firefox ESR logo

Mozilla Firefox 45 Extended Support Release (ESR) is certified as a Windows-based client browser for Oracle E-Business Suite 12.1 and 12.2.

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.  From the Mozilla ESR FAQ:

What does the Mozilla Firefox ESR life cycle look like?

Releases will be maintained for approximately one year, with point releases containing security updates coinciding with regular Firefox releases. The ESR will also have a two cycle (12 week) overlap between the time of a new release and the end-of-life of the previous release to permit testing and certification prior to deploying a new version.

Maintenance of each ESR, through point releases, is limited to high-risk/high-impact security vulnerabilities and in rare cases may also include off-schedule releases that address live security vulnerabilities. Backports of any functional enhancements and/or stability fixes are not in scope.

At the end of the support period for an ESR version:

  • the release will reach its end-of-life
  • no further updates will be offered for that version
  • an update to the next version will be offered through the application update service

E-Business Suite to be certified with Firefox Extended Support Releases

New personal versions of Firefox are released roughly every six weeks.  It is impractical for us to certify these new personal 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 with the E-Business Suite.

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)
  • Windows Vista SP2

References

Related Articles

Monday Feb 22, 2016

Rapid Install StartCD 51 for EBS 12.2 Now Available

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

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

startCD 51

How Can I Obtain startCD 12.2.0.51?

  • You can download startCD 51 as Patch 22066363.

What's New in this Update?

Among other enhancements, startCD version 12.2.0.51:

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

Do I Need A New Stage Area For startCD 12.2.0.51?

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

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

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

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

startCD 51 extras

Where Can I Find More Information About Installing EBS?

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

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

References

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

Related Articles

Thursday Feb 18, 2016

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

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

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

What does "deprecate" mean?

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

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

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

What browsers will support the JRE 9 plug-in?

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

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

Will E-Business Suite still require Java?

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

Will E-Business Suite change how it starts Java?

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

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

When will EBS do this?

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

Related Articles

The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Thursday Feb 11, 2016

ETCC Tool Enhanced for Finding Mandatory EBS 12.2 Patches

Contributing author: Paul Holman

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

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

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

DB-ETCC Example

Why Does This Matter?

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

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

Coverage

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

Obtaining ETCC

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

References

Related Articles


Monday Feb 08, 2016

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

Java logo

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

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

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

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

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

What's new in this release?

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

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

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

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

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 12.1 & 12.2

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) desktops.  For details, see:

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

No.

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

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

Known Iusses

Internet Explorer Performance Issue

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

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

Form Focus Issue

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

References

Related Articles

JRE 1.7.0_97 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_97 (a.k.a. JRE 7u97-b2) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 12.x for Windows-based desktop clients.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

What's new in this release?

This JRE update is a CPU release. If you are running on the JRE 7 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 7 Plug-in.

For further information and bug fix details see Java CPU and PSU Releases Explained.

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

EBS + Discoverer 11g Users

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

JRE 7 End of Public Updates

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

Java Auto-Update Mechanism

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

Known Issues

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

References

Related Articles

JRE 1.6.0_113 Certified with Oracle E-Business Suite

Java logThe latest Java Runtime Environment 1.6.0_113 (a.k.a. JRE 6u113-b1) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 12.x for Windows-based desktop clients.

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

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

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

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

Effects of new support dates on Java upgrades for EBS environments

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

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

New EBS installation scripts

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

32-bit and 64-bit versions certified

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

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

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

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

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

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

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

References

Related Articles
About

Search

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