Wednesday Dec 07, 2016

New OA Framework 12.2.5 Update 8 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 for EBS 12.2.5 is now available:

OA Framework 12.2.5 Update 8

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

What's new in this update?

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

This latest bundle patch includes new fixes for the following critical issues:

  • Formatting issues with Email notifications after 12.2.5 upgrade.
  • Popup is not rendering correctly with Right-to-Left language sessions in Internet Explorer when default browser language is set as Arabic.
Related Articles

Tuesday Dec 06, 2016

Troubleshooting RAC Cloning Issues in EBS 12.1

We have a white paper that outlines a framework for troubleshooting Rapid Clone issues:

Cloning EBS 12.1.3

Things can get more-involved if your E-Business Suite environment uses Real Application Clusters (RAC). There's another white paper that has more details about what to do if you encounter problems when cloning RAC-based EBS environments:

This whitepaper has additional RAC-specific information, such as:

  • Pairsfile.txt
  • RMAN restore phases
  • Secondary node context file creation
  • Known issues (e.g. RAC to RAC cloning causing inventory registration issues)

Related Articles

Monday Dec 05, 2016

Ten Years and Counting

This blog turned 10 this year.  When I started it in 2006 with this article, I had no idea that it would become what it is today.  Things certainly turned out differently than I expected. 


Photo credit: Fulvio Spada, Wikimedia Commons

This little blog now gets millions of visits a year.  It has helped us shape EBS to meet your needs better.  I've been schooled in the many ways that we can do things better for you.  I've been chastised for offhand editorial remarks and have learned to deal with hate mail.  I've learned how hard it is to be a journalist, to state just the facts and pare prose down to its simplest form, accessible to all (with this verbose article being an exception to that rule).

Over the years, I've had several people who have helped me paint this fence. Some of those people have since joined the ranks of Oracle's esteemed alumni.  Some still pitch in occasionally.  Either way, I'm grateful for their contributions over the years.  As with the Stone Soup parable, this little corner of the world is richer for their sharing their expertise with us.

I am sometimes mistaken as an expert, but the real experts are my colleagues and friends in the E-Business Suite division and our sister organizations across Oracle.  They deserve the real credit for all of their dedication, professionalism, and expertise. They are a brilliant team and I am always humbled by their desire to do the best for you.  I am privileged to work alongside them and talk about their achievements on their behalf.  Please join me in thanking all of them for their hard work in polishing EBS to a shine for you. 

And, of course, thank you for joining me on this journey.  I am fortunate to have many of the world's leading EBS experts as readers and friends, and they contribute to this blog in ways large and small.  This blog would not be the same without the lively interactions with all of you.  I look forward to seeing what lies down the road around the corner!

Friday Dec 02, 2016

Database Vault 12.1.0.2 Certified with EBS 12.1 and 12.2

Oracle Database Vault allows security administrators to protect a database from privileged account access to application data.  Database objects can be placed in protected realms, which can be accessed only if a specific set of conditions are met.

We are pleased to announce that Oracle Database Vault 12c 12.1.0.2 is now certified with Oracle E-Business Suite Release 12.2 and 12.1. To integrate Oracle Database Vault 12c with Oracle E-Business Suite Release 12.2 or 12.1, follow the instructions in the corresponding My Oracle Support Knowledge Document:



Note:  We deliver a default realm via two different patches for Oracle E-Business Suite 12.2 and 12.1 .  You may use the default realm as-is or choose a subset.

Pending Certifications with External Integrations

The following two configurations are still underway and pending:

  • Single Sign-On Integration with Oracle Access Manager
  • Oracle Discoverer

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

Related Articles

Thursday Dec 01, 2016

Which Oracle Internet Directory Patchsets Can Be Used With EBS?

You can apply any Oracle Internet Directory (OID) bundle patchsets that have been certified at the fourth-level digit to a certified Oracle E-Business Suite release.  The fifth-level digit in OID versions is not relevant to E-Business Suite certifications. 

