Friday Aug 09, 2013

Internet Explorer 10 Certified with Oracle E-Business Suite

MS IE logoMicrosoft Internet Explorer 10 is now certified as a desktop client browser for Oracle E-Business Suite Release 11i, 12.0, and 12.1.  The certified desktop operating systems are:

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

EBS 12.1 Prerequisites

  • EBS 12.1.1 or higher
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher

EBS 12.0 Prerequisites

  • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or higher.
  • Oracle Forms Version 10.1.2.3 or higher.
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher

EBS 11i Prerequisites

  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or higher
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or higher.
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) (see Note 125767.1)
  • MLR patch 8888184 or higher (see note 125767.1 for the latest release)
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher

Compatibility Mode for IE 10 + EBS 12

To prevent issues with certain OA Framework pages, you should run IE 10 in "Compatibility Mode." See the "Known Issues" section in Note 389422.1 for more details.

JRE 1.7 is 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 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 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 1.6 or JRE 7 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


Tuesday Aug 06, 2013

You're Closer to EBS 12.1.3 Than You Think

Congratulations -- you're running EBS 12.1.1 or 12.1.2 in production.  Our standing recommendation is to apply the EBS 12.1.3 suite-wide Release Update Pack (RUP), despite the relaxed requirements in the recent changes to our Error Correction Support Policy.

If you can't apply the suite-wide 12.1.3 Release Update Pack, you should apply the individual 12.1.3 Family Packs for the EBS products that you've deployed.

Here's our best-kept secret:  this will change your environment less than you think.  If you've applied any patches to your 12.1.1 or 12.1.2 environment, you probably already have much of 12.1.3 already in production today.  

A glimpse behind the curtain

This is due to the way that our EBS source code control system works: we deliver patches based upon the latest versions of code in our source control system.  Developers sometimes refer to this as "delivering code on the tip of the codeline."

If "source control systems" are unknown territory to you, here's an example to illustrate this:

Let's imagine that you're running 12.1.1 and report an issue with a Financials screen. 

That Financials screen was first released in 12.1.1, updated in 12.1.2, and updated again in 12.1.3.

Whatever patch you apply will deliver the latest version of the 12.1.3 code and all of the related dependencies in other screens or packages

In this particular case, you might think you're on 12.1.1, but applying that patch has raised your code level for the updated files to the 12.1.3 level or even later.

Apps DBA Tip: Check which files a patch changes

Here's how to check this out yourself.  The Oracle Applications Manager contains a tool that all Apps DBAs should use:

The Patch Wizard has an "Analyze Specific Patches" function that tells you how a specific patch will affect your system.

Patch Wizard Analyse Specific Patches screenshot

The resulting "Patch Impact Analysis" report provides you with a summary of:

  • Applications patched
  • New files introduced
  • Existing files changed
  • Existing files unchanged

Screenshot of Patch Wizard Impact Analysis Report

Power users tip:  identify affected customizations

Patch Wizard Register Flagged Files screenshotIf you've flagged your customized files using the Oracle Applications Manager "Register Flagged Files" function, the Patch Wizard will also identify which of your customizations are affected by a given patch.

This allows you to reassure your developers and end-users that you have very-granular control over the impact of a given patch on critical customized functionality.

A case study: Financials and Procurement 12.1.3 vs. 12.1.1

A major steel manufacturer running EBS 12.1.1 approached us with their concerns about applying the suite-wide EBS 12.1.3 Release Update Pack to their environment.  Like many manufacturers, every hour of EBS downtime meant lost productivity so they wanted to minimize the amount of retesting triggered by 12.1.3.

They had been running 12.1.1 Financials and Procurement in production for quite some time.  They had stabilized their environment with a number of one-off patches on top of 12.1.1.  

We used the Patch Wizard's "Patch Impact Analysis" report to assess the number of files that would be affected by the 12.1.3 Family Packs for Financials and Procurement.  Here's what we found:

  • They already had applied 81% of the 12.1.3 Procurement Family Pack.  The 12.1.3 Procurement Family Pack has ~3,800 files, which means that over 3,100 files were unchanged.  Only 3 of the files that they'd customized needed review.

  • The 12.1.3 Financials Family Pack contains ~12,000 files.  They had already applied 72% of the 12.1.3 Financials Family Pack, leaving over 8,600 files unchanged.  Only one of their customized files needed review.

Do your own 12.1.3 impact analysis

Your mileage will vary.  Run the Patch Wizard comparing the 12.1.3 Family Packs to see how close you are.

I'd be interested in hearing your reports.  Feel free to post a comment here or drop me an email with your results.

References

Related Articles


Thursday Aug 01, 2013

New Source Database Added for EBS 12 + 11gR2 Transportable Tablespaces

The Transportable Tablespaces (TTS) process was originally certified for the migration of E-Business Suite R12 databases going from a source database of 11gR1 or 11gR2 to a target of 11gR2.

This requirement has now been expanded to include a source database of 10gR2 (10.2.0.5) - this will potentially save time for existing 10gR2 customers as they can remove on a crucial upgrade step prior to performing the platform migration.

Transportable Tablespaces supported options

The migration process requires an updated Controlled patch delivered by the Oracle E-Business Suite Platform Engineering team, i.e. it requires a password obtainable from Oracle Support. We released the patch in this manner to gauge uptake, and help identify and monitor any customer issues due to the nature of this technology. This patch has been updated to now include supporting 10gR2 as a source database.

Does it meet your requirements?

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

SQL>select platform_name from v$db_transportable_platform;

If the intended target platform does not appear in the output, it means that it is of a different endian format from the source. Consequently. database migration will need to be performed via Transportable Tablespaces (for large databases) or export/import.

The use of Transportable Tablespaces can greatly speed up the migration of the data portion of the database. However, it does not affect metadata, which must still be migrated using export/import. We recommend that users initially perform a test migration on their database, using export/import with the 'metrics=y' parameter. This will help identify the relative amounts of data and metadata, and provide a basis for assessing likely gains in timing. In general, the larger the amount of data (compared to metadata), the greater the reduction in downtime that can be expected from using TTS as a migration process.

For smaller databases or for those that have relatively small data compared to metadata, TTS will not be as beneficial for cross endian migration and the use of export/import (datapump) for the whole database is recommended.

Where can I find more information?

Related Articles

Friday Jul 26, 2013

E-Business Suite Release 12.1.1 Consolidated Upgrade Patch 2 Now Available

Oracle E-Business Suite Release 12.1.1 Consolidated Upgrade Patch 2 (CUP2) is now available in My Oracle Support. This patch includes fixes and performance improvements for the scripts used to upgrade an EBS 11i environment to 12.1.1.

This patch is mandatory for customers who are upgrading to Release 12.1.1 from the following releases:

  • Oracle E-Business Suite Release 11i version 11.5.9 (base, CU1, CU2)
  • Oracle E-Business Suite Release 11i version 11.5.10 (base, CU1, CU2)

This patch includes all of the upgrade-related fixes released previously in the Consolidated Upgrade Patch 1 (CUP1, Patch 7303029) and many additional upgrade related fixes released since March 2010. 

You can download it here:



What is Oracle E-Business Suite Consolidated Upgrade Patch 2 for Release 12.1.1?

The Consolidated Upgrade Patch 2 (CUP2) for Release 12.1.1 combines critical upgrade error corrections and upgrade performance improvements from Release 11i into a consolidated suite-wide patch.

Who should use it?

Customers who are upgrading to Release 12.1.1 from Release 11.5.9 (base, CU1, CU2) or Release 11.5.10 (base, CU1, CU2) should apply Release 12.1.1 CUP2.

How does it differ from the Family Consolidated Upgrade Patch (FCUP) in Release 11i?

