Wednesday Jun 10, 2015

Does the Leap Second Affect the E-Business Suite?

Earth blue marbleBack in my salad days, I once took a university-level astronomy course, where I was surprised to learn that the earth's rotational speed varies due to climactic and geologic events.  These speed variations mean that the Coordinated Universal Time (UTC) occasionally needs to be adjusted by a leap second to remain synchronized with the mean solar time (UT1).

The next leap second is scheduled for June 30, 2015.

E-Business Suite users do not need to worry about the impact of leap seconds.  These time adjustment events do not have any impact on EBS operations or data integrity.


Thursday Jun 04, 2015

E-Business Suite Plug-in 12.1.0.4 for Enterprise Manager 12c Now Available

Oracle E-Business Suite Plug-in 12.1.0.4 is now available for use with Oracle Enterprise Manager 12c.  Oracle E-Business Suite Plug-in 12.1.0.4 is part of Oracle Enterprise Manager 12 Application Management Suite for Oracle E-Business Suite.

This latest plug-in extends EM 12c Cloud Control with E-Business Suite specific system management capabilities and features enhanced change management support.

The Oracle Enterprise Manager 12c Application Management Suite for Oracle E-Business Suite includes:

  • Functionality that was available in the previously-standalone Application Management Pack for Oracle E-Business Suite and Application Change Management Pack for Oracle E-Business Suite
  • Oracle Real User Experience Insight
  • Oracle Configuration & Compliance capabilities  

Licensing information  

A license for Oracle Enterprise Manager 12c Cloud Control is required to use this product. There is an additional licensing cost for the Application Management Suite for Oracle E-Business Suite.  A license for the Application Management Suite includes licenses for the E-Business Suite Plug-in, Oracle Real User Experience Insight, and Oracle Configuration & Compliance products.

This is a Development blog, and we don't have the background to discuss licensing in more detail.  We'd recommend contacting your Oracle account manager for more information about licenses.

Updates to product bundling

Features that were previously available in the standalone management packs are now packaged in the Oracle E-Business Suite Plug-in, which is certified with Oracle Enterprise Manager 12c Cloud Control: 

  • Functionality previously available for Application Management Pack (AMP) is now classified as “System Management for Oracle E-Business Suite” within the plug-in.
  • Functionality previously available for Application Change Management Pack (ACMP) is now classified as “Change Management for Oracle E-Business Suite” within the plug-in.

The Application Configuration Console and the Configuration Change Console are now native components of Oracle Enterprise Manager 12c.

Screenshot of AMP 12.1.0.3

New enhancements in this release

Discovery & Monitoring
  • Discover multiple Oracle E-Business Suite targets:
    • Customers now have the ability to discover multiple Oracle E-Business Suite targets in a single step using EMCLI command line discovery interface.
  • Instance Administration:
    • Instance administration helps customers to add or remove (Scale in or Scale out) application services, application nodes and managed servers by using simple user interface. This feature is very useful for those customers planning to upgrade to EBS 12.2.  This feature is supported for Oracle E-Business Suite releases 12.0.x, 12.1.x and 12.2.x.
  • Monitoring Concurrent Processing Service:
    • Concurrent processing monitoring has been enhanced to include additional capabilities to monitor Parallel Concurrent Processing, Concurrent Request Sets and Conflict Resolution Manager.
  • Monitor Mobile Web Applications (MWA) targets:
    • Capability to discover and monitor Mobile Web Applications Targets. Mobile Web Applications (MWA) is a node specific module. It will be discovered during application node targets discovery for Oracle E-Business Suite 12.1.3 & 12.2 instances. The MWA target will be added as a direct member of EBS system.
Configuration Management
  • Compare Technology Stack Components and Versions:
    • Ability to view, search and compare Oracle E-Business Suite technology stack components and versions. This feature is helpful to view the complete inventory of the technology stack and the versions for a given E-Business Suite environment.
  • Search and compare NLS patches:
    • In addition to search and compare EBS patches, now administrators have the ability to search and compare NLS patches.
Multi-level Hierarchical Approvals
  • Currently, Oracle Enterprise manager allows one level of approval for changes. In this release we have enhanced the capability for super administrator to define multi-level hierarchical approval process. Using this process a hierarchy of approvers and sequence of approval can be associated with a specific EBS target. Once the change request is submitted, the approval process will enforce the defined approval hierarchy.
Patch Recommendations
  • This is a significant new feature that can reduce or eliminate research time for DBAs. Patch recommendations functionality shows list of Oracle recommended patches that are not applied to the specific Oracle E-Business Suite instance. This includes Oracle E-Business Suite module specific patch recommendations for EBS 12.1 and 12.2. Also, technology stack patches for Database, WebLogic server, Oracle HTML server and Forms for EBS 12.2.x.
