Thursday Jun 07, 2012

Java 6 Certified with Forms and Reports 10g for EBS 12

Java logoJava 6 is now certified with Oracle Application Server 10g Forms and Reports with Oracle E-Business Suite Release 12 (12.0.6, 12.1.1 and higher).

What? Wasn't this already certified?

No, but a little background might be useful in understanding why this is a new announcement.

We previously certified the use of Java 6 with E-Business Suite Release 12 -- with the sole exception of Oracle Application Server 10g components in the E-Business Suite technology stack.

Oracle Application Server 10g originally included Java 1.4.2 as part of its distribution.  E-Business Suite 12 uses, amongst other things, the Oracle Forms and Reports 10g components running on Java 1.4. Java 1.4 in the Oracle Application Server 10g ORACLE_HOME is used exclusively by AS 10g Forms and Reports' for Java functionality.  This version of Java is separate from the Java distribution used by other parts of EBS such as Oracle Containers for Java (OC4J).

What's new about this certification?

You can now upgrade the older Java 1.4 libraries used by Oracle Forms & Reports 10g to Java 6. This allows you to upgrade the Java releases within the Oracle Application Server 10g ORACLE_HOME to the the same level as the rest of your E-Business Suite technology stack components.

Why upgrade?

This becomes particularly important for customers as individual vendors' support lifecycle for Java 1.4 reaches End of Life:

  • Oracle's Sun JDK Release 1.4.2's End of Extended Support: February 2013
    (Sustaining Support indefinitely after)
  • IBM SDK and JRE 1.4.2's End of Service: September 2013
  • HP-UX Java 1.4.2's End-of-Life : May 2012
Along with Oracle Forms, Java lies at the heart of the Oracle E-Business Suite.  Small improvements in Java can have significant effects on the performance and stability of the E-Business Suite.  As a notable side-benefit, later versions of Java have improved built-in and third-party tools for JVM performance monitoring and tuning.

Our standing recommendation is that you always stay current with the latest available Java update provided by your operating system vendor. 

Don't forget to upgrade Forms & Reports to 10.1.2.3

E-Business Suite 12 originally shipped with Oracle Application Server 10g Forms & Reports 10.1.2.0.2.  That version is no longer eligible for Error Correction Support. New Forms and Reports 10g patches are now being released with Forms and Reports 10.1.2.3 as the prerequisite. Forms and Reports 10.1.2.3 was certified for EBS 12 environments in November 2008.

If you haven't upgraded your EBS 12 environment to Forms & Reports 10.1.2.3, this is a good opportunity to do so.

References

Related Articles


Monday Jun 04, 2012

Plans for Java 7 and E-Business Suite Certification

[Update Dec. 11, 2012: JRE 7 is now certified with the E-Business Suite; see this announcement for complete details.]

[Update Oct. 19, 2012: All customers can begin preparing for JRE 7 now by applying a Forms-based patch to their E-Business Suite environments.  For details, see: Planning Bulletin for JRE 7: What EBS Customers Can Do Today]

Java logoAs of June 2012, Java 7 has not been certified yet with Oracle E-Business Suite.  EBS customers should continue to run JRE 6 on their Windows end-user desktops, and JDK 6 on their EBS servers.

If a search engine has brought you to this article, please check the Certifications summary for our latest certified Java release.

Our plans for certifying Java 7 for the E-Business Suite

We plan on releasing the Java 7 certification for E-Business Suite customers in two phases:

  • Phase 1: Certify JRE 7 for Windows end-user desktops
  • Phase 2: Certify JDK 7 for server-based components

When will Java 7 be certified with EBS?

We're working on the first phase now. As usual, I cannot discuss release dates here, but you can monitor or subscribe to this blog for updates.

Current known issues with JRE 7 in EBS environments

Our current testing shows that there are known incompatibilities between JRE 7 and the Forms-invocation process in EBS environments.  We have been working directly with the Java division on this for a while now.  In the meantime, EBS customers should not deploy JRE 7 to their end-user Windows desktop clients. You should stick with JRE 1.6 for now. 

But wait, you previously said...

Older JRE certification announcements stated:

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 higher.  We test all new JRE releases in parallel with the JRE development process, so all 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 releases to your EBS users' desktops.

Yes, this is true.  This standard boilerplate text was written before JRE 7 was released, so there was no possibility of misunderstanding.  With the availability of JRE 7, that boilerplate needs to be revised to read:

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.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 releases to your EBS users' desktops.

References

Related Articles

Friday Apr 27, 2012

Sun JRE 1.6.0_32 Certified with Oracle E-Business Suite

Java logo

[Apr. 30, 2012 Update: Clarified certification information for JRE 7, added more details about Java 7 plans]

I'm pleased to let you know that the latest Java Runtime Environment 1.6.0_32 (a.k.a. JRE 6u32-b05) is now certified with Oracle E-Business Suite Release 11i and 12.  

What's new in Java 1.6.0_32?

See the 1.6.0_32 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions.  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.

All JRE 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.  We test all new JRE releases in parallel with the JRE development process, so all 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 releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What about Java 7?

We're working on our Java 7 certification for the E-Business Suite right now.  Our first set of certifications will cover JRE 7 for Windows desktops.  This will be followed by JDK 7 certifications for server-based components.  

These certifications haven't been completed yet.  You should remain on Java 6 for both desktop-based and server-based components until we announce those certifications.

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

References

Related Articles

Wednesday Feb 15, 2012

Sun JRE 1.6.0_31 Certified with Oracle E-Business Suite