In Release 11i, Family Consolidated Upgrade Patches (FCUP) were the release vehicles used to ship consolidated upgrade-related patches from all products within a product family.  In R12, the term Consolidated Upgrade Patch (CUP) has been coined to ship critical upgrade error corrections and upgrade performance improvements across all the product families in Oracle E-Business suite.

How do you apply Release 12.1.1 CUP2?

For instructions on applying this patch, see the "Notes for Upgrade Customers" section in:
Can this patch be applied by customers who are upgrading to Release 12.1.1 from an earlier version of Release 12?

No.  Release 12.1.1 CUP2 is applicable only if you are upgrading your E-Business Suite Release 11i instance to Release 12.1.1.  If your Oracle E-Business Suite instance is already at Release 12 or higher (e.g. Release 12.0.4, 12.0.6), you should not apply Release 12.1.1 CUP2.

Can I apply Release 12.1.1 CUP2 to Release 12.1.1?

No.  If your environment is already at the Release 12.1.1 level, you do not need this patchset.  You should apply Release 12.1.1 CUP2 only while upgrading a Release 11i Oracle E-Business Suite instance to Release 12.1.1

Is Release 12.1.1 CUP2 mandatory for upgrading to Release 12.1.1 if I have done multiple test upgrades and am close to "Go-Live"?

If you have already performed multiple test upgrades without Release 12.1.1 CUP2 and are close to completing User Acceptance Testing prior to your actual production upgrade, it is not mandatory to apply the patch.

Oracle will continue to provide patches for Oracle E-Business Suite Release 12.1.1 environments that do not have the Release 12.1.1 CUP2 patchset.

How is the Consolidated Upgrade Patch (CUP) different from other release vehicles?

With the introduction of this patchset, there are now five types of release vehicles for the E-Business Suite:
  1. Rapid Install
  2. Maintenance Pack
  3. Product Family Release Update Pack
  4. E-Business Suite Release Update Pack
  5. Consolidated Upgrade Patch
Rapid Install

With Rapid Install (RI), you can install a fully configured Oracle E-Business suite system, lay down the file system and configure server processes for an upgraded system, or install a new database tier or application tier technology stack.

Release 12 Rapid Install versions are
  • Release 12.0.0
  • Release 12.0.4
  • Release 12.1.1
Maintenance Pack

A Maintenance Pack (MP) is an aggregation of patches for all products in Oracle E-Business Suite. It is a feature-rich release which combines new functionalities along with error corrections, statutory/regulatory updates, and functionality enhancements, etc.

The Release 12.1.1 Maintenance Pack can be used to upgrade an existing Oracle E-Business Suite Release 12.0.x environment to Release 12.1.1

Product Family Release Update Pack

Product Family Release Update Pack (RUP) is an aggregation of patches on a given codeline created for all products in a specific product family for a specific point release. RUPs are generally cumulative in nature.

Examples of Product Family Release Update Packs released in Release 12.0:
  • R12.ATG_PF.A.Delta.4
  • R12.FIN_PF.A.Delta.5
  • R12.ATG_PF.A.Delta.6
  • R12.HR_PF.A.Delta.7
Examples of Product Family Release Update Packs released in Release 12.1:
  • R12.AD_PF.B.Delta.2
  • R12.ATG_PF.B.Delta.2
  • R12.CC_PF.B.Delta.2
  • R12.SCM_PF.B.Delta.2
E-Business Suite Release Update Pack

An E-Business Suite Release Update Pack (RUP) is an aggregation of product or product family RUPs on a given codeline created across Oracle E-Business Suite after the initial release. Like product family Release Update Pack, E-Business suite Release Update Pack is cumulative in nature.

Examples of E-Business Suite Release Update Packs
  • Release 12.0.4
  • Release 12.0.6
  • Release 12.1.2
Consolidated Upgrade Patch

A Consolidated Upgrade Patch is a collection of critical fixes that improve the performance and stability of the upgrade process from Release 11i to Release 12.1.1.
References
Related Articles

Monday Jul 22, 2013

Quarterly E-Business Suite Upgrade Recommendations: July 2013 Edition

We've previously provided advice on the general priorities for applying EBS updates.  This article will help you understand your top priorities for major upgrades to EBS and its technology stack components.

The following is a summary of 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. 

Upgrade Recommendations for July 2013

  1. EBS 11i users should upgrade to 12.1.3, or -- if staying on 11i -- should be on the minimum 11i patching baseline,

  2. EBS 12.0 users should upgrade to 12.1.3, or -- if staying on 12.0 -- should be on the minimum 12.0 patching baseline,

  3. EBS 12.1 users should upgrade to 12.1.3.

  4. Oracle Database 10gR2 and 11gR1 users should upgrade to 11gR2 11.2.0.3.

  5. EBS 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.0 or OAM 11gR1 Patchset 2 11.1.1.7.

  6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 1 11.1.2.1.0 or Oracle Access Manager 10g 10.1.4.3.

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

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

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

  10. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_51 or later 1.6 updates , or JRE 1.7.0_25 or later 1.7 updates.

  11. All Firefox users should upgrade to Firefox Extended Support Release 17.

Related Articles

Friday Jul 19, 2013

Announcing Oracle E-Business Suite Extensions for Oracle Endeca 12.1.3.3

The Oracle E-Business Suite Extensions for Oracle Endeca provide selected EBS applications with Oracle Endeca-based capabilities. These extensions allow users to take an information-driven approach to business, optimizing operational decisions and improving process efficiency.

Each extension provides an existing EBS application with a search-oriented dashboard that summarizes current operational information. Users can explore this information in whatever way makes sense to them, combining free text and faceted search with drilldown on visualizations such as key performance indicators (KPIs), tag clouds, charts and cross-tabs. With each drilldown or search refinement, the entire set of visualizations and search choices changes to reflect the user’s previous choices. Users can browse and drill to the subset of information that is important for them to act on, automatically passing context to an EBS transaction screen where they can take the necessary action – for example, expediting a sales order by substituting a replacement part.

Endeca screenshot

The Oracle E-Business Suite Extensions for Oracle Endeca allow users to leverage modern, self-service discovery mechanisms for identifying and acting on exceptions and opportunities. Users can find information that that they otherwise might not find with conventional ERP query screens, reducing their reliance on emails, phone calls, and IT-provided reports.

What’s New in Oracle E-Business Suite Extensions for Oracle Endeca 12.1.3.3?
Oracle recently announced Oracle E-Business Suite Extensions for Oracle Endeca 12.1.3.3 for EBS 12.1.3 environments.  This release adds six new extensions:

  • Oracle Warehouse Management Extensions for Oracle Endeca
  • Oracle Installed Base Extensions for Oracle Endeca
  • Oracle Process Manufacturing Extensions for Oracle Endeca
  • Oracle Cost Management Extensions for Oracle Endeca
  • Oracle Depot Repair Extensions for Oracle Endeca
  • Oracle Learning Management Extensions for Oracle Endeca

In addition, 12.1.3.3 includes updates to nine previously-available extensions:

  • Oracle Order Management Extensions for Oracle Endeca
  • Oracle Discrete Manufacturing Extensions for Oracle Endeca
  • Oracle Inventory Management Extensions for Oracle Endeca
  • Oracle Channel Revenue Management Extensions for Oracle Endeca
  • Oracle Enterprise Asset Management Extensions for Oracle Endeca
  • Oracle Field Service Extensions for Oracle Endeca
  • Oracle Project Management Extensions for Oracle Endeca
  • Oracle iProcurement Extensions for Oracle Endeca
  • Oracle iRecruitment Extensions for Oracle Endeca  