Customization Discovery & Reporting
  • Customers can now easily view the inventory of customizations they have in any given Oracle E-Business Suite environment. Customers can view or download a spreadsheet of discovered customizations by customization type.
Automated Cloning for Database and Applications Cloning
  • A single user interface has been included to facilitate automation of Database cloning and Application tier cloning. Administrators can schedule the Database and Applications cloning in a single procedure regardless of the database cloning method they use to clone E-Business Suite database.

Installation & Upgrades

  • Customers currently running on Enterprise Manager 12c, can use Self Update to download and install AMP 12.1.0.4

Prerequisites

  • Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4.0)
  • One or more of the following Oracle E-Business Suite Releases
  • Release 12.2.3 or 12.2.2
  • Release 12.1.3
  • Release 11.5.10 CU2 with 11i.ATG_PF.H.RUP7 or higher

References

Related Articles



Thursday May 28, 2015

11gR2 Transportable Database Certified for EBS 12.2 Database Migration

Database migration across platforms of the same "endian" (byte ordering) formats using the Transportable Database (TDB) process is now certified for Oracle E-Business Suite Release 12.2 with Oracle Database 11g Release 2 (11.2.0).

The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba):

    SQL> select platform_name, endian_format from v$transportable_platform;

Here's a list of relevant platforms certified for the EBS R12 (12.2) with 11gR2 on the database tier:

 Big Endian Platforms
 Little Endian Platforms
 Oracle Solaris on SPARC  Linux x86-64
 HP-UX Itanium  Oracle Solaris on x86-64
 IBM AIX on POWER Systems  MS Windows x64
 IBM: Linux on System z

Using Transportable Database is the fastest method for migration between platforms of the same endian format. A requirement of this migration process is that the source and target Database versions must match (including patch set version), so database upgrades as part of the migration cannot be done.

For migration between platforms of different endian formats, users must use alternative migration methods such as export/import (datapump).

References

Related Articles

Tuesday May 19, 2015

Firefox ESR 38 Certified with EBS 12.2 and 11i

Firefox ESR logo

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

The certification with EBS 12.1 is pending; see below.

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 8.1 (32-bit and 64-bit)
  • Windows 7 SP1 (32-bit and 64-bit)
  • Windows Vista SP2

References

Pending Certification

The certification of Firefox ESR 38 with Oracle E-Business Suite 12.1 is still in progress. An interoperability patch is required for this certification; this patch is being prepared. 

EBS 12.1 users should remain on Firefox ESR 31 for now. This certification will be announced in a separate blog article.

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


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. 


Monday May 11, 2015

EBS 12.2: New Getting Started Flowchart and Go-Live Readiness Checklist

There is a lot of EBS 12.2 documentation.  The best place to get a high-level overview of what is involved in implementing EBS 12.2 can be found here:

We've updated this document, which now includes:

  • Technical Planning Guide
  • Navigational flowchart 
  • Go-live checklist

The Technical Planning Guide helps you identify what you need to think about as you prepare to install or upgrade to Oracle E-Business Suite Release 12.2 and its most significant new feature, Online Patching.

Portion of EBS 12.2 implementation flowchart

Our new navigational flowchart shows you the detailed steps you need to take when moving to Release 12.2 from several different starting points:

  • Performing a fresh installation
  • Upgrading from a Release 11i or pre-12.2 Release 12.x system
  • Upgrading from a Release 12.2.x system to Release 12.2.4

The go-live checklist helps you identify and meet the high-level requirements for a successful go-live.  Checks include operating system requirements, install and upgrade process fundamentals, database and Oracle Fusion Middleware patches, and critical performance fixes. To help ensure success, we recommend proceeding with your go-live only after you have met these essential requirements.

Don't miss any updates

We're updating this document regularly to help streamline the EBS 12.2 implementation process. To be notified when it's updated, add it to your Favorites in My Oracle Support.  See:

Related Articles


Monday May 04, 2015

EBS 12.1 Certified on Oracle Linux 7 and Red Hat Enterprise Linux 7

Linux Tux logoOracle E-Business Suite Release 12.1 (12.1.3) is now certified on Oracle Linux 7 (64-bit) and Red Hat Enterprise Linux 7 (64-bit).

Installations of the E-Business Suite 12.1 on these operating systems require the application of the 12.1 RUP 3 (12.1.3). Cloning of existing EBS 12.1.3 Linux environments to these operating systems is also certified using the standard Rapid Clone process.