Java logoI'm pleased to let you know that the latest Java Runtime Environment 1.6.0_31 (a.k.a. JRE 6u31-b05) is now certified with Oracle E-Business Suite Release 11i and 12.  

What's new in Java 1.6.0_31?

See the 1.6.0_31 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

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.

All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all 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 releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

References

Related Articles

Tuesday Dec 13, 2011

Sun JRE 1.6.0_30 Certified with Oracle E-Business Suite

Java logo

I'm pleased to let you know that the latest Java Runtime Environment 1.6.0_30 (a.k.a. JRE 6u30-b12) is now certified with Oracle E-Business Suite Release 11i and 12.  

What's new in Java 1.6.0_30?

See the 1.6.0_30 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

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:  for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26, and higher.

All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all 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 releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

References

Related Articles

Tuesday Nov 29, 2011

In-House Generated Certificates Supported for Signing E-Business Suite JAR Files

[Nov 30, 2011 Update: Removed certified platforms as this enhancement is certified for all E-Business Suite  platforms.]

The E-Business Suite uses Java Archive (JAR) files to deliver certain types of E-Business Suite content to desktop clients.  Previously we announced the support of securing JAR files with 3072-bit certificates signed by a third-party Certificate Authority (CA).  We now support securing JAR files with in-house generated certificates.  The new steps to use an in-house Certificate Authority for securing JAR files are provided in:

This enhancement is great news for those of you familiar with the warning that is triggered when using a self-signed certificate.  As a result of supporting self-signed certificates, the following warning can be avoided:


References
Related Articles

Saturday Oct 22, 2011

Latest DSTv17 Timezone Patches Available for E-Business Suite R11i

Hourglass iconIf your E-Business Suite Release 11i or 12 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. 

DSTv17 is now available and certified with Oracle E-Business Suite Release 11i. The DSTv17 update includes the timezone information from Olson tzdata 2011j. 

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

For more details about the timezones affected by the DSTv17 update, see:

Thursday Oct 20, 2011

Sun JRE 1.6.0_29 Certified with Oracle E-Business Suite

Java logoSome questions following our last few JRE certifications indicated that there's still lingering confusion about which JRE releases are safe to use with E-Business Suite environments.  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:  for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26.

As of today, you can also apply Sun Java Runtime Environment 1.6.0_29 (a.k.a. JRE 6u29-b11).  JRE 1.6.0_29 is certified with E-Business Suite Release 11i and 12.

All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all 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 releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What happened to JRE 1.6.0_28?

JRE 1.6.0_28 (6u28) was not released externally.  JRE 1.6.0_29 is a CPU Security Java release.

References

Related Articles

Monday Oct 17, 2011

Latest DSTv16 Timezone Patches Available for E-Business Suite 11i

Hourglass iconWe announced the certification of the DSTv16 update with E-Business Suite 12 last August.  The second part of that certification with EBS 11i is now available. The DSTv16 update includes the timezone information from Olson tzdata 2011g.

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

For more details about the timezones affected by the DSTv16 update, see:

Related Articles


Friday Oct 14, 2011

Latest DSTv17 Timezone Patches Available for E-Business Suite R12

Hourglass iconIf your E-Business Suite Release 11i or 12 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 August 2011 and released as DSTv16.

DSTv17 is now available and certified with Oracle E-Business Suite Release 12. The DSTv17 update includes the timezone information from Olson tzdata 2011j. 

DSTv17 is an interim release.  Its primary purpose is to include the new DST rules for Russia which take effect from 30th October 2011.  At this time the clocks will not move back one hour but will remain on "summer time" instead.

Patches for this release are available on a request-only basis.  If you require this patch for your operating system/patch configuration, you must request it explicitly from Oracle Support.

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

We last discussed the DSTv16 patches on this blog. The latest DSTv17 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv17 includes changes to the following timezones since the DSTv16 release:

  • Africa/Nairobi,
  • Africa/Dar_es_Salaam,
  • Africa/Kampala,
  • America/St_Johns,
  • America/Goose_Bay,
  • America/Resolute,
  • Asia/Yekaterinburg,
  • Asia/Omsk,
  • Asia/Novosibirsk,
  • Asia/Krasnoyarsk,
  • Asia/Irkutsk,
  • Asia/Yakutsk,
  • Asia/Vladivostok,
  • Asia/Magadan,
  • Asia/Kamchatka,
  • Asia/Anadyr,
  • Asia/Sakhalin,
  • America/Metlakatla,
  • Europe/Kaliningrad,
  • Europe/Moscow,
  • Europe/Samara,
  • Europe/Volgograd,
  • Pacific/Apia,
  • Canada/Newfoundland,
  • W-SU

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:

What happened to EBS 11i?

The certification of DST v17 with Oracle E-Business Suite Release 11i is still in progress.  Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates. You're welcome to monitor or subscribe to this blog for updates, which I'll post as soon as soon as they're available.    

Related Articles

Wednesday Aug 17, 2011

Sun JRE 1.6.0_27 Certified with Oracle E-Business Suite

Java logoSome questions following our last JRE certification indicated that there's still lingering confusion about which JRE releases are safe to use with E-Business Suite environments.  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:  for example, JRE 1.6.0_23, 1.6.0_24, 1.6.0_25, and 1.6.0_26.

As of today, you can also apply Sun Java Runtime Environment 1.6.0_27 (a.k.a. JRE 6u27-b07).  JRE 1.6.0_27 is certified with E-Business Suite Release 11i and 12.

All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all 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 releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_27?

See the 1.6.0_27 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