For example, we have certified EBS 12.2 with OID 11.1.1.9. All of the following Oracle Internet Directory patchsets will work with EBS 12.2:

  • Oracle Internet Directory 11.1.1.9.0 (documented certification)
  • Oracle Internet Directory 11.1.1.9.3
  • Oracle Internet Directory 11.1.1.9.160719

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

  • Oracle Internet Directory 11.1.1.9
  • Oracle Internet Directory 11.1.1.9.x

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

Reference

Related Articles

Wednesday Nov 30, 2016

Load-Balancing EBS 12.2 Environments

You can use load-balancing routers (LBR) to protect your E-Business Suite 12.2 environment from system failures.  Load-balancers increase your environment's fault-tolerance and scalability by distributing load across a pool of servers. See: HTTP Layer Load-Balancing

HTTP Layer load-balancing is the most common method used in E-Business Suite environments. In this configuration, end-users navigate to a specific Web Entry Point that represents your E-Business Suite's domain name.  An HTTP Layer load-balancer routes all subsequent traffic for a specific user to a specific Web Node.

EBS LBR Architecture

HTTP Layer load-balancers may use heartbeat checks for node death detection and restart, and sophisticated algorithms for load-balancing.

DNS-Based Load-Balancing

When an end-user's browser attempts to access your E-Business Suite environment, your local Domain Name Server (DNS) can direct that user to a specific application server in a pool based on available capacity:


Traffic for that user's session will be handled by the application server 10.10.10.10, while other users' traffic may be directed to other application servers in the pool.  Like HTTP layer load-balancers, many DNS-based load-balancers use heartbeat checks against nodes and sophisticated algorithms for load-balancing.

Minimum Requirement:  Session Persistence

Oracle doesn't certify specific load-balancers or networking hardware with the E-Business Suite.  We've designed the E-Business Suite to be able to use load-balancers in general. Our instructions for configuring load-balancers should work for all standards-compliant networking solutions, whether they are hardware or software-based.

The minimum requirement is that a load-balancer support session persistence.  Persistence describes a mode where a client's initial HTTP connection is directed to a particular application server, and then subsequent HTTP requests from that client are directed to the same server.  As long as a load-balancer is able to handle session persistence (also referred to as "stickiness"), it's likely to work with the E-Business Suite.

Other load-balancing variations

EBS 12.2 can be deployed in a number of variations to handle specialized or advanced load-balancing requirements.  For details about implementing the following variations, see:

WLS Clusters: EBS 12.2 uses WebLogic Server.  It is possible to deploy multiple WebLogic Server instances in a cluster to increase scalability and fault-tolerance. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster’s capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server.

Multiple Web Entry Points:  It is possible to configure the same EBS environment to have multiple web entry points (URLs).  For example, users might be able to access your EBS environment via the following different URLs:

  • store.company.com
  • recruitment.company.com

Functional redirection:  It is possible to direct users to specific servers based upon the functional responsibilities that they chose.  For example, manufacturing end-users may be directed to a different pool of servers than, say, HRMS end-users.

Related Articles

Tuesday Nov 29, 2016

EBS Presentations at December 2016 UK Oracle User Group Meeting

Staff from Oracle E-Business Suite Development will be contributing to the APPS16 track of the UKOUG Conference & Exhibition 2016. The conference takes place at the International Convention Centre, Birmingham, England, and runs from Sunday 4th December to Wednesday 7th December.


Please bring your questions or issues about any aspect of running EBS: feel free to ask about overall strategy, specific deployment aspects, or anything else you want to know.

You'll also have the chance to attend numerous formal presentations from prominent Oracle speakers on many aspects of EBS. Here are some highlights.

On the Monday (5th), there is a great opportunity to hear the latest news from the general manager of EBS:

Another presentation that will be of particular interest to readers of this blog is:

General EBS presentations include:

And last but not least, don't miss the chance to hear about EBS Release 12.2 online patching feature from one of its architects:

You'll also be well placed to attend the TECH16 track, where you can learn about the latest developments in Oracle Database and other technologies.

We look forward to seeing you at APPS16!

References

Related Articles


Monday Nov 28, 2016

Will EBS Work with Microsoft Unified Update Platform?

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

The new UUP delivery method will provide only the Windows 10 patches that have been released since the last time a desktop was updated.  Microsoft currently expects to switch to this new delivery method after the Windows 10 Creators Update is released in early 2017.