There are specific requirements to upgrade technology components such as the Oracle Database (to 11.2.0.4 or 12.1.0.2) and Fusion Middleware components as necessary. Other requirements, known issues, patches needed, etc. are noted in the Installation and Upgrade Notes (IUN) below and must be reviewed and implemented.

Pending Certifications

Certification of EBS Release 12.2 is in progress and will be announced at a later time when completed.

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

References

Thursday Apr 30, 2015

High Availability Configuration for Integrated SOA Gateway R12.2

Oracle E-Business Suite Integrated SOA Gateway (ISG) provides a SOA based infrastructure to provide, consume and monitor web services from E-Business Suite. In Release 12.2, ISG uses SOA Suite and E-Business Suite Adapter for SOAP based Web Services. REST Services provided by ISG do not depend on these external components in R12.2.

High Availability is one of the key requirements when providing web services in enterprise SOA implementations. Oracle recommends using a multi-node configuration to increase fault-tolerance and balance the transactional load in high-volume environments.

Multinode Integrated SOA Gateway EBS configuration diagram

Multiple E-Business Suite nodes can be configured with multiple SOA Suite nodes to provide high availability EBS SOAP Services. Oracle recommends using the SOA Suite Enterprise Deployment topology for multi-node configurations. When you deploy public EBS API as SOAP Services, it is deployed in all configured SOA Suite nodes. If a SOA node goes down, EBS SOAP Service requests are handled by the remaining available nodes.

References

Related Articles

Wednesday Apr 29, 2015

Database Migration Using 12cR1 Transportable Tablespaces Now Certified for EBS 12.1.3

As a follow up to a prior announcement, database migration across platforms of different "endian" or byte ordering formats using the Transportable Tablespaces (TTS) process is now certified for Oracle E-Business Suite Release R12 (12.1.3) with Oracle Database 12c Release 1 (12.1.0) as both the source and target database. The previous announcement covered the use of 11gR2 as the source and 12cR1 as the target database.

Furthermore, this TTS migration process uses the new 12c feature of full transportable export/import to move the entire database to further speed up the migration process. Also, users have the option to use cross platform incremental backup, a way to minimize database downtime and data transfer times.

This migration process requires a patch delivered by EBS Development that is 'Controlled', i.e. it requires a password obtainable through Oracle Support subject to approval. We released the required patch in this manner to assess suitability, potentially monitor customer issues due to the nature of this technology and to gauge uptake.

 The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba):

    SQL> select platform_name, endian_format from v$transportable_platform;

Here's a list of relevant platforms certified for the EBS R12 with 12cR1 on the database tier:

 Big Endian Platforms
 Little Endian Platforms
 Oracle Solaris on SPARC
 Linux x86-64
 HP-UX Itanium
 Oracle Solaris on x86-64
 IBM AIX on Power Systems
 MS Windows x64

For more information, please review the following:

Related Articles


Friday Apr 24, 2015

Best Practices for Optimizing Oracle XML Gateway Performance

Oracle XML Gateway allows you to generate, consume and transport business transaction documents via XML messages from Oracle E-Business Suite (EBS). It uses Oracle Workflow, Business Event System, Oracle Advanced Queuing, and other database components.

Leaving aside the network latency, the performance of XML Gateway’s inbound and outbound message processing depends on sizing and resource allocation of various components on the EBS application and database tiers.

XML Gateway architecture diagram

In Oracle E-Business Suite Release 12.2, we enhanced XML Gateway’s core execution engine for inbound message processing. Now, inbound transactions are mainly processed on the application tier. Outbound transactions are processed on the database tier. 

Our Applications Performance team executed performance tests on XML Gateway R12.2. The test cases involved payloads of varying sizes and concurrent messages. Based on our tests, we have published new performance tuning recommendations for Oracle XML Gateway. It includes sizing of Oracle Workflow listeners, updates of XML Gateway properties,  and tuning of memory and cache settings of OAFM Managed Servers:

References

Related Articles

Wednesday Apr 22, 2015

Quarterly EBS Upgrade Recommendations: April 2015 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 April 2015

  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 RPC3 or 12.2.

  4. EBS 12.2 users should upgrade to 12.2.4, the March 2015 AD/TXK tools, StartCD 49, and FMW 11.1.1.7.

  5. Users staying on EBS 11i and 12.1 should upgrade to Database 11.2.0.4 or 12.1.0.2.

  6. Users upgrading to EBS 12.2 should upgrade to Database 11.2.0.4.

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

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

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

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

  11. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_95 or later 1.6 updates or JRE 1.7.0_79 or later 1.7 updates or JRE 1.8.0_45 or later 1.8 updates.

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

  13. All Firefox users should upgrade to Firefox Extended Support Release 31.

  14. All EBS 11i, 12.0, 12.1, 12.2 users should apply the April 2015 Critical Patch Update.

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

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

  17. All EBS customers should switch from Secure Socket Layer (SSL) to Transport Layer Security (TLS).