JRE 1.6.0_27 provides the following fixes and functionality change that may affect Oracle E-Business Suite customers:

  • The browser window opening behind the Forms window issue is now fixed for Windows Vista and Windows 7 users running IE.
  • Selecting the "Close Window" Link through Internet Explorer will no longer display a modal window with the prompt, "The webpage you are viewing is trying to close the tab, Do you want to close this tab?".
  • Due to JRE6u27 now adhering more strictly to the IE browser settings,  "File Export" and certain "Form Attachments" will now fail through IE without the correct browser setting for IE6, IE7 & IE8 users.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References

Related Articles

Tuesday Aug 09, 2011

Latest DSTv16 Timezone Patches Available for E-Business Suite R12

Hourglass iconIf your E-Business Suite Release 11i or 12 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 2011 and released as DSTv15.

DSTv16 is now available and certified with Oracle E-Business Suite Release 12. The DSTv16 update includes the timezone information from Olson tzdata 2011g. 

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

We last discussed the DSTv15 patches on this blog. The latest DSTv16 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv16 includes changes to the following timezones since the DSTv15 release:

  • Africa/Cairo
  • Africa/Casablanca
  • America/Juneau
  • America/Havana
  • America/Santiago
  • Asia/Amman
  • Atlantic/Stanley
  • Europe/Istanbul
  • Pacific/Honolulu
  • Pacific/Easter
  • Pacific/Apia
  • Egypt
  • Cuba
  • Chile/Continental
  • Turkey
  • US/Hawaii
  • Chile/EasterIsland
  • Asia/Istanbul

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:

What happened to EBS 11i?

The certification of DST v16 with Oracle E-Business Suite Release 11i is still in progress.  Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates. You're welcome to monitor or subscribe to this blog for updates, which I'll post as soon as soon as they're available.    

Related Articles

Wednesday Jun 08, 2011

Sun JRE 1.6.0_26 Certified with Oracle E-Business Suite

Java compatible logoYou might get a sense of deja vu when reading this article, but I'll keep repeating myself until it seems safe to stop.  To recap: the mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:

  • Sun Java Runtime Environment 1.6.0_26 (a.k.a. JRE 6u26-b03) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_26 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23, JRE 1.6.0_24, and JRE 1.6.0_25.
All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_26?

See the 1.6.0_26 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Friday May 27, 2011

Sun JRE 1.6.0_25 Certified with Oracle E-Business Suite

Java compatible logoThe mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:

  • Sun Java Runtime Environment 1.6.0_25 (a.k.a. JRE 6u25, 1.6.0_25-b06) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_25 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23 and JRE 1.6.0_24.
All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_25?

See the 1.6.0_25 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Wednesday Feb 23, 2011

Windows 7 Service Pack 1 Certified with E-Business Suite

windos7_logo2.png
There are three possible configurations for Windows 7 desktop clients:
  1. 32-bit Windows 7, 32-bit browsers, 32-bit JRE
  2. 64-bit Windows 7, 32-bit browsers, 32-bit JRE
  3. 64-bit Windows 7, 64-bit browsers, 64-bit JRE
We certified the first configuration in December 2009:  E-Business Suite with 32-bit Windows 7 desktop clients running 32-bit versions of Internet Explorer (IE) and Firefox with the 32-bit JRE.

We certified the second configuration in September 2010: E-Business Suite with 64-bit Windows 7 desktop clients running 32-bit versions of IE and Firefox with the 32-bit JRE.

I'm pleased to announce that Microsoft Windows 7 Service Pack 1 (SP1) is now certified with both of those configurations for Oracle E-Business Suite 11i and Oracle E-Business Suite R12 with the following minimum requirements:

Internet Explorer 8 (32-bit)
ie8_logo_125.png
Oracle E-Business Suite 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) (note 125767.1).
  • MLR Patch 8888184
  • Java client plug-in JRE 1.6.0_03 (32-bit) or higher.
Oracle E-Business Suite R12.0.x Prerequisites
  • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or higher.
  • Oracle Forms Version 10.1.2.3 or higher.
  • Java client plug-in JRE 1.6.0_03 (32-bit) or higher.
Oracle E-Business Suite R12.1.x Prerequisites
  • Oracle E-Business Suite 12.1.1 or higher.
  • Java client plug-in JRE 1.6.0_03 (32-bit) or higher.
Firefox 3.6.x (32-bit)
firefox_logo4.jpg
Oracle E-Business Suite 11i Prerequisites
  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or higher
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) or higher (note 125767.1)
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6)(patch 5903765) or higher
  • Applications Framework Patch 7651759
  • Java client plug-in JRE 1.6.0_10 (32-bit) or higher.
  • It is also strongly recommended that 11i.ATG_PF.H Rollup 6 (RUP 6) users apply patch 7567782 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. This is particularly important for running client side next-generation JRE plugin (JRE 1.6.0_10 or higher).
Oracle E-Business Suite R12.0 Prerequisites
  • Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or higher.
  • Applications Framework Patch 7602616
  • Java client plug-in JRE 1.6.0_10 (32-bit) or higher.
  • It is also strongly recommended to apply patch 7567840 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. This is particularly important for running client side next-generation JRE plugin (JRE 1.6.0_10 or higher).
Oracle E-Business Suite R12.1 Prerequisites
  • Oracle E-Business Suite 12.1.1 or higher.
  • Java client plug-in JRE 1.6.0_10 (32-bit) or higher.
  • Exceptions
Oracle JInitiator Not Supported

Premier Support for Oracle JInitiator has expired for E-Business Suite customers.