Will this work with EBS?

Yes.  Windows 10 is certified with all current EBS releases, including EBS 12.1 and 12.2.  This new delivery method is not expected to change that.

Microsoft emphasizes that nothing changes with Windows 10 itself -- this only modifies the way that Win10 patches are delivered:

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

Related Articles

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

Friday Nov 18, 2016

Reminder: Upgrade to EM 12.1.0.5

Oracle periodically produces Fusion Middleware patchsets -- cumulative collections of fixes -- between major product releases.  All Oracle customers have a limited amount of time 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. 

What is the impact on EBS customers using Application Management Pack?

Enterprise Manager 12.1.0.5 was released in June 2015.  Oracle continued to create new patches for EM 12.1.0.4 until June 2016.  New patches for EM 12.1.0.4 are no longer available. New patches are being created only for EM 12.1.0.5.

EBS 12.1 and 12.2 customers who need new patches for their Enterprise Manager components must be on EM 12.1.0.5 and AMP 12.1.0.4 BP3, at minimum.  No new patches for earlier versions of AMP will be available.

EBS customers should consider upgrading to Enterprise Manager 13c and AMP 13.1 or higher:

Related Articles


Thursday Nov 17, 2016

Oracle Enterprise Manager 12.1 Support Dates Changed

Two important changes have been made to Oracle Enterprise Manager 12.1 Lifetime Support dates:

  1. Extended Support fees have been waived for the first year up to October 31, 2017
  2. Extended Support now ends on October 31, 2020 (one extra year of Extended Support)

These changes are published here:

Impact on EBS customers

These support changes apply to E-Business Suite customers using Application Management Pack released as part of Oracle Application Management Suite for Oracle E-Business Suite. 

EBS customers should consider upgrading to Enterprise Manager 13c and AMP 13.1 or higher:

Wednesday Nov 16, 2016

E-Business Suite Technology Codelevel Checker Updated for EBS 12.2

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

What's New

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

  • October 2016 WebLogic Server (WLS) Patch Set Update (PSU)
  • October 2016 Database Patch Set Update and Bundle Patch
  • July 2016 Database Patch Set Update and Bundle Patch
  • July 2016 Database Cloud Service (DBCS) / Exadata Cloud Service (ExaCS) service

Obtaining ETCC

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

Related Articles

References

Tuesday Nov 15, 2016

DSTv28 Timezone Patches Available for E-Business Suite 12.1 and 12.2

Hourglass iconIf your E-Business Suite Release environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in October 2016 and released as DSTv27.

DSTv28 is now available and certified with Oracle E-Business Suite Release 12.1 and 12.2. This update includes the timezone information from the IANA tzdata 2016g.  It is cumulative: it includes all previous Oracle DST updates. 

Is Your Apps Environment Affected?

When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

  • Your Oracle E-Business Suite environment is located in the affected country or region OR
  • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

The latest DSTv28 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv27 includes changes to the following timezones since the DSTv24 release:

  • Asia/Rangoon
  • Asia/Istanbul
  • Europe/Istanbul
  • Turkey

What Patches Are Required?

In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

Proactive backports of DST upgrade patches to all Oracle E-Business Suite tiers and platforms are not created and supplied by default. If you need this DST release and an appropriate patch is not currently available, raise a service request through support providing a business case with your version requirements.

The following Note identifies the various components in your E-Business Suite environment that may need DST patches:

What is the business impact of not applying these patches?

Timezone patches update the database and other libraries that manage time. They ensure that those libraries contain the correct dates and times for the changeover between Daylight Savings Time and non-Daylight Savings Time.

Time is used to record events, particularly financial transactions.  Time is also used to synchronize transactions between different systems.  Some organizations’ business transactions are more-sensitive to timezone changes than others. 

If you do not apply a timezone patch, and do business with a region that has changed their timezone definitions, and record a transaction that occurs at the boundary between the “old” and the “new” time, then the transaction may be recorded incorrectly. That transaction's timestamp may be off by an hour. 