Related Articles

Tuesday Apr 21, 2015

Best Practices for Testing EBS Endeca Applications

[Editor: This article was contributed by Prasanti Madireddi, Sr. Director, EBS Quality Assurance]

We introduced Oracle E-Business Suite Extensions for Oracle Endeca in 2013.  These EBS Extensions  provide selected EBS applications with Oracle Endeca-based capabilities. What is the best approach for testing your Endeca-based content for the E-Business Suite?

Endeca screenshot

Overall testing strategy

The primary goal is to test Endeca's integration with the EBS application. Customers should be able to use EBS products alongside the Endeca search features to search and summarize EBS data. 

Testing access to Endeca Applications

You must complete Endeca's role based access control (RBAC) before testing Endeca applications. You must create users, responsibilities and roles after the Endeca installation. After the RBAC setup is run, users can open Endeca pages and search for EBS data.

Testing Endeca integration with EBS products

Open Endeca pages from EBS. Verify the navigation from Endeca pages to self service pages and other windows, and also check the navigation back to the Endeca pages. Verify if the context is being set appropriately while navigating from one page to another.

Test key flows

Test all key flows in the Endeca products that you've integrated with the E-Business Suite. For example, if you've installed the Endeca extensions for iProcurement, the key flow in Oracle iProcurement would be to search for items in the Endeca page, compare the items, select some items and add them to cart and create a requisition.

Test data synchronization

Endeca maintains its own operational data store.  This database needs to be synchronized with the E-Business Suite database. Data synchronization is key to the functioning of Endeca pages. Run the full data synchronization for your installed Endeca extensions and verify that the data is loaded appropriately. Open Endeca pages to verify that the synchronized data is accurate and is displayed properly.

Some of the products control the data to be loaded through a profile option wherein a cut-off date can be specified. The full load process pulls in data entered after the cut-off date specified.

For example: in the Project Procurement - Supplier & Item Analysis dashboard, you can use the profile "PO: Item and Supplier Analysis Data-load Cut-off" to restrict the data that is sent to Endeca.

Test your full load processes to verify that the data is synchronized based on product-specific profiles.

You can run the Incremental Synchronization tools to keep the Endeca database updated after new changes have been made to the EBS database. Test this by creating, updating, or deleting data from EBS and then running the incremental graph to verify that the changes are reflected in Endeca pages.

Test all search components and capabilities

Endeca provides several options for filtering and searching data.

  • Search Box
  • Breadcrumbs
  • Guided Navigation
  • Range Filters
  • Tag Cloud
  • Book Marks

Use these search features to verify that your data is filtered appropriately.  Choose a small well-defined set of data for testing.

After you enter the search criteria, check that all Endeca components are refreshed appropriately with the queried data. This includes metric bars, result tables, record details and charts.

Most components have additional search capabilities, e.g. clicking on a value in a chart will further filter the data based on the clicked value. Check that those additional search features also show the latest synchronized data.

Additional Features

Endeca provides additional features: Metrics, Compare, and Export. The Metrics component provides a summary of the selected data. This component can be configured to highlight the data in different colors based on some specific conditions.  Test Metrics to verify the accuracy and the format of the summarized data.

The Compare feature is used to compare two objects, for example, to compare two items before adding them to a cart in iProcurement. Test the Compare feature to verify that the selected objects are compared appropriately.

Test the Export option to verify that the displayed data can be exported and saved in Excel spreadsheets.

Security Testing

Test your RBAC setup by verifying that only authorized users can access Endeca pages.

Test your RBAC setup by verifying that only authorized users can see the data that they're authorized to access in Endeca. For example, if a user is allowed to see data from Organization A but not  Organization B, verify that the appropriate Endeca pages also honor this data security check.

Descriptive Flex fields

Descriptive Flex fields (DFF) provide customizable expansion space on the EBS Endeca user interfaces and are used to track additional information. Endeca allows users to search on DFF attributes.

Test DFFs by creating new DFF definitions and then running the full load process to populate the DFF details. Search for the DFF values in the guided navigation.

Browser and mobile device compatibility

Test Endeca pages in the certified browsers that you've deployed in your organization.

Endeca pages should open in desktop clients, tablets, and mobile devices. Some components behave differently when opened in mobile devices. For example, the Guided Navigator is not rendered automatically in tablets and mobile devices; users open the Guided Navigator by clicking a button.