Premier Support for Oracle JInitiator 1.1.8 ended in December 2008, and Premier Support for Oracle JInitiator 1.3 ended for EBS customers in July 2009.  For more information about JInitiator desupport and switching your EBS end-users from JInitiator to the Sun JRE, see:
Windows 7 desktop clients are certified only with the native Sun Java Runtime Engine (JRE) with Windows 7.  Oracle JInitiator was built on top of Java 1.3.  Java 1.3 is desupported by Sun Microsystems and and not compatible with either Windows Vista or Windows 7.  We have no plans to certify Oracle JInitiator with Windows 7.

On Hacking Up JInitiator -- Please Don't

Various creative individuals have discovered that it's possible to replace a certain DLL in Oracle JInitiator 1.3 with a JVM from, say, JDK 1.6. I can't personally testify that these hacks work. I can say that this kind of surgery makes me intensely uncomfortable.

While it's nice to see creative initiative, I have to remind you that Oracle would regard this as a customization. We don't recommend customizing Oracle JInitiator for production environments.

What About Earlier Versions of IE?

Microsoft only supports IE 8 on Windows 7 desktops.  Microsoft does not support earlier versions of IE on Win7, so Oracle is only able to support IE8 on Windows 7 clients for the E-Business Suite.

Exceptions to this certification

Oracle JDeveloper 10g is not certified on Windows 7 desktop clients.  Our Fusion Middleware group has not publicly announced any plans for this certification.  If you are interested in this combination, I strongly recommend your logging a formal Service Request via My Oracle Support against the JDeveloper product to request it.

For information on other client based products that are not certified on Windows 7 please see:
Why are you interested in the third configuration?

As I mentioned in my previous update on this topic, we've certified the first two configurations and we're working on the third.  You've asked for it, so we'll deliver.

That said, I am curious about your business need for the final certification (Win7 64-bit + 64-bit browsers and JREs).  Firefox 64-bit releases seem to lag in functionality and in the general release cycle.  Some reports suggest that 64-bit browsers do not necessarily provide improved performance across the board, and may have compatibility issues -- most notably with Flash, since Adobe is still working on their 64-bit Flash Player.

Even more telling, in fresh installs of Windows 7 64-bit, Microsoft configures the default browser to be IE 32-bit, not IE 64-bit.  In other words, end-users need to take an extra step to run the 64-bit version of IE. 

If you're planning to reconfigure your users' desktops to invoke a 64-bit browser by default, I'd be very interested in understanding your reasons.  Feel free to post a comment here or drop me an email.

References
Related Articles

Tuesday Feb 15, 2011

Sun JRE 1.6.0_24 Certified with Oracle E-Business Suite

jceecolorlogo2.gif
The mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:
  • Sun Java Runtime Environment 1.6.0_24 (a.k.a. JRE 6u24, 1.6.0_24-b07) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_24 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23.
All JRE 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 higher.  We test all new JRE releases in parallel with the JRE development process, so all JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_24?

See the 1.6.0_24 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Wednesday Jan 12, 2011

Latest DSTv15 Timezone Patches Available for E-Business Suite

Wooden_hourglass_small2.jpg
If your E-Business Suite Release 11i or 12 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 July 2010 and released as DSTv14. DSTv15 is now available and certified with Oracle E-Business Suite Release 11i and 12.

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
We last discussed the DSTv14 patches on this blog. The latest "DSTv15" timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv15 includes changes to the following timezones since the DSTv14 release:
  • Africa/Cairo 2010 2010
  • Egypt 2010 2010
  • America/Bahia_Banderas 2010 2010
  • Asia/Amman 2002
  • Asia/Gaza 2010 2010
  • Europe/Helsinki 1981 1982
  • Pacific/Fiji 2011
  • Pacific/Apia 2011
  • Hongkong 1977 1977
  • Asia/Hong_Kong 1977 1977
  • Europe/Mariehamn 1981 1982
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:
Related Articles

Tuesday Dec 07, 2010

Mismanaged Session Cookie Issue Fixed for EBS in JRE 1.6.0_23

jceecolorlogo2.gif
At last:  some good news for those of you affected by the mismanaged session cookie issue in E-Business Suite environments.  This issue is resolved by the latest Sun Java Runtime Environment 1.6.0_23 (a.k.a. JRE 6u23, internal version 1.6.0_23-b05).

See the 1.6.0_23 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Monday Nov 15, 2010

Two New Options for Signing E-Business Suite JAR Files Now Available

We use Java Archive (JAR) files to deliver certain types of E-Business Suite content to end-user desktop clients.  JAR files can be digitally signed for increased security. 

Oracle E-Business Suite uses a self-signed certificate to sign the JAR files that are downloaded to the client PC when launching forms and other applets (such as Workflow Status Diagram or Account Hierarchy Manager).  By default, E-Business Suite JAR files are signed with 1024-bit self-signed digital certificates.  Self-signed digital certificates can trigger Windows security warnings like this:

Windows Warning dialog box triggered with self-signed Java content - the application's digital certificate cannot be verified - dig_sig_warning.png
Some E-Business Suite users have advanced requirements for signing JAR files, including the ability to:
  1. Sign E-Business Suite JAR files with 3072-bit certificates
  2. Sign E-Business Suite JAR files with digital certificates from third-party Certificate Authorities (CA) (e.g.Verisign, Comodo, etc.)
I'm pleased to announce that both of these advanced JAR file signing options are now certified for Oracle E-Business Suite Release 11i and 12.

What are the benefits of these new signing options?

The first of these two new signing options meets the latest recommendations of the US National Institute of Standards and Technology (NIST):
The second option allows you to prevent the potentially-alarming warning from being triggered when your users access certain E-Business Suite functions for the first time.