Technical Overview of Oracle E-Business Suite Extensions for Oracle Endeca
Oracle E-Business Suite Extensions for Oracle Endeca use Oracle Endeca Information Discovery (EID) technology, which features:

  • A hybrid search-analytical engine
  • A user interface optimized for visual discovery and analysis
  • A data integration (ETL) engine

E-Business Suite transactional information is loaded and stored in a faceted, in-memory data model that gets refreshed with changes at intervals prescribed by the system administrator. Information is pre-classified, pre-summarized, and pre-sorted before it becomes available for search, discovery and analysis in a rich content container that is embedded within an EBS HTML page.  EBS handles session management so that Endeca content in the rich content container is consistent with EBS context and security.

EBS customers can add Endeca-based capabilities using an all-in-one installer, achieving out-of-the box security and integration with their Oracle E-Business Suite applications. We typically recommend that the EID components be run on any hardware or VM running 64-bit Oracle or Redhat Linux V5 or V6.

Downloads

You can download the Oracle E-Business Suite Extensions for Oracle Endeca Media Pack here:

References

Related Articles

Introducing Anne Carlson, Guest Author

I'm pleased to welcome Anne Carlson to this blog's panel of guest authors.  Anne has previously contributed articles on best practices for planning EBS 12 upgrades and an overview webcast of that material, too.

Anne is a Senior Director for Oracle E-Business Suite Product Strategy at Oracle, with a focus on product launch and adoption. Anne frequently writes and speaks about upgrade and implementation planning, sharing best practices and lessons learned from customers.

Previously, Anne led product management and information development for the Applications Technology Group at Oracle, responsible for communicating how the E-Business Suite leverages Oracle’s systems technologies.

Anne received a bachelor’s degree from Yale University and a master’s degree from MIT Sloan School of Management.

Thursday Jul 18, 2013

Oracle Access Manager 11gR2 11.1.2.1.0 Certified With E-Business Suite

I am happy to announce that Oracle Access Manager 11gR2  Patchset 1 (11.1.2.1.0) is now certified with E-Business Suite Releases 11i, 12.0 and 12.1.

Choosing the Right Architecture

If you are implementing single sign-on for the first time, or are an existing Oracle Access Manager user, you may integrate with Oracle Access Manager 11gR2 Patchset 1 using Oracle Access Manager WebGate and Oracle E-Business Suite AccessGate. If you are using Oracle Single Sign-On 10gR3 (10.1.4.3) you may migrate to Oracle Access Manager 11gR2 Patchset 1 with Oracle E-Business Suite Access Gate.

Our previously published blog article and support note provides an overview of single sign-on integration options and recommendations:

Platforms Certified

The Oracle E-Business Suite AccessGate Java application is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to the Oracle Fusion Middleware Release 11g (11.1.1.x) Certification Matrix for more details.

For information on operating systems supported by Oracle Access Manager 11gR2 and its components, refer to the Oracle Identity and Access Management 11g Release 2 (11.1.2.1.0) Certification Matrix.

Integration with Oracle Access Manager involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