References

Thursday Apr 16, 2015

JRE 1.8.0_45 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_45 (a.k.a. JRE 8u40-b14) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 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 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

With the release of 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.

References

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


JRE 1.7.0_79 and 1.7.0_80 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_79 (a.k.a. JRE 7u79-b15) and 1.7.0_80 (7u80-b15) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i, 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?

What's new in this release?

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

  • CPU Release is JRE 1.7.0_79
  • PSU Release is JRE 1.7.0_80

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

There are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it.

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.

32-bit and 64-bit versions certified

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

Where are the official patch requirements documented?

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

For EBS 11i:

For EBS 12.0, 12.1, 12.2
EBS + Discoverer 11g Users

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

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

JRE 7 End of Public Updates

This is 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:

References

Related Articles

Java JRE 1.6.0_95 Certified with Oracle E-Business Suite

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

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 in this Java release?

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

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here:

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

32-bit and 64-bit versions certified

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

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

Coexistence of multiple JRE releases Windows desktops

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

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

What do Mac users need?

Mac users running Mac OS X 10.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

Wednesday Apr 15, 2015

Critical Patch Update for April 2015 Now Available

The  Critical Patch Update (CPU) for April 2015 was released on April 14, 2015.  Oracle strongly recommends applying the patches as soon as possible.

The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

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

The next four Critical Patch Update release dates are:

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

Tuesday Apr 14, 2015

EBS OA Extensions for JDeveloper Certified with Windows 8.1

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. These patchsets must be certified for the desktop operating system that is used to develop the OA Framework extensions. 

The latest updates of the OA Extensions for JDeveloper are certified with Windows 8.1.  There are updates for EBS 12.2.4, 12.2.3, 12.1.3, and 11.5.10.2.

For details, see:

Pending Certifications

The certification of the following Desktop Client tools on Windows 8.1 is still pending:

  • BI Publisher Desktop Tools (formally XML Publisher)
  • Discoverer Administrator/Desktop
  • Sales for Handhelds (Outlook Sync Client)
  • Warehouse Builder Client

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

Wednesday Apr 08, 2015

Third Recommended Patch Collection for EBS 12.1.3 Now Available

We are pleased to announce the availability of the third consolidated patch collection for Oracle E-Business Suite Release 12.1.3.  This patchset combines important patches for Release 12.1.3 into a single integrated and regression-tested patchset:

EBS 12.1.3 RPC3 Patch 20203366 download screenshot

Reasons to Apply RPC3

Oracle E-Business Suite Release 12.1.3 has been available for a while, and over its lifetime has been significantly enhanced in numerous ways. These enhancements and fixes are provided as individual patches, product family Release Update Packs (RUP), and product-specific Recommended Patch Collections (RPC).

For example, there are Recommended Patch Collections for Financials products such as General Ledger and Payables. On the technology side, there are patchsets such as the OA Framework 12.1.3.1 Consolidated Update Patch.

Identifying and applying all the individual patches, RUPs, and RPCs you need can be time-consuming. Complicating matters further, patchsets across multiple product families are generally not tested together.

Patches included in Oracle E-Business Suite Release 12.1.3+ RPC3 are also available individually, and may contain conditions and prerequisites relevant to their application. RPC3 includes all the recommended patches, along with their dependencies. Applying this patch in a single downtime patching window saves effort and time, rather than applying each recommended patch individually.

What's Included in RPC3?

The EBS 12.1.3+ RPC3 patchset includes the latest recommended patches and their dependencies for the following Oracle E-Business Suite products and product families:

  • Applications Technology (ATG)
  • Oracle Customer Relationship Management (CRM)
  • Oracle Financials (FIN)
  • Oracle Human Resource Management System (HRMS)
  • Oracle Procurement (PRC)
  • Oracle Projects (PJ)
  • Oracle Supply Chain Management (SCM)
  • Oracle Value Chain Planning (VCP)
  • Oracle Business Intelligence (BIS)

Is it necessary to apply this RPC if I only use a subset of Oracle E-Business Suite products?

Applying this RPC is recommended, even if you are using only a subset of Oracle E-Business Suite products. The patching utility 'adpatch' takes care of the files to be applied and generates them based on the product installation status.

I have already applied a few Family Packs included in this RPC. What happens when I apply this RPC?

Applying this RPC on top of already applied individual Family Packs will not harm your system because the patching utility 'adpatch' skips the files already applied on the system. You can apply the latest available RPC on your system.

A patch I need isn't included in this RPC. Why not?