Oracle E-Business Suite Release 12 Certified Platforms
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (RHEL 3, 4, 5)
  • Linux x86 (SLES 9, 10)
  • Linux x86-64 (Oracle Linux 4, 5)
  • Linux x86-64 (RHEL 4, 5)
  • Linux x86-64 (SLES 9, 10) 
  • Oracle Solaris on SPARC (64-bit) (8, 9, 10)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • IBM Linux on System z** (RHEL 5, SLES 9, SLES 10)
  • HP-UX Itanium (11.23, 11.31)
  • HP-UX PA-RISC (64-bit) (11.11, 11.23, 11.31)
  • Microsoft Windows Server (32-bit) (2003, 2008 for EBS 12.1 only)
Oracle E-Business Suite Release 11i Certified Platforms
  • Linux x86 (Oracle Enterprise Linux 4, 5)
  • Linux x86 (RHEL 3, 4, 5)
  • Linux x86 (SLES 8, 9, 10)
  • Linux x86 (Asianux 1.0)
  • Oracle Solaris on SPARC (64-bit) (8, 9, 10)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • HP-UX PA-RISC (64-bit) (11.11, 11.23, 11.31)
  • HP Tru64 (5.1b)
  • Microsoft Windows Server (32-bit) (2000, 2003)
References
Related Articles

Wednesday Oct 13, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_22

I'm afraid that this blog article comes bearing continued bad news about our latest JRE release.

jceecolorlogo2.gif
My colleagues in the Java division shipped Java Runtime Environment 1.6.0_22 (a.k.a. JRE 6u22, internal version 1.6.0_22-b04) last week.  See the 1.6.0_22 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

Unfortunately, like other recent JRE releases, this latest release of JRE 6u22 (1.6.0_22-b04) still has the 'Mismanaged Session Cookie' issue that we reported in earlier articles.  This can cause a failure of the following E-Business Suite functions with certain desktop and browser combinations, notably for IE 6 and 7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails

A JRE plug-in release with fixes for these issues is only available through patch 10189354.  Patch 10189354 contains JRE 1.6.0_22-b03.  This fixed version is not available as a download from Sun or through the Java Update Mechanism (which continues to offer only JRE 1.6.0_22-b04).  This fix will not be available through the normal Sun distribution channels until a future release of JRE 1.6.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for JRE 1.6.0_23 or later
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_22-b03 (released via patch 10189354)
  4. Disable next-generation Java through the 'Java Control Panel'
I understand that this is a frustrating state of affairs and I apologize for the continued delay in resolving this once and for all.  We're continuing to work with our colleagues in the Java division to get this set of fixes into the main JRE codelines.  I'll post updates here as soon as I have more information to share.

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 Sep 10, 2010

Windows 7 64-bit Clients + 32-bit Browsers Certified with EBS 11i & 12

windos7_logo2.png

[July 21, 2011 Update:  Added new client-server component certifications]

[Update Sep 15, 2010:  Changed JRE 1.6.0_03 to JRE 1.6.0_10 for Firefox and EBS 12.1 sections]

There are three possible configurations for Windows 7 desktop clients:

  1. 32-bit Windows 7, 32-bit browsers, 32-bit JRE
  2. 64-bit Windows 7, 32-bit browsers, 32-bit JRE
  3. 64-bit Windows 7, 64-bit browsers, 64-bit JRE
We certified the first configuration in December 2009:  E-Business Suite with 32-bit Windows 7 desktop clients running 32-bit versions of Internet Explorer (IE) and Firefox with the 32-bit JRE.

I'm very pleased to announce that the second configuration is now certified.  You may now run 64-bit Windows 7 desktop clients with 32-bit IE and Firefox with the 32-bit JRE and Oracle E-Business Suite Release 11i and 12.

Internet Explorer 8 (32-bit)
ie8_logo_125.png
Oracle E-Business Suite 11i Prerequisites
  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or later
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or later.
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) (Note 125767.1).
  • MLR Patch 8888184
  • Java client plug-in JRE 1.6.0_03 (32-bit) or later
Oracle E-Business Suite R12.0 Prerequisites
  • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or later.
  • Oracle Forms Version 10.1.2.3 or later.
  • Java client plug-in JRE 1.6.0_03 (32-bit) or later
Oracle E-Business Suite 12.1 Prerequisites
  • Oracle E-Business Suite 12.1.1 or higher
  • Java client plug-in JRE 1.6.0_03 (32-bit) or later
Firefox 3.6 (32-bit)
firefox_logo4.jpg
Oracle E-Business Suite 11i Prerequisites
  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or later
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) or later (note 125767.1)
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6)(patch 5903765) or later
  • Applications Framework Patch 7651759
  • Java client plug-in JRE 1.6.0_10 (32-bit) or later
  • It is also strongly recommended to apply patch 7567782 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. This is particularly important if using client side next-generation JRE plugin (JRE 1.6.0_10 or later).
Oracle E-Business Suite R12.0 Prerequisites
  • Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or later
  • Applications Framework Patch 7602616
  • Java client plug-in JRE 1.6.0_03 (32-bit) or later
  • It is also strongly recommended to apply patch 7567840 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. This is particularly important if using client side next-generation JRE plugin (JRE 1.6.0_10 or later).
Oracle E-Business Suite R12.1 Prerequisites
    • Oracle E-Business Suite 12.1.1 or higher
    • Java client plug-in JRE 1.6.0_10 (32-bit) or later
Exceptions to this certification