References

    Related Articles

    (Article Contributor:  Allison Sparshott)

    Wednesday Jul 17, 2013

    Critical Patch Update for July 2013 Now Available

    The  Critical Patch Update (CPU) for July 2013 was released on July 16, 2013. 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:

    • October 15, 2013
    • January 14, 2014
    • April 15, 2014
    • July 15, 2014
    E-Business Suite Releases 11i and 12 Reference

    Wednesday Jul 10, 2013

    How to Define Table-Validated Lists of Values in Web ADI

    I am pleased to announce a new video tutorial on defining table-validated Lists of Values using the Oracle Web Application Desktop Integrator (Web ADI).  One of the common requirements for List of Values in a Web Application Desktop Integrator spreadsheet is to display user-friendly values in a desktop-based spreadsheet but upload a corresponding identifier or code to the E-Business Suite. You can learn how to do this in this new tutorial.

    Using the List of Values component with Web ADI

    Oracle Web Application Desktop Integrator supports Oracle E-Business Suite’s user interface components such as List of Values (LOV) in spreadsheets. In a Web Application Desktop Integrator spreadsheet, a List of Values can be displayed as a pop-list or as a standard Search and Select view. A table-validated List of Values is a type of List of Values that not only displays set of values from a table, but also ensures that the value uploaded to Web Application Desktop Integrator Interface is valid. 

    The Desktop Integration Framework allows you to create custom desktop integrators for Web Application Desktop Integrator in E-Business Suite Release 12. You can define table-validated List of Values components for data uploaded from spreadsheets to the Oracle E-Business Suite.


    What is in this tutorial?

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

    1. Prepare Database Objects
    2. Create Custom Integrator
    3. Define Table List of Values Component
    4. Associate Table List of Values Component to Interface Attribute
    5. Define Layout for Integrator
    6. Preview Integrator
    7. Verify uploaded data

    Your feedback is welcome

    This is our first video tutorial and we're very interested in feedback.  Please post a comment here or drop us an email directly with your thoughts.

    References

    Related Articles

    Tuesday Jul 09, 2013

    Latest DSTv20 Timezone Patches Available for E-Business Suite

    Hourglass iconIf your E-Business Suite Release 11i, 12.0, or 12.1 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 January 2013 and released as DSTv19.

    DSTv20 is now available and certified with Oracle E-Business Suite Release 11i, 12.0, and 12.1. The DSTv20 update includes the timezone information from Olson tzdata 2012j and 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 DSTv20 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv20 includes changes to the following timezones since the DSTv19 release:

    • Africa/Casablanca,
    • America/Port-au-Prince,
    • America/Santiago,
    • America/Asuncion,
    • Antarctica/Palmer,
    • Asia/Gaza,
    • Asia/Hebron,
    • Pacific/Easter,
    • Chile/Continental,
    • Chile/EasterIsland

    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.

    We've published the following Notes which identify the various components in your E-Business Suite environment that may need DST patches:


    Wednesday Jul 03, 2013

    Microsoft Ending Support for Windows XP and Office 2003 in April 2014

    Microsoft LogoMicrosoft is ending support for Windows XP and Office 2003 on April 8, 2014.  The official announcement is published here:

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

    What can EBS customers expect after April 2014?

    After Microsoft desupports WinXP and Office 2003 in April 2014:

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

    What should EBS customers do?

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

    Certifications for Windows 8 and Office 2013 are still underway; you can monitor this blog for updates on those pending certifications.  EBS customers should avoid deploying Win8 or Office 2013 to end-users who depend on the E-Business Suite until these certifications are announced.

    Related Articles

    Tuesday Jul 02, 2013

    Plans for Certifying Oracle Database 12c with E-Business Suite

    Oracle Database 12c Logo

    [Oct. 24, 2013 Update: Database 12.1.0.1 is certified with the E-Business Suite]

    The Oracle Database 12c is now officially released.  We're as excited about this new database release as you are. 

    In fact, we've been testing a wide variety of E-Business Suite releases and configurations with internal DB 12c betas for some time.  This testing is going well, but as usual, Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates

    You're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.   


    Monday Jul 01, 2013

    E-Business Suite R12 Certified on 2012 Hyper-V Windows Guests

    Microsoft LogoOracle E-Business Suite Release 12 (12.1) is now certified on Windows Server 2008 (32-bit) and Windows Server 2008 R2 running as guest operating systems within Window Server 2012 Hyper-V virtual machines.

    Hyper-V is a built-in feature of Microsoft Windows Server that allows for the creation and management of virtualized computing environments. With this certification, the E-Business Suite is now supported on the above Windows virtualized guest operating systems in a similar way to non-virtualized Windows.

    References

    Thursday Jun 20, 2013

    EBS Sessions at July 2013 OAUG Connection Point in Pittsburgh

    Members of our E-Business Suite Applications Technology Group will be at the OAUG Connection Point - AppsTech 2013 to be hosted in the Marriott City Center in  Pittsburgh, PA on July 30-31, 2013.

    Please drop by any of our sessions to hear the latest news and meet up with us.

    General Session

    13311 - Oracle E-Business Suite Technology: Latest Features and Roadmap
    Steven Chan, Sr. Director, Applications Technology Group, Oracle

    Tuesday, July 30, 08:30 am - 09:30 am
    Location: Grand Ballroom

    This Oracle development session provides a comprehensive overview of the product strategy for Oracle E-Business Suite technology, capabilities and associated business benefits of recent releases and a review of capabilities on the product roadmap. Come hear about the latest enhancements of the user interface; systems administration and configuration management tools; security-related updates; and tools and options for extending, customizing, and integrating Oracle E-Business Suite with other applications.

    Speaker Sessions

    13312 - Oracle E-Business Suite Technology Certification Primer and Roadmap
    Steven Chan, Sr. Director, Applications Technology Group, Oracle

    Tuesday, July 30, 01:15 pm - 02:15 pm
    Location: City Center B

    This Oracle development session summarizes the latest certifications, support dates, upgrade implications and roadmap for the Oracle E-Business Suite technology stack, including elements such as database releases and options, Java, Oracle Forms, Oracle Containers for J2EE, desktop operating systems, browsers, JRE releases, development and Web authoring tools, user authentication and management, business intelligence, Oracle Application Management Packs, security options, clouds, Oracle VM, and virtualization.

    13314 - Deployment and System Administration of  Oracle E-Business Suite 12.2
    Elke Phelps, Sr. Principal Product Manager, Applications Technology Group, Oracle

    Tuesday, July 30, 02:30 pm - 03:30 pm
    Location: Grand Ballroom

    This Oracle Development session covers the latest technology stack for Oracle E-Business Suite, including the use of Oracle WebLogic Server and Oracle Database 11g Release 2. Topics include an architectural overview of the latest updates, installation and upgrade options, new configuration options, and new tools for hot cloning and automated “lights-out” cloning. Come learn how online patching (based on the Oracle Database 11g Release 2 Edition-Based Redefinition feature) will reduce your database patching downtimes.


    13313 - Minimizing Oracle E-Business Suite Maintenance Downtimes
    Elke Phelps, Sr. Principal Product Manager, Applications Technology Group, Oracle

    Wednesday, July 31, 01:45 pm - 02:45 pm
    Location: City Center A

    This Oracle development session describes the best techniques sysadmins can use to minimize patching downtimes. It starts with an architectural-level review of Oracle E-Business Suite fundamentals and then moves to a practical view of the various tools and approaches for downtimes. Topics include merging patches and shortcuts, distributing workers across multiple servers, noninteractive mode, staged APPL_TOPs and more. An added bonus: get a glimpse on the upcoming Oracle E-Business Suite 12 online patching capabilities.


    13315 - Oracle E-Business Suite Upgrade Best Practices: Technical Insight
    Elke Phelps, Sr. Principal Product Manager, Applications Technology Group, Oracle

    Wednesday, July 31, 11:30 am - 12:30 pm
    Location: Grand Ballroom

    This session is ideal for organizations thinking about upgrading to Oracle E-Business Suite 12.1. It covers the fundamentals of upgrading to Release 12.1, including the technology stack components and supported upgrade paths. Hear from Oracle Development about the set of best practices for patching in general and executing the Release 12.1 technical upgrade, with special considerations for minimizing your downtime. Also get to know about relatively recent upgrade resources.

    13316 - Advanced Management of Oracle E-Business Suite with Oracle Enterprise Manager
    Vasu Rao, Sr. Principal Product Manager, Applications Technology Group, Oracle

    Wednesday, July 31, 09:00 am - 10:00 am
    Location: Salon 6

    Oracle Enterprise Manager is the only product on the market that is designed to monitor and manage all the different technologies that constitute Oracle E-Business Suite applications. Learn how to use Oracle Enterprise Manager to gain dramatic improvements in system visibility and diagnostic capability as well as administrator productivity. The purpose of this session is to highlight the key features and benefits of Oracle Enterprise Manager and Oracle Application Management Suite for Oracle E-Business Suite.


    Meet the Oracle E-Business Suite Tools and Technology Experts

    Don’t miss this Oracle Applications Meet the Experts session with experts who specialize in Oracle E-Business Suite technology. This is the place where attendees can have informal and semistructured but open one-on-one discussions with Strategy and Development regarding Oracle Applications strategy and your specific business and IT strategy. The experts will be available to discuss the value of the latest releases and share insights into the best path for your enterprise, so come ready with your questions.

    To participate, be sure to reserve your 30-minute slot by signing up after you pick up your registration materials. Meeting times will be available throughout both days. Don’t miss out on this great opportunity — sign up early, as space will be limited.

    • Steven Chan - Sr. Director, Oracle
    • Elke Phelps - Sr. Principal Product Manager, Applications Technology Group, Oracle
    • Vasu Rao - Sr. Principal Product Manager, Applications Technology Group, Oracle

    For complete listing of all speaker sessions and other activities, please visit the OAUG Connection Point - AppsTech Web Site.


    Wednesday Jun 19, 2013

    Java JRE 1.6.0_51 Certified with Oracle E-Business Suite

    [Jun. 20, 2013 Update: corrected link to Java 6 downloads via My Oracle Support]

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

    All JRE 6 and 7 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 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 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 1.6 or JRE 7 releases to your EBS users' desktops.

    What's new in Java 1.6.0_51?

    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:

    32-bit and 64-bit versions certified

    This certification includes both the 32-bit and 64-bit JRE versions.

    32-bit JREs are certified on:

    • Windows XP Service Pack 3 (SP3)
    • Windows Vista Service Pack 1 (SP1) and Service Pack 2 (SP2)
    • Windows 7 and Windows 7 Service Pack 1 (SP1)

    64-bit JREs are certified only on 64-bit versions of Windows 7 and Windows 7 Service Pack 1 (SP1).

    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 (emphasis added):

    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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

    1. EBS 11i Extended Support ends November 2013
    2. EBS 12.0 Extended Support ends January 2015
    3. EBS 12.1 Extended Support ends December 2018

    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:

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

    The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 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 7 will be invoked instead of JRE 6 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.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

    Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

    Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

    JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

    The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

    What do Mac users need?

    Mac users running Mac OS 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

    EBS 12 certified with Mac OS X 10.7 and 10.8 with Safari 6 and JRE 7

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

    No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

    Java (JDK) 7 Certified for E-Business Suite 12 Servers

    References

    Related Articles

    Java JRE 1.7.0_25 Certified with Oracle E-Business Suite

    Java logoJava Runtime Environment 7u25 (a.k.a. JRE 7u25-b16) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12 for Windows-based desktop clients.

    All JRE 6 and 7 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 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 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 1.6 or JRE 7 releases to your EBS users' desktops.

    What's needed to enable EBS environments for JRE 7?

    EBS customers should ensure that they are running JRE 7u17, at minimum, on Windows desktop clients.

    Of the compatibility issues identified with JRE 7, the most critical is an issue that prevents E-Business Suite Forms-based products from launching on Windows desktops that are running JRE 7. 

    Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers. 

    These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite.  These patches may be applied immediately to all E-Business Suite environments. All other Forms prerequisites documented in the Notes above should also be applied. 

    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

    Prerequisites for 32-bit and 64-bit JRE certifications

    JRE 1.70_25 32-bit + EBS 11.5.10.2

    JRE 1.70_25 32-bit + EBS 12.0 & 12.1

    JRE 1.7.0_25 64-bit + EBS 11.5.10.2

    JRE 1.70_25 64-bit + EBS 12.0 & 12.1

    EBS + Discoverer 11g Users

    JRE 1.7.0_25 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.

    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 (emphasis added):

    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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

    1. EBS 11i Extended Support ends November 2013
    2. EBS 12.0 Extended Support ends January 2015
    3. EBS 12.1 Extended Support ends December 2018

    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:

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

    No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

    The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 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 7 will be invoked instead of JRE 6 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.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

    Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

    Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

    JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

    The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

    What do Mac users need?

    Mac users running Mac OS 10.7 or 10.8 can run JRE 7 plug-ins.  See this article:

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

    No. This upgrade is recommended but optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

    References

    Related Articles

    Thursday Jun 13, 2013

    Important Changes to E-Business Suite Error Correction Support Policy

    Oracle provides bug fixes and legislative updates for Oracle E-Business Suite as part of its Premier and Extended Support offerings.  The requirements and methods for delivering those updates are explained here:

    We've made some important changes to our policies.  All EBS customers should read Version 4 carefully.

    Why did we make these changes?

    Version 3 was published in 2011.  That version stated that new EBS 12.1 one-off patches would require all customers to have applied the suite-wide EBS 12.1.3 Release Update Pack by January 2013.

    A significant number of customers have told us that they have not been able to apply EBS 12.1.3 in time.  These customers have expressed concerns that 12.1.1 or 12.1.2 "were being desupported" and that they would not be able to request new updates.

    What is our standard guidance?

    Oracle recommends that all customers apply the latest suite-wide Release Update Pack. There are significant benefits to keeping your E-Business Suite environment updated with the latest suite-wide Release Update Packs:

    • They are cumulative, reducing the overhead of identifying many individual patchsets
    • They deliver the latest new features and enhancement requests
    • They include the latest updates for performance, stability, and security
    • They reduce the number of prerequisites required for other patches or new technology integrations

    What has changed?

    The 2011 version stated that all new one-off patches would require the suite-wide EBS 12.1.3 Release Update Pack as a minimum prerequisite.

    The 2013 version relaxes the prerequisites for new one-off patches.  New one-off patches will be produced with the individual 12.1.3 Family Packs as minimum prerequisites. This is so that vast majority of customers, who are at the 12.1.3 level, can get simpler and smaller patches. 

    How will this work?

    For example, you request a new one-off patch for an Oracle Financials issue that you've encountered with EBS 12.1.2:

    • Under the 2011 policy, the new Financial patch's prerequisite would be the EBS 12.1.3 suite wide Release Update Pack.
    • Under the 2013 policy, the new Financial patch's prerequisite is the Financials 12.1.3 Family Pack.
    Are EBS 12.1.1 or 12.1.2 desupported?

    You are not desupported if you are on 12.1.1 or 12.1.2.  The question incorrectly assumes that 12.1.1 or 12.1.2 are "releases" covered by our Premier or Extended Support offerings.

    An EBS environment consists of a base release and subsequent updates.

    Base releases are used to create new E-Business Suite environments or upgrade environments running older EBS releases.  Base releases are documented in Oracle Lifetime Support Policy: Oracle Applications and are eligible for Premier, Extended, and Sustaining Support.

    EBS 12 Base release support dates

    Examples of base releases:

    • E-Business Suite Release 12.0
    • E-Business Suite Release 12.1

    You get updates to base releases through:

    • Release Update Packs (RUPs)
    • One-off patches
    • Critical patch updates (CPUs)
    Here's the same question, restated:
    • Q: "How do I get updates for the EBS 12.1 base release?" 
    • A: By applying the latest Release Update Pack.  If the fix that you need is not already included in the latest Release Update Pack, you may request a new one-off patch.  New one-off patches will require their respective 12.1.3 Family Packs as a minimum prerequisite.

    What if you haven't applied the relaxed minimum prerequisites?

    Oracle will first recommend that you apply the appropriate 12.1.3 Family Packs. In cases of urgent business need, Oracle will evaluate the feasibility of creating one-off patches without the established minimum prerequisites. Whether this is practical will vary depending upon the complexity of the dependencies.  If the patch is in an area of code that has undergone little revision with few dependencies, it may be straightforward to produce one-off patches without the established minimum prerequisites. 

    In most cases involving complex code objects, such as the major transaction screens, it is likely that a full dependency analysis will show that a major portion of the established minimum prerequisites levels are, in fact, required to apply the patch.  In these cases, Oracle will recommend that customers minimize their risk by installing the established minimum prerequisites rather than a one-off dependency tree that is nearly as extensive but has not undergone the same level of testing.

    You are closer to 12.1.3 than you realize

    Our patching minimum prerequisite have been relaxed.  We still recommend that all customers apply the EBS 12.1.3 suite-wide Release Update Pack.  If you can't apply the EBS 12.1.3 suite-wide Release Update Pack, you should still apply the 12.1.3 Family Packs for the EBS products that you're using.

    You are probably a lot closer to 12.1.3 in most areas than you may realize.  Any patches that were created since you went live almost certainly delivered code above the 12.1.3 version level.  So, in areas where you had any patching or tuning as you stabilized on 12.1, it's pretty likely that any further patching would not require the 12.1.3 Family Pack.  To understand this in more detail, you can run "Patch Wizard" to do an analysis of what files on your system would really change if you applied each 12.1.3 Family Pack.  

    What are the impacts of these changes for 12.0 customers?

    The patching prerequisites for EBS 12.0 are not affected by these policy changes.  EBS 12.0 customers must have the minimum prerequisites

    Your feedback is welcome

    We've relaxed these policies to simplify your EBS maintenance requirements.  Please feel free to let us know if you have any comments or questions about these updated policies. 

    Monday Jun 10, 2013

    Java (JDK) 7 Certified for E-Business Suite 12.0 and 12.1 Servers

    Java logoWindows and Mac-based desktop clients connecting to the E-Business Suite can use the Java Runtime Environment (JRE) plug-in to run Forms-based components.  JRE 7 was certified with EBS 11.5.10.2, 12.0, and 12.1 in 2012.  As of today, the latest available version is JRE 1.7.0_21 for Windows clients and for Mac clients.  All new JRE releases on the 1.6 and 1.7 codelines are automatically certified with EBS on the day of their release.  If you're reaching this article via a search engine, please check My Oracle Support or the Certifications summary for the latest desktop version available.

    Java (JDK) 7 is now certified for E-Business Suite 12.0 and 12.1 application and database tier servers.  For instructions on upgrading your EBS 12.x environments, see:

    The Java version currently in your environment

    Oracle E-Business Suite Release 12 Rapid Install delivers the following Java SE Development Kit (JDK) Versions for use by Oracle E-Business Suite:

    Release 12.0.x

      • Java SE Development Kit (JDK) Version 5.0 on the application tier
      • Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
      • Java SE Runtime Environment (JRE) Version 5.0 on the database tier

    Release 12.1.x

      • Java SE Development Kit (JDK) Version 6.0 on the application tier
      • Java SE Development Kit (JDK) Version 1.4.2 on the OracleAS 10g 10.1.2 application tier hosting Forms and Reports services
      • Java SE Runtime Environment (JRE) Version 6.0 on the database tier

    You can now upgrade to the newer Java 7.0 Update on all EBS application tier and database tier nodes. Please note that the JRE 7.0 upgrade on the database tier is independent from the others. But if the application tier nodes are planned to be upgraded to Java 7.0, the same upgrade in the OracleAS 10.1.2 ORACLE HOME must be planned together.

    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 will change 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. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

    1. EBS 11i Extended Support ends November 2013
    2. EBS 12.0 Extended Support ends January 2015
    3. EBS 12.1 Extended Support ends December 2018

    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:

    Will EBS users be forced to upgrade to JDK 7 for EBS Servers?

    No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

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

    No. This upgrade will be highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  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 desktop clients. 

    Coexistence of JRE 6 and JRE 7 on Windows desktops

    The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 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 7 will be invoked instead of JRE 6 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 290801.1 and 393931.1.

    Applying Updates to JRE 6 and JRE 7 to Windows desktops

    Auto-update will keep JRE 7 up-to-date for Windows users with JRE 7 installed.

    Auto-update will only keep JRE 7 up-to-date for Windows users with both JRE 6 and 7 installed. 

    JRE 6 users are strongly encouraged to apply the latest Critical Patch Updates as soon as possible after each release. The Jave SE CPUs will be available via My Oracle Support.  EBS users can find more information about JRE 6 and 7 updates here:

    The dates for future Java SE CPUs can be found on the Critical Patch Updates, Security Alerts and Third Party Bulletin.  An RSS feed is available on that site for those who would like to be kept up-to-date.

    What will Mac users need?

    Oracle will provide updates to JRE 7 for Mac OS X users. EBS users running Macs will need to upgrade to JRE 7 to receive JRE updates.

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

    No. This upgrade will be highly recommended but will be optional for EBS application tier servers running on Windows, Linux, and Solaris.  You can choose to remain on JDK 6 for the duration of your respective EBS Extended Support period.  If you remain on JDK 6, you will continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6.

    References

    Related Articles

    Friday Jun 07, 2013

    WebCenter 11.1.1.7 Certified with E-Business Suite 12

    Oracle WebCenter Suite is an integrated suite of Fusion Middleware 11gR1 tools used to create web sites and portals using service-oriented architecture (SOA).  Applications adapters are also available.

    WebCenter Development Framework

    WebCenter Portal 11.1.1.7 (a.k.a. Patchset 5) is now certified with Oracle E-Business Suite Release 12 (12.0.6 and higher; 12.1.1 and higher).  WebCenter Portal 11.1.1.7 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.7.0, also known as FMW 11gR1 Patchset 6. 

    Certified Platforms

    Oracle WebCenter 11gR1 Version 11.1.1.6 is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. For information on operating systems supported by Oracle WebLogic Server 11g and Oracle Portal, refer to the 'Oracle Fusion Middleware on WebLogic Server - System Certification' in the Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Certification Matrix.

    Migrating to Oracle WebCenter

    If you're currently using Oracle Portal, you should be aware that Portal is now in maintenance mode.  Updates with bug fixes will continue to be produced, but you should consider migrating to Oracle WebCenter for ongoing new features.

    References

    Related Articles

    Thursday Jun 06, 2013

    Discoverer 11.1.1.7 Certified with E-Business Suite

    Oracle Business Intelligence Discoverer is an ad-hoc query, reporting, analysis, and Web-publishing tool that allows end-users to work directly with Oracle E-Business Suite OLTP data.

    Discoverer graph screenshot

    Discoverer 11g (11.1.1.7) is now certified with Oracle E-Business Suite Release.  Discoverer 11.1.1.7 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.7.0, also known as FMW 11gR1 Patchset 6.  Certified E-Business Suite releases are:
    • EBS Release 11i 11.5.10.2 + ATG RUP 7 and higher
    • EBS Release 12.0.6 and higher
    • EBS Release 12.1.1 and higher

    Certified Platforms

    Oracle Discoverer Release 11g R1 Patch Set 6 (11.1.1.7) is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. For platform details, see:

    References


    Tuesday Jun 04, 2013

    Oracle Internet Directory 11gR1 11.1.1.7 Certified with E-Business Suite

    Oracle E-Business Suite comes with native user authentication and management capabilities out-of-the-box. If you need more-advanced features, it's also possible to integrate it with Oracle Internet Directory and Oracle Single Sign-On or Oracle Access Manager, which allows you to link the E-Business Suite with third-party tools like Microsoft Active Directory, Windows Kerberos, and CA Netegrity SiteMinder. 


    For details about third-party integration architectures, see:

    Oracle Internet Directory 11.1.1.7 is now certified with Oracle E-Business Suite Release 11i, 12.0 and 12.1.  OID 11.1.1.7 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.7.0, also known as FMW 11g Patchset 6.  Certified E-Business Suite releases are:
    • EBS Release 11i 11.5.10.2 + ATG PH.H RUP 7 and higher
    • EBS Release 12.0.6 and higher
    • EBS Release 12.1.1 and higher

    Supported Configurations

    Oracle Internet Directory 11.1.1.7.0 can be integrated with these single sign-on solutions for EBS environments:

    • Oracle Internet Directory (OID) and Directory Integration Platform (DIP) from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 11gR2 (11.1.2.0) with an Oracle E-Business Suite system (Release 11i, 12.0.6 or higher or 12.1.x).
    • Oracle Internet Directory and Directory Integration Platform from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 11gR1 Patchset 2 (11.1.1.7.0) with an Oracle E-Business Suite system (Release 12.0.6 or higher or 12.1.x).
    • Oracle Internet Directory and Directory Integration Platform from Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Access Manager 10g (10.1.4.3) with an existing Oracle E-Business Suite system (Release 11i or 12.1.x).
    • Oracle Internet Directory and Directory Integration Platform from Oracle Fusion Middleware 11gR1 Patchset 6 (11.1.1.7.0) with Oracle Single Sign-On Server and Oracle Delegated Administration Services Release 10g (10.1.4.3.0) with an existing Oracle E-Business Suite system (Release 11i, 12.0.6 or 12.1.x).
    Oracle Access Manager strongly recommended

    Oracle has two single sign-on solutions: Oracle Single Sign-On Server (OSSO) and Oracle Access Manager (OAM). Oracle strongly recommends that all new single sign-on implementations use Oracle Access Manager. Oracle Access Manager is the preferred solution going forward, and forms the basis of Oracle Fusion Middleware 11g. OSSO is no longer being actively developed and will not be ported to Oracle WebLogic Server.

    Platform certifications

    Oracle Internet Directory is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to the Oracle Fusion Middleware 11g System Requirements for more details.

    For information on operating systems supported by Oracle Internet Directory and its components, refer to the Oracle Identity and Access Management 11gR1 certification matrix.

    Integration with Oracle Internet Directory involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

    References

    Related Articles

    Friday May 10, 2013

    Oracle Access Manager 11gR1 Patchset 2 11.1.1.7 Certified with EBS 12

    Oracle Access Manager 11gR1 Patchset 2 (a.k.a. 11.1.1.7) is now certified with E-Business Suite Release 12.0 and 12.1.  Applying Oracle Access Manager 11gR1 Patchset 2 will provide you with the latest set of fixes for Oracle Access Manager 11gR1 which have been validated with Oracle E-Business Suite Release 12.0 and 12.1.

    Oracle has two single sign-on solutions, Oracle Single Sign-On Server (OSSO) and Oracle Access Manager. Oracle strongly recommends that all new single sign-on implementations use Oracle Access Manager. Oracle Access Manager is the preferred solution going forward, and forms the basis of Oracle Fusion Middleware 11g. Oracle Single Sign-On is no longer being actively developed and will not be ported to Oracle WebLogic Server.

    Prerequisites

    • Oracle E-Business Suite Release 12.1.1 and higher, Release 12.0 RUP 6 (12.0.6)
    • Oracle Internet Directory 11gR1 PS1 (11.1.1.2) or higher

    Platforms Certified

    Oracle Access Manager 11gR1 is certified to run on any operating system for which Oracle WebLogic Server 11g is certified. Refer to Oracle Fusion Middleware Supported System Configurations on the Oracle Technology Network (OTN):

    Integration with Oracle Access Manager involves components spanning several different suites of Oracle products. There are no restrictions on which platform any particular component may be installed so long as the platform is supported for that component.

    References

    The following documents have been updated to include a new table listing Oracle Access Manager 11gR1 bundle patches that have been certified with Oracle E-Business Suite Release 12:

    Related Articles

    Thursday May 09, 2013

    Configuring Integrated SOA Gateway in Multinode EBS Environments

    The E-Business Suite's three-tier architecture consists of application tier services such as Web Application Services (oacore, oafm, Forms), Web Entry Point Services, Batch Processing Services, Root Services and database tier processes and data. A node represents a physical server with a set of processes. When application and database processes are distributed across multiple servers, it is called a multi-node installation. Generally, a hardware load-balancer is used to distribute EBS traffic between multiple nodes.

    Load-balanced multi-node EBS environment

    Oracle E-Business Suite Integrated SOA Gateway (ISG) provides a SOA-based infrastructure to provide and consume web service in EBS. The Integrated SOA Gateway can be configured for use in multi-node EBS environments; see:

    Configuring Oracle E-Business Suite Integrated SOA Gateway Release 12.1.2 and Release 12.1.3 in a Multinode Environment (Note 1081100.1)

    This document's steps for web service generation and deployment in multi-node environments should be followed for each EBS Public API exposed as web service.

    How to set up Integrated SOA Gateway in multi-node environment

    Service Provider:  ISG generates web service artifacts and stores them in the Instance Home (INST_TOP). Regardless of whether a shared file system is used in EBS multi-node installation, ISG’s Service Provider should be configured to synchronize web service artifacts across all EBS application tier nodes.

    Service Invocation Framework:  ISG stores metadata about the web service to be invoked in database tables. However, if the target web service resides outside a corporate firewall, then you need to ensure that the EBS host has access to WSDL and target web service endpoints required for sending SOAP requests. This requires setting up Proxy Host and Port at appropriate EBS application tiers; see the "Setup Tasks" section in Chapter 9 in this guide:

    Oracle E-Business Suite Integrated SOA Gateway Implementation Guide [Part E12169-06].

    Proxy Host and Port setup should be done for each node in a multi-node environment.

    References

    Related Articles

    Wednesday May 08, 2013

    BPEL 11.1.1.7 Certified for Prebuilt E-Business Suite 12.1 SOA Integrations

    Service Oriented Architecture (SOA) integrations with Oracle E-Business Suite can either be custom integrations that you build yourself or prebuilt integrations from Oracle.  For more information about the differences between the two options for SOA integrations, see this previously-published certification announcement.

    There are five prebuilt BPEL business processes by Oracle E-Business Suite Release 12 product teams:

    1. Oracle Price Protection (DPP)

    1. Complex Maintenance, Repair & Overhaul (CMRO/AHL)

    1. Oracle Transportation Management (WMS, WSH, PO)

    1. Advanced Supply Chain Planning (MSC)

    1. Product Information Management (PIM/EGO)

    BPEL integration architecture diagram example

    Last year we announced the certification of BPEL 11.1.1.6 for Prebuilt E-Business Suite 12.1.3 SOA integrations.  The five prebuilt BPEL processes have now been certified with Oracle BPEL Process Manager 11g version 11.1.1.7 (in Oracle Fusion Middleware SOA Suite 11g).  These prebuilt BPEL processes are certified with Oracle E-Business Suite Release 12.1.3 and higher.

    Note: The Supply Chain Trading Connector (CLN) product team has opted not to support BPEL 11g with their prebuilt business processes previously certified with BPEL 10.1.3.5.  If you have a requirement for that certification, I would recommend contacting your Oracle account manager to ensure that the Supply Chain team is notified appropriately. 

    For additional information about prebuilt integrations with Oracle E-Business Suite Release 12.1.3, please refer to the following documentation:

    Certified Platforms

    • Linux x86 (Oracle Linux 4, 5)

    • Linux x86 (RHEL 5)

    • Linux x86 (SLES 10)

    • Linux x86-64 (Oracle Linux 4, 5, 6)

    • Linux x86-64 (RHEL 5)

    • Linux x86-64 (SLES 10) 

    • Oracle Solaris on SPARC (64-bit) (9, 10, 11)

    • HP-UX Itanium (11.23, 11.31)

    • HP-UX PA-RISC (64-bit) (11.23, 11.31)

    • IBM AIX on Power Systems (64-bit) (5.3, 6.1, 7)

    • IBM: Linux on System z (RHEL 5, SLES 10)

    • Microsoft Windows Server (32-bit) (2003, 2008) 

    • Microsoft Windows x64 (64-bit) (2008 R2)

    Getting Support

    If you need support for the prebuilt EBS 12.1.3 BPEL business processes, you can log Service Requests against the Applications Technology Group product family.

    Related Articles


    Thursday May 02, 2013

    Secure Global Desktop 5 Certified with E-Business Suite 12

    Screenshot of Oracle Secure Global DesktopOracle Secure Global Desktop provides secure access to centralized applications—Microsoft Windows, UNIX, mainframe, and midrange—from a variety of clients including Windows PCs, Oracle Solaris workstations, Linux PCs, and thin clients.  Secure Global Desktop 4.6 was certified with the E-Business Suite last year.

    Secure Global Desktop 5 is now certified with E-Business Suite 12.  

    Secure Global Desktop 5 is certified for use with Microsoft Windows Server 2003 and 2008 virtualized environments acting as desktop clients connecting to Oracle E-Business Suite Release 12 environments.  32-bit and 64-bit versions of Microsoft Windows Server are certified. These combinations may also be used in conjunction with Oracle VM, if required.

    Requirements

    Windows Server 2008 R2 (64-bit)

      • Windows Server 2008 R2 (64-bit) is certified with Oracle E-Business Suite 12.1.3 running:
      • Internet Explorer 8 (32-bit and 64-bit) or Internet Explorer 9 (32-bit and 64-bit)
      • JRE Plug-in 1.6.0_32 (32-bit and 64-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit and 64-bit) or higher

    Windows Server 2008 (32-bit)

    • Windows Server 2008 (32-bit) is certified with Oracle E-Business Suite 12.1.3 running:
    • Internet Explorer 8 (32-bit) or Internet Explorer 9 (32-bit)
    • JRE Plug-in 1.6.0_32 (32-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit) or higher

    Windows Server 2003 R2 (64-bit)

    • Windows Server 2003 R2 (64-bit) is certified with Oracle E-Business Suite 12.1.3 running:
    • Internet Explorer 8 (32-bit and 64-bit)
    • JRE Plug-in 1.6.0_32 (32-bit and 64-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit and 64-bit) or higher

    Windows Server 2003 R2 (32-bit)

      • Windows Server 2003 (32-bit) is certified with Oracle E-Business Suite 12.1.3 running:
      • Internet Explorer 8 (32-bit)
      • JRE Plug-in 1.6.0_32 (32-bit) or higher or JRE Plug-in 1.7.0_17 (32-bit) or higher

    References

    Related Articles

     

    Tuesday Apr 30, 2013

    Where Should EBS Concurrent Managers be Located?

    This FAQ topic continues to bounce around, suggesting that this needs to be called out explicitly:

    EBS concurrent managers do not need to be installed on database servers any more.

    Nick Quarmby correctly noted this as one of five common mistakes that customers make when installed the E-Business Suite:

    COMMON ERROR #2: Placing concurrent processing services and the database tier on the same node to improve performance.

    ORACLE’S RECOMMENDATION: There is no significant performance benefit to placing concurrent processing and the database tier on the same node. Your system will be more scalable if your database tier hardware is dedicated solely to serving the needs of the database. Patching, cloning and E-Business Suite administration will also be much easier as you will have at least one less APPL_TOP and application tier technology stack to maintain. Placing concurrent processing on the database tier node to distribute load might suggest that your application tier hardware is already undersized. You should place concurrent processing on the same nodes as your web/forms services or create a dedicated concurrent processing tier in exceptionally busy environments.

    Where is this correctly documented?

    This is currently noted in our official documentation here:

    • Oracle E-Business Suite Technology Stack Release Notes for Release 12.1.3 [ID 1098650.1]
    2.6 Updated Architectural Guidance

    With fast local networks and the typical co-location of database and application tier machines, it is now generally preferable to perform concurrent processing on a separate machine from the database. This facilitates ease of management and maintenance, and provides deployment flexibility.

    This is updated guidance is already reflected in our 12.1.3 Concepts Guide and Installation Guides, and will continue to be included in future versions of our documentation.

    A shibboleth of sorts

    Interestingly, this question is a bit of a shibboleth in the EBS sysadmin community.  DBAs who instinctively place the concurrent processing server on the same physical server as the database have been around a long time -- before gigabit network speeds made the placement irrelevant.

    In fact, sharp-eyed readers might notice that this is incorrectly-documented even in some versions of our official R12 Installation Guides, which may state erroneously: "Batch Processing services must be installed on the same node as the database."

    This is a documentation artifact from a bygone time.  This guidance doesn't apply any longer.


    Monday Apr 29, 2013

    How to Obtain Media Packs for Older Versions of Oracle Products

    Installation media for all Oracle products can be downloaded from the Oracle Software Delivery Cloud (SDC, formerly called Oracle eDelivery). You can use this site to obtain Media Packs for the latest versions of all licensable Oracle products.  Media Packs are available in zip and ISO formats, which you can unzip or burn to DVDs, respectively.  All of the download links on the Oracle Technology Network (OTN) point to the Software Delivery Cloud, making the latter the authoritative source for all Oracle downloads.

    Screenshot of Oracle Software Delivery Cloud

    For more information about SDC, see:

    Need to download older versions?

    The Oracle Software Delivery Cloud hosts the latest released versions.  There may be times when you need a media pack for an older release.  

    For example:

    As of today, the latest version of Oracle Access Manager available for download is Oracle Access Manager 11.1.2.1.0.

    We're certifying Oracle Access Manager 11.1.2.1.0 with the E-Business Suite right now.  In the interim, E-Business Suite customers should use only the 11.1.2.0.0 version.

    If you need a Media Pack for an older release, you can log a Service Request requesting the specific release.  Oracle Support has a team that's dedicated to handling these types of shipping requests and other non-technical issues.  Also see:

    Wednesday Apr 24, 2013

    Seven EBS 12 Products Supported on Linux, Solaris, and AIX

    Some earlier Oracle E-Business Suite R12 certifications on newer operating systems excluded the following products due to the lack of third-party product support:
    • Advanced Supply Chain Planning
    • Inventory Optimization
    • Constraint Based Optimization
    • Sourcing
    • Engineering
    • Work In Process
    • Manufacturing Scheduling

    These restrictions are now lifted and the products are now officially supported on the following operating systems:

    • Oracle Linux 6 and Red Hat Enterprise Linux 6 on Linux x86 (32-bit)
    • Oracle Linux 6 and Red Hat Enterprise Linux 6 on Linux x86-64 (64-bit)
    • Novell SUSE Linux Enterprise Server (SLES) 11 on Linux x86-64 (64-bit)
    • Solaris 11 on Oracle Solaris on SPARC (64-bit)
    • AIX 7 on IBM AIX on Power Systems (64-bit)
    References

    Tuesday Apr 23, 2013

    Using SAML-based Authentication for Web Services with Integrated SOA Gateway

    Web services provided by Oracle E-Business Suite Integrated SOA Gateway are secured at the transport level through SSL and at the message level through authentication tokens – Username Token and SAML Token (Sender Vouches). I will discuss SAML Token (Sender Vouches) here.

    Brief on SAML, SAML Token, SAML Token Profile

    Security Assertion Markup Language (SAML) is a XML-based framework to exchange security related information between Service Consumer, Identity Provider and Service Provider. The security information is expressed in terms of assertions. Statements about the subject or user form the SAML Token. 

    WS-Security defines a set of security token profiles for different types of tokens embedded within the SOAP message as headers. SAML Token Profile is one of the WS-Security Token Profiles that describe the syntax and meaning of SAML Tokens. SAML Tokens are embedded within SOAP messages by placing assertion elements inside the SOAP Header.

    As per WS-Security, there are three common methods to assure the Service Provider that the SOAP message came from the subject referenced in the token. The three common subject confirmation methods are Sender Vouches, Holder of Key, and Bearer. As of Oracle E-Business Suite Release 12.1.3, web services provided by Integrated SOA Gateway (inbound) support SAML Token using the Sender Vouches subject confirmation method.

    SAML Token - Sender Vouches

    SAML Tokens assert that the subject or user has already been authenticated. As the name suggests, in the Sender Vouches case, the Sender or SOAP web service client that sends the SOAP request message to SOAP web service vouches for the identity of the assertion’s subject.

    SAML flow diagram

    The SAML assertion may be provided by an external Identity Provider -- a SAML Authority or SAML Issuer. In this case, a client sends a SAML assertion request to a SAML Authority. The SAML Authority identifies the client, authenticates the subject, and sends SAML assertion as response to client. The client’s private key is used to sign both the assertion and the SOAP message body.

    The E-Business Suite's Integrated SOA Gateway uses Oracle Application Server’s Web Services Security framework. It verifies the digital signature in a SOAP request and extracts the SAML Token. It validates the SAML assertion such as the issuer, validity period, and authentication statement. It extracts the SAML Subject Name Identifier and verifies the same with registered Oracle Internet Directory (OID) for single sign-on users or with FND_USER table in Oracle E-Business Suite (EBS) database for non-single sign-on users. It uses Oracle Internet Directory to map the single sign-on user with the equivalent EBS user. The EBS username is then used for the authorization check for the web service execution.

    When to use SAML Sender Vouches based authentication for web services provided by Integrated SOA Gateway?

    SAML Token with Sender Vouches is best used for following scenarios:

    • Single Sign On: As part of your business process, you may want to authenticate once and propagate the authenticated identity as a SAML assertion to subsequent EBS web service calls.
    • Subject or user needs to be authenticated locally (at web service client end) or centrally by Identity Provider (or SAML Authority), and propagate the assertion to an EBS web service.

    How to use SAML Token Sender Vouches in Integrated SOA Gateway?

    The steps to expose an EBS API as web service are described in Oracle E-Business Suite Integrated SOA Gateway Implementation Guide and Developer's Guide

    • Create Grant for EBS API methods that you want to expose as web service operations
    • Generate and Deploy the EBS API as web service with SAML Token (Sender Vouches) authentication type
    • Configure client and EBS (server) for SAML  

    See Setting Up SAML Token Security for Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3 [Note 1144313.1] 

    This Note describes the steps to configure SOAP Web Service Client as well as Oracle E-Business Suite (SOAP Web Service Provider). In Integrated SOA Gateway, a SAML Token Sender Vouches policy is applied at the web service level or port level. You may have to configure EBS for SAML for all web services that are deployed with Authentication Type as SAML Token (Sender Vouches).

    • Invoke web service with SAML Token

    The Note also describes steps to test web service invocation with a SAML Token. Depending upon the client program, you may programmatically insert SAML assertions or let web service security policy enforcement products such Oracle Web Services Manager (OWSM) insert a SAML Token in a SOAP request message.

    References

    Related Articles

    About

    Search

    Categories
    Archives
    « April 2014
    SunMonTueWedThuFriSat
      
    1
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
       
           
    Today