This RPC combines recommended patches that were released after Release 12.1.3 into a single, integrated and regression-tested patch to help ensure a successful installation. If you don't find the patch in the RPC, it is likely that the patch was released after the patch list for the specific RPC was frozen or the patch was not marked "recommended" at the time the list was generated.

Should I only install the latest RPC? Do I have to install all prior RPCs? Should I install later individual product family RPCs?

To keep your system up-to-date with the most current Oracle E-Business Suite recommended patches, you should only apply the latest available RPC (which supersedes any prior release suitewide RPC) and thereafter either install individual product-level recommended patches as required or install the next suitewide level RPC when it becomes available.

Related Articles

Monday Apr 06, 2015

Reminder: Upgrade EBS 12.2 to FMW 11.1.1.7

Oracle periodically produces Fusion Middleware patchsets -- cumulative collections of fixes -- between major product releases.  All Oracle customers have 24 months to upgrade from the prior patchset when a later patchset is released.  This is called the "grace period."  You cannot request new patches for the prior patchset after the grace period ends.

Where are Fusion Middleware grace periods documented?

The specific grace periods for upgrading from one Fusion Middleware patchset to another are published here:

Do these apply to EBS customers?

Yes.  These dates apply to all Oracle customers, including E-Business Suite customers.  

Which EBS releases are affected?

E-Business Suite 12.2 originally included Fusion Middleware 11.1.1.6 as part of its Rapid Install. Specifically, The Oracle E-Business Suite Release 12.2's Rapid Install delivers three Fusion Middleware (FMW) components:

  1. Oracle WebLogic Server 10.3.6 (this is the "$FMW_HOME") 
  2. Oracle WebTier Utilities 11.1.1.6
  3. Oracle Common Home (Part of Oracle WebTier Utilities 11.1.1.6)

According to the Note above, new patches were released for FMW 11.1.1.6 until April 30, 2014. EBS customers can still download existing patches produced for FMW 11.1.1.6, but no new patches for FMW 11.1.1.6 are being produced now.

What is the impact on EBS 12.2 customers?

EBS 12.2 customers who need new patches for their FMW components must to be on FMW 11.1.1.7. The Oracle WebTier Utilities and the Oracle Common Home should be upgraded by EBS sysadmins to get the latest updates for security, performance, and stability. 

Where can I get these updates?

You can download the latest update for these two components here: 

Here are instructions on how to apply this update to your EBS 12.2 environment:

Related Articles

Thursday Mar 19, 2015

Oracle Database 12.1.0.2 Certified with EBS 12.1 on HP-UX Itanium, IBM AIX

As a follow up to a prior announcement, Oracle Database 12c Release 1 (12.1.0.2) is now certified with Oracle E-Business Suite Release 12.1.3 on the following additional platforms:

  • HP-UX Itanium (11.31)
  • IBM AIX on Power Systems (64-bit) (6.1, 7.1)

database 12c download screenshot

Database Feature and Option Certifications

The following database features and options are supported for use:

  • Advanced Compression
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO)
  • Database In-Memory Column Store (IM Column Store)
  • Real Application Clusters (RAC)
  • TDE Column Encryption and TDE Tablespace Encryption
  • Export/Import Process

The following are not yet certified:

  • Oracle Multitenant
  • Oracle Database Vault
  • Transportable Database and Transportable Tablespaces Data Migration Processes

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

References


Please refer to the platform specific Oracle Database Installation Guides for operating system and other prerequisites.
Please refer to the Oracle Database 12c Release 1 (12.1.0.2) New Features Guide 12c Release 1 (12.1) and Oracle Database Administrator's Guide for more information regarding the "In-Memory Column Store" feature.

Related Articles


Tuesday Mar 17, 2015

March 2015 Updates to AD and TXK for EBS 12.2

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

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

Delta 6 screenshot

You must always keep your AD and TXK codelevels synchronized. See the following Note for an additional FND patch needed, as well as complete installation instructions:

What's new in these updates?

  • Online Patching support for single file system on development or test systems
  • Integration of EBS Technology Consistency Checker (ETCC) with ADOP
  • Simplification and enhancement of adop console messages
  • Performance improvements in adop operations
  • Improved error reporting by Online Patching Log Analyzer utility
  • Change to default password for spliced products
  • Ability to deregister a custom application
  • Elimination of certain context variables
  • Support for Managed Server Independence Mode
  • Enhancements to Delete Application Tier Node
  • Minimize failures by pre-checking the availability of required ports during cutover phase
  • Removed dynamic generation of portlet.xml file used by Oracle E-Business Suite portlet producer
  • Provision to change passwords during rapid clone
  • Provision for txkSetAppsConf.pl to accept new arguments