Microsoft Windows 7 (64-bit) is currently not certified as a desktop client operating system for any Oracle client-based products, including:
  • BI Publisher Desktop (a.k.a. XML Publisher)
  • Discoverer Administrator Desktop
  • Sales for Handhelds (Outlook desktop synchronization client)
  • Workflow Builder Client
  • XML Gateway Message Designer
  • (July 21, 2011 Update: The three struck-through components above are now certified on Windows 7) 

Oracle JInitiator Not Supported

Premier Support for Oracle JInitiator has expired for E-Business Suite customers.

Premier Support for Oracle JInitiator 1.1.8 ended in December 2008, and Premier Support for Oracle JInitiator 1.3 ended for EBS customers in July 2009.  For more information about JInitiator desupport and switching your EBS end-users from JInitiator to the Sun JRE, see:
Windows 7 desktop clients are certified only with the native Sun Java Runtime Engine (JRE) with Windows 7.  Oracle JInitiator was built on top of Java 1.3.  Java 1.3 is desupported by Sun Microsystems and and not compatible with either Windows Vista or Windows 7.  We have no plans to certify Oracle JInitiator with Windows 7.

On Hacking Up JInitiator -- Please Don't

Various creative individuals have discovered that it's possible to replace a certain DLL in Oracle JInitiator 1.3 with a JVM from, say, JDK 1.6. I can't personally testify that these hacks work. I can say that this kind of surgery makes me intensely uncomfortable.

While it's nice to see creative initiative, I have to remind you that Oracle would regard this as a customization. We don't recommend customizing Oracle JInitiator for production environments.

What About Earlier Versions of IE?

Microsoft only supports IE 8 on Windows 7 desktops.  Microsoft does not support earlier versions of IE on Win7, so Oracle is only able to support IE8 on Windows 7 clients for the E-Business Suite.

Why are you interested in the third configuration?

As I mentioned in my previous update on this topic, now that we've certified the second configuration, we'll move on to the third.  You've asked for it, so we'll deliver.

That said, I am curious about your business need for the final certification (Win7 64-bit + 64-bit browsers and JREs).  Firefox 64-bit releases seem to lag in functionality and in the general release cycle.  Some reports suggest that 64-bit browsers do not necessarily provide improved performance across the board, and may have compatibility issues -- most notably with Flash, since Adobe is still working on their 64-bit Flash Player.

Even more telling, in fresh installs of Windows 7 64-bit, Microsoft configures the default browser to be IE 32-bit, not IE 64-bit.  In other words, end-users need to take an extra step to run the 64-bit version of IE. 

If you're planning to reconfigure your users' desktops to invoke a 64-bit browser by default, I'd be very interested in understanding your reasons.  Feel free to post a comment here or drop me an email.

References
Related Articles
The following 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 Aug 13, 2010

Special JRE 6u21-b08 Build Now Available for EBS Customers

jceecolorlogo2.gif
The painful saga of our recent JRE releases' issues with the Oracle E-Business Suite is almost over.  It is expected that a future release of JRE 1.6 will contain a mainline fix for the "Mismanaged Session Cookie" issues that exist with JRE 1.6.0_18 to 1.6.0_21 build 6 (6u21-b06), inclusive. 

There is an interim workaround until that new release is available.  JRE 1.6.0_21 build 8 (6u21-b08) is now available and certified for Oracle E-Business Suite 11i and R12. This Build of the native plug-in fixes the 'Mismanaged Session Cookie' issue for the JRE 6u21 stream, which could cause a failure of the following functionalities on certain desktop/browser combinations, and particularly prevalent for IE6 and IE7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails
Special release vehicle for this JRE build

This version of the plug-in is only available through patch 10021403 and is not available as a download through the usual channels or through the Java automatic update facility. The standard version of the plug-in remains at JRE 1.6.0_21 build 6 (6u21-b06). This fix will not be available through the usual channels until a future release of JRE 1.6.

This release also fixes the long standing z-ordering issue (HTML Window opens behind Forms Window) for Windows XP users running Internet Explorer. A permanent fix is not yet available for Firefox users or Windows Vista or Windows 7 users, therefore please continue to use one of the workaround options if required.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for the upcoming JRE release that includes this fix
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_20-b05 (released via patch 9915543)
  4. Deploy JRE 1.6.0_21-b08 (released via patch 10021403)
For further information and requirements please see:
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.

Tuesday Aug 10, 2010

Reminder: Use Java 6 for EBS on Sun, Windows, Linux Platforms

Several threads have crossed my inbox lately about Java 5 (a.k.a. JDK 1.5).  If you're running your E-Business Suite servers on on Linux, Windows, or Sun operating system platforms, you should be reminded that the End of Service Life for Java 5.0 was on October 30, 2009. 

SunJavaSEdownloadpagescreen2.jpg
That End of Service Life (EOSL) date for Java 5 applies to Java Standard Edition (Java SE) release families.  You have the option of migrating to Java Standard Edition for Business, which offers longer End of Service Life windows for different Java releases -- for example, up to June 2019 for Java 5.  I am not a Java licencing specialist, but my understanding is that Java Standard Edition for Business comes at an additional cost. For information about Java licencing, I would recommend contacting your Oracle account manager. 

For more details about the support-related differences between Java SE and Java for Business, see:
Does this affect your environments?

If all of the following apply to your environment:
  1. Your servers are running on Linux, Sun, or Windows operating systems
  2. Your servers are running either Java Standard Edition 4 (1.4) or 5 (1.5)