For example:

  • An order is placed for a customer in a country which changed their DST dates in DST v27
  • The old Daylight Savings Time expiration date was Nov. 2
  • The new Daylight Savings Time expiration date is now October 31
  • An order is set to ship at 12am on November 1st
  • Under the old Daylight Savings Time rules, the revenue would be recorded for November
  • Under the new Daylight Savings Time rules, the revenue would be recorded for October

Related 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. I'll post updates here as soon as soon as they're available.   


Monday Nov 14, 2016

Application Management Pack 13.1.1.1 Certified with Enterprise Manager 13.2

In July 2016, we announced the general availability of Oracle Application Management Suite 13.1.1.1 for Oracle E-Business Suite as a plug-in for Enterprise Manager Cloud Control 13c. Application Management Suite 13.1.1.1 is now certified as a plug-in with Oracle Enterprise Manager Cloud Control 13c Release 2.

EM 13cR2 compatibility

We encourage all customers to upgrade to the latest release of Oracle Enterprise Manager 13.2 and Oracle Application Management Pack 13.1.1.1. If you are planning to manage Oracle E-Business Suite cloud environments, you must be on Oracle Enterprise Manager 13c and Oracle Application Management Pack Release 13.1.1.1.0 with latest patches listed in the Note below.

References

For release details and product documentation links, see:

Downloading this update

Oracle Application Management Suite for Oracle E-Business Suite can be downloaded and installed by:

Related Article


Tuesday Nov 08, 2016

Troubleshooting Cloning Issues in EBS 12.1

The Rapid Clone tool is used to create a working identical copy of an existing Oracle E-Business Suite 12.1 environment.  There are several ways of using Rapid Clone, including cloning a single node environment to another single node environment, adding additional nodes to an existing environment, and reducing nodes when cloning a multinode environment to a single node clone. 

Cloning EBS 12.1.3

The guide to using Rapid Clone in EBS 12.1 environments is:

When things go wrong

Given the variety of ways that this tool can be used, it is inevitable that some things might not go as expected.  When that happens, it's helpful to have a troubleshooting framework to narrow down the possible root causes and identify a solution. 

If you've encountered a problem with Rapid Clone, your first stop should be:

This excellent Note covers the most-common questions and issues associated with Rapid Clone, such as:

  • Location of cloning log files
  • Missing prerequisite patches
  • Preparing the source system's database and application tiers
  • The expected layout of the cloning stage area for both the applications and database tiers
  • Execution of the cloning process
  • Inventory registration issues
  • Common issues when cloning the database tier
  • Known issues

Related Articles


Monday Nov 07, 2016

New OA Framework 12.2.4 Update 13 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 updates to Oracle Application Framework to fix performance, security, and stability issues. 

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

The latest OAF update for EBS 12.2.4 is now available:


Where is the documentation for this update?

Instructions for installing this OAF Release Update Pack are here:

Who should apply this patch?

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

What's new in this update?