What's changed in these updates?

  • Enhanced Rapid Clone
  • Improvements in handling when running ADOP on multiple nodes
  • Improvements to single sign-on functionality
  • Improvements to JVM and Admin server heap size
  • Improved ADOP flow
  • Improvements in ADOP flow communications handling
  • Improvements on Integrated SOA Gateway scripts
  • Support for unlimited number of application tier nodes

What Is a Codelevel?

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

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

Benefits of the Latest Codelevel

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

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

How Can I Get To the Latest Codelevel?

Installation instructions are here:

Further information about these updates can be found here:

Related Articles

Wednesday Mar 04, 2015

JRE 1.8.0_40 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_40 (a.k.a. JRE 8u40-b25) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 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 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

EBS + Discoverer 11g Users

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

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

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

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

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

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

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

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

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

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

No.

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

Impact of enabling JRE Auto-Update

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

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

With the release of 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) and 10.9 (Mavericks) 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.

References

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


Thursday Feb 26, 2015

Reminder: Upgrade Database 12.1.0.1 to 12.1.0.2 by July 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 12.1.0.1 Database patchset on July 22, 2015. All EBS customers on Database 12.1.0.1 should upgrade to the Database 12c 12.1.0.2 patchset before then. 

Related Articles

Tuesday Feb 24, 2015

How To Be Notified When MOS Notes Are Updated

We update our My Oracle Support (MOS) Notes regularly.  How do you find out when a new note is published or an existing one is updated?

There is a new MOS feature -- Hot Topics -- which emails you when notes on your Favorites list are updated.

Here's what to do:

  1. Mark the document of interest as a Favorite (by clicking the yellow star to the left of the document title). 
  2. From the More dropdown, choose Settings.
  3. On the left, under Personalization, choose Hot Topics E-Mail.
  4. Select the options that meet your requirements.
  5. Click the Apply button to save your changes.

Hot Topics

In this example, I am requesting a daily email (in HTML format) listing any notes on my Favorites list that have been updated since the last email was sent. An email will only be sent if at least one note has changed.

You can also specify products if you want to be notified of updates to any notes in a specific  product area.

Notifications of New Notes

Although this mechanism does not tell you when new Oracle E-Business Suite technology stack notes are published, you can find out by adding the technology stack roadmap notes as MOS Favorites and consequently receiving notification emails when they are updated:

This example screenshot shows content from a Hot Topics notification email advising me that these two roadmap notes (as well as a couple of other important notes) have been updated:


Typically, the roadmap notes are updated to reflect the addition of a new note that supports a new or modified feature or component. A look at the latest (topmost) entry in the change log of the roadmap will quickly tell you what's new. And if the new note is relevant, you can then add it to your Favorites and be notified when it changes.

We also recommend that you review the notes currently listed in the roadmaps, and mark as Favorites any that are relevant to the technologies you are using in your Oracle E-Business Suite installation.

References

  • My Oracle Support Help - Hot Topics E-Mail instructions
  • How to use Hot Topics Email notification to subscribe to Support Product News, SRs, Bugs, etc. and events so that you Never Miss an Important Update (Doc ID 793436.2)

Related Articles

Friday Feb 20, 2015

EBS 12.x certified with Apple Mac OS X 10.10 (Yosemite)

Apple logoOracle E-Business Suite Release 12 (12.1.3, 12.2.4 or higher) is now certified with Apple Mac OS X 10.10 (Yosemite) with the following desktop configuration:

  • Mac OS X 10.10 ("Yosemite" version 10.10.2 or higher)
  • Safari version 8 (8.0.3 or higher)
  • Oracle JRE 7 plugin (1.7.0_72 or higher) and JRE 8 plugin (1.8.0_31 or higher)

Users should review all relevant information along with other specific patching requirements and known limitations posted in:

Related Articles


Monday Feb 16, 2015

Tutorial: Publishing EBS 12.2 PL/SQL APIs as REST Services

Oracle E-Business Suite Integrated SOA Gateway provides REST and SOAP-based web service interfaces for public PL/SQL APIs registered in the EBS Integration Repository.  Here is a video tutorial that walks you through the process of deploying our seeded PL/SQL APIs as REST services in EBS 12.2.4:

Title page for ISG video tutorial

What is in this tutorial?

This step-by-step video tutorial walks you through the following:

  1. Search API in Integration Repository
  2. Deploy API as REST Service
  3. Create Grants for REST Service
  4. Invoke EBS REST Service (in JSON message format)
  5. Verify the result in EBS