Then you must do one of the following:
  1. Migrate to the Java Standard Edition for Business release of your choice
  2. Upgrade to Java Standard Edition 6 (1.6)
For details about upgrading E-Business Suite environments to Java 6, see:
What about other server operating systems?

If you're running either HP-UX or IBM AIX, your Java release on those operating system platforms is supported by Hewlett-Packard and IBM, respectively.  You should check with those vendors for their End of Service Life dates for Java.

What are the support implications if I don't upgrade?

Here's a hypothetical situation: let's say that you haven't migrated to Java SE for Business or upgraded to Java SE 6.  You report an E-Business Suite issue that turns out to be related to either Java 1.5 or 1.5.  What are the support implications?

EBS Support will attempt to reproduce the issue on an Oracle Support environment.  Chances are high that that environment will already be upgraded to Java 6. 

If the issue cannot be reproduced on an environment running Java 6, it is likely that Oracle Support will recommend that you upgrade your environment to Java 6 before proceeding with further diagnostics or analysis.

Generally speaking, EBS Development will provide Java-related patches for Sun, Linux, and Windows-based issues that can be reproduced on Java 6.

Related Articles

Monday Jul 19, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_21

jceecolorlogo2.gif
My colleagues in the Java division shipped Java Runtime Environment 1.6.0_21 (a.k.a. JRE 6u21, internal version 1.6.0_21-b06) last week.  See the 1.6.0_21 Update Release Notes for details about what has changed in this release.

Unfortunately, this release of JRE 6u21 (1.6.0_21-b06) still has the 'Mismanaged Session Cookie' issue that we reported in earlier articles.  This can cause a failure of the following E-Business Suite functions with certain desktop and browser combinations, notably for IE 6 and 7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails
A JRE plug-in release with fixes for these issues is only available through patch 9915543.  Patch 9915543 contains JRE 1.6.0_20-b05.  This fixed version is not available as a download from Sun or through the Java Update Mechanism (which continues to offer only JRE 1.6.0_20-b02).  This fix will not be available through the normal Sun distribution channels until a future release of JRE 1.6.

A fixed version of the JRE 1.6.0_21 (6u21) plug-in is expected to be made available through a special patch download in the near future.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for JRE 1.6.0_22 or later
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_20-b05 (released via patch 9915543)
I understand that this is a frustrating state of affairs and I apologize for the continued delay in resolving this once and for all.  We're continuing to work with our colleagues in the Java division to get this set of fixes into the main JRE codelines.  I'll post updates here as soon as I have more information to share.

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.

Tuesday Jul 06, 2010

Latest DSTv14 Timezone Patches Available for E-Business Suite

Wooden_hourglass_small2.jpg
If your E-Business Suite Release 11i or 12 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 2010 and released as DSTv13. DSTv14 is now available and certified with Oracle E-Business Suite Release 11i and 12.

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
We last discussed the DSTv13 patches on this blog. The latest "DSTv14" timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv14 includes changes to the following timezones since the DSTv13 release:
  • Africa/Casablanca,
  • Africa/Tunis,
  • America/Argentina/San_Luis,
  • America/Argentina/San_Luis,
  • America/Tijuana, America/Santiago,
  • America/Asuncion,
  • Antarctica/Casey,
  • Antarctica/Davis,
  • Asia/Dacca,
  • Asia/Taipei,
  • Asia/Karachi,
  • Asia/Gaza,
  • Asia/Damascus,
  • Asia/Kamchatka,
  • Asia/Anadyr,
  • Europe/Samara,
  • Pacific/Easter,
  • Pacific/Fiji,
  • Pacific/Apia,
  • America/Ensenada,
  • Chile/Continental,
  • Asia/Dhaka,
  • ROC,
  • Chile/EasterIsland,
  • Mexico/BajaNorte
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:
Related Articles

Friday May 28, 2010

JRE 1.6.0_20 Build 5 Fixes E-Business Suite Compatibility Issues

Good news, worth sneaking under the publication wire prior to my vacation:  Sun Java Runtime Engine (JRE) 1.6.0_20 Build 5 (6u20-b05) fixes the mismanaged cookie session issue which could affect JRE 1.6.0_18 (6u18) to 1.6.0_20 (6u20-b02) users. This JRE release is only available through Patch 9553040. The Sun download version remains at 1.6.0_20 build 2 (6u20-b02), therefore you cannot uptake this fix through the Java automatic update facility. It is expected that this fix will be available through the usual delivery mechanism from Sun once JRE 1.6.0_21 (6u21) is released.  Until then, you can download it here:

patch-9553040.png

Patch 9553040 contains both a JRE (jrefb-6u20-rev-b05-windows-i586.exe) and a JDK (jdkfb-6u20-rev-b05-windows-i586.exe) executable. You only need to extract and install the JRE version from this patch to fix this issue.

Patch Installation Instructions
  1. Download patch 9553040
  2. Extract the jrefb-6u20-rev-b05-windows-i586.exe
  3. Run the executable to install on the desktop
If you wish to distribute this release as a download through Oracle E-Business Suite and users do not already have an earlier release of JRE 6u20 installed on their desktop, follow the installation instructions in the appropriate note:
If your users already have jre6u20 installed on their desktop, please uninstall the earlier release or over write it by installing this later version over it.

Related Articles

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

Thursday Apr 15, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_20

jceecolorlogo2.gif
My colleagues in the Java division have just released Java Runtime Engine (JRE) 1.6.0_20 today.  See the 1.6.0_20 Update Release Notes for details about what has been changed in this release.