Fixes are included for following critical issues:

    • When Descriptive Flexfield (DFF) is rendered in an advanced table, some of its segments may not be displayed, and instead other columns of the table get repeated.
    • Unable to attach the Font message choice drop-downs such as Font, Color and Size to Message Rich Text Editor (MRTE).

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

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

    Related Articles


    Friday Nov 04, 2016

    Achieving Optimal Performance with Oracle E-Business Suite

    Our Applications Performance Group ensures that the E-Business Suite runs at peak performance in all circumstances.  This team has helped tune the E-Business Suite environments of world's largest companies to handle staggering amounts of transactional volume in multi-terabyte databases.  This group also publishes our official Oracle Apps benchmarks, white papers, and performance metrics.

    This team has collected the latest tips for optimizing EBS performance here:

    This presentation covers the following areas:

    • Optimizing Applications Tier
    • Optimizing Database Tier
    • Optimizing EBS on Real Application Clusters (RAC)
    • Optimizing EBS on Engineered Systems (e.g. Exadata)
    • Optimizing EBS using Database In-Memory
    • Optimizing EBS data management 

    Concurrent Manager Workload settings

    This is a concrete and practical collection of tips that are useful for all ranges of EBS environments.  Some specific topics covered include:

    • Using optimal FND Debug logging settings for the Apps tier
    • Optimizing Workflow processes through purging and deferred activities
    • Sizing guidelines for middle tier concurrency for JVMs, Forms
    • Dealing with network latency and bandwidth constraints
    • Tuning init.ora parameters, including SGA and PGA memory sizing
    • Best practices for gathering applications statistics
    • Archiving and purging tips
    • ... and much more...

    Related Articles


    Thursday Nov 03, 2016

    Will Windows Monthly Rollups Work with EBS?

    Microsoft logoMicrosoft announced that they will release security and reliability patches in a single Monthly Rollup update instead of as individual patches.  They also announced the availability of a single Security-only rollup. 

    This change was effective from October 2016 onwards and applies to:

    • Windows 7 Service Pack 1 (SP1)
    • Windows 8.1
    • Windows Server 2008 R2
    • windows Server 2012
    • Windows Server 2012 R2

    Compatibility with Oracle E-Business Suite

    Microsoft Monthly Rollups and Security-only updates are intended to be backwards-compatible with all applications. Existing Windows functionality does not change.

    It is expected that these updates will be fully-compatible with Oracle E-Business Suite 12.1 and 12.2.  We expect that we will do periodic testing of selected updates, but will do not expect to release regular certification announcements for them. 

    EBS customers do not have to wait for explicit certification announcements before applying Microsoft Monthly Updates or Security-only updates to their Windows desktops or servers.

    Related Articles



    Wednesday Nov 02, 2016

    Is Oracle E-Business Suite FIPS 140 Certified?

    Customers frequently ask whether Oracle E-Business Suite is certified with the FIPS standards. 

    The Federal Information Processing Standards (FIPS) Publication 140-2 defines US Federal standards for cryptographic-based security systems.  FIPS Publications are issues by the National Institute of Standards and Technology (NIST).

    From our Oracle E-Business Suite Security FAQ (Note 2063486.1)

    The cryptographic modules in Oracle E-Business Suite currently cannot be considered FIPS certified. Some elements of the Oracle E-Business Suite Release 12.1.3 technology stack have been FIPS certified; however, some of the cryptographic libraries that are used by Oracle E-Business Suite have not been FIPS certified. Additionally, some of the cryptographic libraries that have been FIPS certified have had patches issued since certification, which technically takes them out of compliance.

    Specifically, the cryptographic libraries that Oracle HTTP Server (OHS) uses for SSL/TLS traffic were FIPS certified. However, there have been a variety of security and non-security related patches in that area that technically take it out of compliance, and it has not been recertified since those patches have been issued. Oracle E-Business Suite also makes use of other cryptographic libraries for variety of usages that have not been FIPS certified.  Oracle does not currently plan to certify all of the cryptographic libraries currently used by Oracle E-Business Suite.


    Tuesday Nov 01, 2016

    Which Oracle Database Patchsets Can Be Used With EBS?

    Oracle versions numbers can be very long.  Complicating matters further, different product families within Oracle use the version hierarchy differently.  This can make it confusing to determine whether a specific product update has been certified with Oracle E-Business Suite.

    Oracle Database update numbers can be daunting.  However, it might be reassuring to learn that the fifth-level digit in Oracle Database version is not relevant to E-Business Suite certifications.  In other words, you can apply any database patchsets that have been certified at the fourth-level digit. 

    For example, we have certified EBS 12.2 with Database 12.1.0.2. All of the following Oracle Database patchsets will work with EBS 12.2:

    • Oracle Database 12.1.0.2.0 (documented certification)
    • Oracle Database 12.1.0.2.160419 (April 2016 Database Proactive Bundle Patch)
    • Oracle Database 12.1.0.2.160719 (July 2016 Database Proactive Bundle Patch)

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

    • Oracle Database 12.1.0.2
    • Oracle Database 12.1.0.2.x

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

    Related Articles

    Monday Oct 31, 2016

    Upgrading to EBS 12.2 With a Non-APPS Schema

    An Oracle database stores the objects associated with a single installation of Oracle E-Business Suite. Product code objects are stored in the APPS schema; product data objects are stored in the relevant base product schemas. Product code objects include packages, procedures, functions, triggers, views, materialized views, java classes, and queues.

    EBS APPS schema

    What does the APPS schema do?

    The APPS schema has access to the complete Oracle E-Business Suite data model. Oracle E-Business Suite responsibilities connect to an APPS schema, and the environment variable FNDNAM is set to the name of the APPS schema. The APPS schema owns all the code objects for the Oracle E-Business Suite, and has access to all data objects. There is one APPS schema for every product installation group.

    Utilizing a single schema that has access to all objects avoids cross-product dependencies, and creates a hub-and-spoke access model rather than the spider web model that would otherwise be needed. The APPS schema also improves the reliability of and reduces the time needed for installation, upgrading, and patching, by eliminating the need for cross-product grants and synonyms.

    It wasn't always "APPS"

    Older versions of EBS were delivered with a different default schema name: APPS_FND.  Some older versions even allowed you to override the default name of the schema prior to installation.

    Recent versions of Oracle E-Business Suite use the APPS schema by default.  It is not possible to change the name of the APPS schema.

    Hardcoded references to APPS are not permitted

    We have many upgrade-related scripts, tools, and utilities.  All of these standard EBS tools are required to handle any EBS schema name, regardless of whether it is named APPS, APPS_FND, or something else.  There should be no hardcoded references to, say, the APPS schema. This development standard is enforced by regular automated scans of the entire EBS source code.

    Earlier versions of some EBS upgrade scripts may have had hardcoded references to APPS.  Running an upgrade to, say, EBS 12.2 against an EBS environment with an EBS schema named APPS_FND would fail in certain circumstances.  This is not expected behavior.  We would regard that as a bug that needs to be fixed immediately.

    All E-Business Suite scripts with hardcoded APPS schema references have since been superceded by later versions that can handle any EBS schema names.  To avoid issues with non-standard schema names, make sure that you're using the latest Rapid Install and AD/TXK utilities.  Click on the "Upgrade Recommendations" link in the sidebar of this site for pointers to the latest utilities.

    Known issues

    It is possible to integrate E-Business Suite environments with Oracle Identity Manager (OIM), which offers connectors that handle user provisioning.  Those OIM connection scripts still contain hardcoded references to the APPS schema (bug 24613821). 

    Getting support

    If you encounter any issues with non-standard EBS schema names, please log a formal Service Request with Oracle Support. You are welcome to drop me a line or post a comment here, too, if your schema-related SR gets stuck in the pipeline for some reason.

    References

    Friday Oct 28, 2016

    Installing Developer 10g 32-bit on 64-bit Windows versions

    E-Business Suite 12.1 and 12.2 require Forms Developer 10g and Reports Designer 10g.  Forms Developer 10g and Reports Designer 10g are part of Oracle Developer Suite 10g.  Oracle Developer Suite 10g is a 32-bit program certified with Windows Vista, 7, 8.1, and 10.

    Forcing 32-bit programs to run on 64-bit Windows

    Although Windows 32-bit programs will not install by default on 64-bit versions of Windows, there are three possible workarounds:

    Workaround 1: You can run the Developer 10g setup.exe installer in Windows compatibility mode > Windows XP (Service Pack 2) or Windows XP (Service Pack 3).  See Section 6 in Note 277535.1.

    Workaround 2: You can let Windows determine how to install it automatically via the "Program Compatibility Assistant".  See Section 6 in Note 277535.1.

    Windows Program Compatibility Assistant

    Workaround 3: Install some additional patches and run the Developer 10g installer with the -ignoreSysPrereqs command line parameter.  See Note 1292919.1 for more details.

    Related Articles

    Thursday Oct 27, 2016

    New OA Framework 12.2.5 Update 7 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 for EBS 12.2.5 is now available:

    Screenshot EBS 12.2.5 OAF Bundle Patch 7

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

    What's new in this update?

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

    This latest bundle patch includes new fixes for the following critical issues:

    • The number values in Total column in the Budget table are partially hidden after applying some set of ATG and Mobile Application patches.
    • Failed to return to the base page after submitting the popup due to client side validation.
    • The rawtext with style class set to OraInstrcutionText under HideShowHeader with style class OraHeaderSub does not word-wrap.
    • Tables are not get rendered properly when scrolling when there are more than 300 records in the table.
    • Page/form image icons are not aligned on home page with the function name links in Navigator and Favorites regions in Chrome and Firefox browsers.
    • The document catalog column was displayed on inline attachment popup windows even if document catalog option was disabled.
    • In HTTPS-enabled environments, navigating to 3-Frame JSP page shows a blank page since the request to load mixed active content has been blocked.
    Related Articles

    Tuesday Oct 25, 2016

    Quarterly EBS Upgrade Recommendations: October 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 October 2016


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

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

    In Premier Support to September 30, 2023

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

    In Premier Support to December 31, 2021

    In Sustaining Support. No new patches available.

    Upgrade to 12.1.3 or 12.2

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

    In Sustaining Support. No new patches available.

    Upgrade to 12.1.3 or 12.2

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

    Apply the latest EBS suite-wide RPC or RUP

    12.2.6
    Sept. 2016

    12.1.3 RPC5
    Aug. 2016

    12.0.6

    11.5.10.2
    Use the latest Rapid Install

    StartCD 51
    Feb. 2016

    StartCD 13
    Aug. 2011

    12.0.6

    11.5.10.2

    Apply the latest EBS technology stack, tools, and libraries

    AD/TXK Delta 8
    Sept. 2016

    FND
    Aug. 2016

    EBS 12.2.5 OAF Update 6
    Sept. 2016

    EBS 12.2.4 OAF Update 11
    Jul. 2016

    FMW 11.1.1.9

    12.1.3 RPC5

    OAF Bundle 5
    Note 1931412.1
    Jun. 2016

    JTT Update 4
    Oct. 2016



    Apply the latest security updates

    Oct. 2016 Critical Patch Update

    SHA-2 PKI Certificates

    SHA-2 Update for Web ADI & Report Manager

    Migrate from SSL or TLS 1.0 to TLS 1.2

    Sign JAR files

    Oct. 2016 Critical Patch Update

    SHA-2 PKI Certificates

    SHA-2 Update for Web ADI & Report Manager

    Migrate from SSL or TLS 1.0 to TLS 1.2

    Sign JAR files

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

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

    Upgrade to IE 11

    Upgrade to Firefox ESR 45

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

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

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

    Upgrade to IE 11

    Upgrade to Firefox ESR 45

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

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



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

    Upgrade to Oracle Access Manager 11.1.2.3

    Upgrade to Oracle Internet Directory 11.1.1.9

    Migrate from Oracle SSO to OAM 11.1.2.3

    Upgrade to Oracle Internet Directory 11.1.1.9



    If you're using Oracle Discoverer
    Migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11.1.1.7. Migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11.1.1.7.

    If you're using Oracle Portal
    Migrate to Oracle WebCenter  11.1.1.9
    Migrate to Oracle WebCenter 11.1.1.9 or upgrade to Portal 11.1.1.6.



    Monday Oct 24, 2016

    New OA Framework 12.2.6 Update 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 for EBS 12.2.x is now available:

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

    I'm on an earlier EBS release.  Can I apply this patch?

    Yes. This patch can be applied to all EBS 12.2.3 to 12.2.5 environments that have AD/TXK Delta 8 and ATG Delta 6 installed.

    What's new in this update?

    This bundle patch is cumulative: it includes all fixes released in previous EBS 12.2.x OAF bundle patches.

    This latest bundle patch includes fixes for the following critical issues along with security :

    • Table scroll navigation issue when navigating to previous records
    • Javadoc for Layered Layout component
    • Reset icon in Personalization workbench not loading few times
    • UI distortion on the page after adding records in table in the last range
    • Worklist Font issue in Tree mode on Homepage
    • KFF combinations update event  was not getting processed for KFF inside table
    • Profile option name for profile FND_SHOW_INSTANCE_NAME changed to FND: Show Instance Name

    Related Articles

    Friday Oct 21, 2016

    Reminder: EBS 12.2 Minimum Patching Baselines and Dates

    Oracle E-Business Suite 12.2 is now covered by Premier Support to September 30, 2023. This is documented here:

    Oracle Lifetime Support table for EBS

    Premier Support includes new EBS 12.2 patches for:

    • Individual product families (e.g. Oracle Financials)
    • Quarterly security updates released via the Critical Patch Update process
    • New technology stack certifications with server-based components
    • New certifications for end-user desktops and mobile devices

    What are the minimum patching baselines for EBS 12.2?

    The minimum patching baselines for EBS 12.2 have not changed.  New EBS 12.2 patches are created and tested against the minimum patching baseline documented in Section 4.1, "E-Business Suite 12.2 Minimum Prerequisites" in this document:

    All EBS 12.2 customers must apply the minimum patch prerequisites to be eligible for Premier Support. Those patches include the suite-wide EBS 12.2.3 Release Update Pack and a small number of technology stack infrastructure updates.

    Instead of applying the minimum baseline

    Many new updates have been released since that patching baseline was originally published.  These new patches contain stability, performance, and security-related updates and are strongly recommended for all customers. 

    If you haven't applied any of those updates yet, the simplest solution would be to apply the latest suite-wide EBS 12.2.6 Release Update Pack (RUP).  That way, you get all of the 12.2 minimum patching requirements and the latest updates simultaneously.

    If you've reached this blog article via a search engine, it is possible that a new Release Update Pack has been released since this article was first published.  Click on the "Certifications" link in the sidebar for a pointer to the latest EBS 12.2 RUP.

    Related Articles

    Thursday Oct 20, 2016

    EBS 12.2.6 OA Extensions for Jdeveloper 10g Now Available

    Jdeveloper logoWhen you create extensions to Oracle E-Business Suite OA Framework pages, you must use the version of Oracle JDeveloper shipped by the Oracle E-Business Suite product team. 

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

    The Oracle Applications (OA) Extensions for JDeveloper 10g are now available for E-Business Suite Release 12.2.6.  For details, see:

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

    Related Articles

    Wednesday Oct 19, 2016

    JRE 1.8.0_111/112 Certified with Oracle EBS 12.1 and 12.2

    Java logo

    Java Runtime Environment 1.8.0_111 (a.k.a. JRE 8u111-b14) and its corresponding Patch Set Update (PSU) JRE 1.8.0_112 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_111
    • PSU Release:  JRE 1.8.0_112
    Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_111) and only upgrade to the PSU release (1.8.0_112) 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), 10.10 (Yosemite), and 10.11 (El Capitan) desktops.  For details, see:

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

    No.

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

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

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

    Known Iusses

    Internet Explorer Performance Issue

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

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

    Form Focus Issue

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

    References

    Related Articles

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

    Java logo

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

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

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

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

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

    32-bit and 64-bit versions certified

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

    Where are the official patch requirements documented?

    EBS + Discoverer 11g Users

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

    JRE 7 End of Public Updates

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

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

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

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

    Coexistence of multiple JRE releases Windows desktops

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

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

    Java Auto-Update Mechanism

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

    Coexistence of multiple JRE releases Windows desktops

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

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

    What do Mac users need?

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

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

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

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

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

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

    Known Issues

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

    References

    Related Articles

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

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

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

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

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

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

    Effects of new support dates on Java upgrades for EBS environments

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

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

    New EBS installation scripts

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

    32-bit and 64-bit versions certified

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

    Implications of Java 6 End of Public Updates for EBS Users

    The Support Roadmap for Oracle Java is published here:

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

    Java SE 6 End of Public Updates Notice

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

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

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

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

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

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

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

    Coexistence of multiple JRE releases Windows desktops

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

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

    What do Mac users need?

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

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

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

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

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

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

    References

    Related Articles

    Tuesday Oct 18, 2016

    Critical Patch Update for October 2016 Now Available

    The Critical Patch Update (CPU) for October 2016 was released on October 18, 2016. Oracle strongly recommends applying the patches as soon as possible.

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

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

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

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

    The next four Critical Patch Update release dates are:

    • January 17, 2017
    • April 18, 2017
    • July 18, 2017
    • October 17, 2017

    References

    Related Articles

    About

    Search

    Categories
    • Oracle
    Archives
    « December 2016
    SunMonTueWedThuFriSat
        
    3
    4
    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