This tutorial is recommended for integration architects, developers and implementers working on Oracle E-Business Suite integrations. The steps mentioned in this tutorial apply to Oracle E-Business Suite Integrated SOA Gateway R12.2.3 or R12.2.4 instance configured for REST Services (using My Oracle Support Doc ID 1311068.1).

References

Related Articles

Friday Feb 13, 2015

Reminder: EBS 11i Reverts to Sustaining Support on January 1, 2016

E-Business Suite 11.5.10.2 has been in Sustaining Support since December 1, 2013.  We have offered a one-time Exception to Sustaining Support (covering only Severity 1 issues) until December 31, 2015. 

This means that we will revert to Sustaining Support for Oracle E-Business Suite 11i 11.5.10.2 on January 31, 2016.  See:

Chart displaying EBS Premier and Extended Support dates

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

What happens after Extended Support ends?

The Exception to Sustaining Support coverage ends and we revert to the normal mode of Sustaining Support on January 1, 2016.  You can request diagnostic assistance for EBS 11i issues and download existing patches and documentation. Sustaining Support does not include:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For more specifics on Premier Support, Extended Support, and Sustaining Support, see:

Implications for EBS 11i users

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

New versions of desktop components may not work with EBS 11i. These include new releases of:

  • Windows
  • Mac OS X
  • Internet Explorer (IE)
  • Firefox
  • Safari
  • Office
  • Desktop-based Java Runtime Environment (JRE)  

New versions of server-based components may not work with EBS 11i. 

These include new releases of:

  • Server-based operating systems (Linux, AIX, HP-UX, Solaris, etc.)
  • Oracle Database
  • Java JDK
  • Fusion Middleware components (Oracle HTTP Server, JServ, Forms, etc.)

Related Articles

Thursday Feb 12, 2015

Database 12.1.0.2 Certified with E-Business Suite 11i

I’m pleased to announce that 12.1.0.2, the first patchset for Database 12c is now certified with Oracle E-Business Suite 11i. Be sure to review the 11i interoperability note.

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

Screenshot of Database 12.1.0.2 OTN download page

Oracle E-Business Suite Release 11i

Prerequisites
  • 11.5.10.2 + ATG PF.H RUP 7 and higher

Certified Platforms

  • Linux x86-64 (Oracle Linux 5) -- Database-tier only
  • Linux x86-64 (RHEL 5) -- Database-tier only
  • Oracle Solaris on SPARC (64-bit) (10)
  • Oracle Solaris on x86-64 (64-bit) (10) -- Database-tier only

Pending Platform Certifications

  • IBM AIX on Power Systems (64-bit)
  • HP-UX Itanium
  • IBM: Linux on System z 

Database Feature and Option Certifications
The following database options and features are supported for use:

Pending Feature/Option Certifications

  • Data Guard Redo Apply with Physical Standby Databases

Certifications Not Planned

  • Active Data Guard
  • Oracle Multitenant
  • Oracle In Memory Database
  • Oracle Database Vault
  • Transportable Database and Transportable Tablespaces data migration processes

About the pending certifications

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

EBS 11i References

Related Articles


Tuesday Feb 10, 2015

EBS 12.2 Certified on Microsoft Windows Server 2012 R2

Microsoft Windows Server logoOracle E-Business Suite Release 12.2 (12.2.3 and higher) is now certified on Microsoft Windows Server 2012 R2. For details, see:

The following editions of Microsoft Windows Server 2012 R2 are certified with Oracle E-Business Suite Release 12.2:

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

The above operating systems running as guests on Windows Server 2012 Hyper-V are also certified for Oracle E-Business Suite Release 12.2.

Users should also review the Microsoft Windows Server Catalog for information regarding hardware certified or supported with these operating system versions.

Unlike our certification of EBS 12.1.3 on Windows Server 2012 R2, E-Business Suite 12.2 can be installed directly on the platform with the use of the latest startCD (version 49 or higher) with Rapid Install.

Related Articles

Friday Feb 06, 2015

Internet Explorer 11 Certified with E-Business Suite 11.5.10.2

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

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

Certified IE 11 Modes

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

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

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

JRE 6, 7, and 8 are certified with EBS

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

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

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

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops. We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

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

"JInitiator version too low" errors

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

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

References

Related Articles


Thursday Feb 05, 2015

Reminder: Upgrade Database 10.2.0.5 Before July 2015

[Aug. 11, 2015 update: corrected reference to incorrect database patchset]

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 10.2.0.5 on July 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


About

Search

Categories
  • Oracle
Archives
« September 2015
SunMonTueWedThuFriSat
  
1
2
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
   
       
Today