The issues reported in the following articles still also apply to JRE 1.6.0_20:
Depending upon your security and Java deployment policies for your end-user desktops, you may need to update your users to this JRE release.  Unfortunately, you will have to balance your need for the fixes in JRE 1.6.0_20 against the impact of the open EBS compatibility issues reported with 6u18, 6u19, 6u20.

We're working closely with the Sun JRE team to get the open EBS compatibility issues resolved as quickly as possible.  This is being worked at the top priority.  Please monitor this blog for updates.


Monday Apr 05, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_19

jceecolorlogo2.gif
Sadly, the issues reported in the following article also apply to JRE 1.6.0_19:
Once again, if you haven't already upgraded your end-users to JRE 1.6.0_18 or 1.6.0_19, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).

We're working closely with the Sun JRE team to get this issue resolved as quickly as possible.  Please monitor this blog for updates.


Monday Mar 22, 2010

Warning: E-Business Suite Issues with Sun JRE 1.6.0_18

jceecolorlogo2.gif
Users need a Java client to run the Forms-based content in Oracle E-Business Suite.  With Oracle JInitiator 1.3 out of Premier Support as of July 2009, Apps users must run the native Sun Java Runtime Engine (JRE) to access this content.

In early 2008 we relaxed our certification and support policy for the use of the native Sun JRE clients with the E-Business Suite. The policy reflected a switch from certifying specific JRE versions for the E-Business Suite to specifying minimum versions, instead. This permits E-Business Suite users to run any JRE release above following minimum certified levels, even later ones that Oracle hasn't explicitly tested with the E-Business Suite:
  • JRE 1.5.0_13 and higher
  • JRE 1.6.0_03 and higher
Under our current policy, Oracle E-Business Suite end-users can upgrade their JRE clients whenever Sun releases a new JRE release on either the 1.5 or 1.6 versions. EBS users do not need to wait for Oracle to certify new JRE 1.5 or 1.6 plug-in updates with the E-Business Suite.

Known E-Business Suite Issues with JRE 1.6.0_18

We test every new JRE release with both E-Business Suite 11i and 12.  We have identified a number of issues with JRE 1.6.0_18.  If you haven't already upgraded your end-users to JRE 1.6.0_18, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).

Due to a regression in JRE 1.6.0_18 (6u18), the following Oracle Forms-based features may fail when running Oracle E-Business Suite through Internet Explorer;
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form in a new window from forms.
  • Opening an Applet in a new window from Oracle Forms (i.e. AHM)
The bug can cause the session cookie to be mismanaged causing a new iexplore.exe session to open on the desktop client. This affects the Oracle E-Business Suite releases in different ways:
  • If this problem occurs running Oracle E-Business Suite 11i a new login page is rendered rather than the correct window or functionality
  • If this problem occurs running Oracle E-Business Suite Release 12 the window opens with the following error:
fndgfm.jsp error : The current session is invalid. Unable to proceed without a valid session.
This issue is particularly prevalent for users running Internet Explorer 6 or 7.  These issues do not reproduce on all desktop client/Oracle E-Business Suite environment combinations, even from the same desktop client. 

Temporary Workaround for JRE 1.6.0_18 Issues

Users may still upgrade to JRE 1.6.0_18 (6u18) or later if required, for example if needing a critical fix from this or a later release of the plug-in.

The only workaround for affected users is to turn off Next-Generation Java from the 'Java Control Panel':
  1. Navigate to: Start > Control Panel > Java > Advanced > Java Plug-in 
  2. De-select the option "Enable the next-generation Java Plug-in (requires browser restart)" 
This issue is being investigated through Sun bug 6927268 - 'ShowDocument calls results in new iexplorer process'.

References
Related Articles

Friday Jan 22, 2010

Latest DSTv13 Timezone Patches Available for E-Business Suite

Wooden_hourglass_small2.jpg
If your E-Business Suite Release 11i or 12 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 July 2009 and released as DSTv11.  DSTv13 is now available and certified with Oracle E-Business Suite Release 11i and 12. 

Note that if you've prided yourself on keeping your environment up-to-date, you didn't miss DSTv12.  That version was not released externally.  DSTv13 is the next release after DSTv11.

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
We last discussed the DSTv11 patches on this blog.  The latest "DSTv13" timezone definition file is cumulative and includes all DST changes in Olson tzdata 2009s and earlier time zone definitions.  DSTv13 includes changes to the following timezones since the DSTv11 release:
  • Africa/Cairo
  • America/Argentina/San_Luis
  • America/Buenos_Aires
  • America/Cordoba, America/Catamarca
  • America/Argentina/Tucuman
  • Antarctica/Casey
  • Antarctica/Davis
  • Antarctica/Mawson
  • Asia/Hong_Kong
  • Asia/Karachi
  • Asia/Gaza
  • Asia/Damascus
  • Europe/Samara
  • Indian/Mauritius
  • Pacific/Fiji
  • Pacific/Apia
  • Egypt
  • America/Argentina/Buenos_Aires
  • America/Argentina/Cordoba
  • America/Argentina/Catamarca
  • Asia/Dhaka, Hongkong
  • NZ-CHAT
  • America/Rosario
  • America/Argentina/ComodRivadavia   
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:
What Have Your Experiences Been?

DST patching was a hot topic a few years ago, so much so that we convened some emergency web-based seminars for customers to clarify out the requirements for E-Business Suite environments. Since then, it seems like time zone patching has become more predictable and better-documented, and I haven't heard about any recent customer escalations in this area. I'd be interested in hearing about your experiences lately in keeping your Apps environment up-to-date with time zone patches; feel free to drop me an email or post a comment here with your thoughts.
About

Search

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