Share the content if you found it is useful (You can share using 300 community websites) click "share" at the end of the post.

You are encouraged to leave a comment.








Thursday, June 14, 2012

URGENT Bulletin from Oracle - Disable JRE Auto-update for all E Business End Users



Posted: 13 Jun 2012 04:16 PM PDT
[Update 4:13 PM June 13, 2012: Added reference to My Oracle Support Note 1467442.1]
[Update 1:40 PM June 13, 2012:  Added more details on finding the Java Update tab, and options 1 to 3]
All desktop administrators must IMMEDIATELY disable the Java Runtime Environment (JRE) Auto-Update option for all Windows end-user desktops connecting to Oracle E-Business Suite Release 11i, 12.0, and 12.1.
Java auto-update logo
You can find this option via the Windows Control Panel > Java > "Update" tab.  Uncheck the "Check for Updates Automatically" checkbox.
If you can't find the "Update" tab
From the Java help page: What is Java Update?
§ The Update tab may not be available if your network administrator has disabled the Java Update feature during installation.
§ If you are not logged in to system as administrator then options to change Java update notifications will be greyed out and user will not be able to change it.
Your options are:
1.       Log into your PC using a userid with administrator privileges.
2.       If you don't have administrator privileges, you must contact your desktop administrators for further guidance.
3.       Check whether you're running the 32-bit or 64-bit JRE version.  The 64-bit version of JRE does not have an auto-update feature. If you have both the 32-bit and 64-bit JRE versions installed, the 64-bit Control Panel appears instead of the 32-bit version.  You can view the 32-bit version of the 'Java Control Panel' by running the 'javacpl.exe' from the JRE installation directory, for example:

C:\Program Files (x86)\Java\jre6\bin\javacpl.exe
Why is this required?
If you have Auto-Update enabled, your JRE 1.6 version will be updated to JRE 7. 
§ This may happen as early as July 3, 2012
§ This will definitely happen after Sept. 7, 2012, after the release of 1.6.0_35 (6u35). 
As of June 13, 2012, the time of this bulletin's publication, Oracle Forms is not compatible with Java 7.  Java 7 has not been certified with Oracle E-Business Suite. Oracle E-Business Suite functionality based on Forms -- e.g. Financials -- will stop working if you upgrade to JRE 7.
Reverting back to Java 6 from Java 7
If an E-Business Suite end-user's desktop has been inadvertently upgraded to JRE 7, you must:
1.       Uninstall JRE 7
2.       Reinstall the latest JRE 1.6 release.
Stay on Java 6 for now
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
Posted: 13 Jun 2012 10:29 AM PDT
I'm pleased to let you know that the latest Java Runtime Environment 1.6.0_33 (a.k.a. JRE 6u33-b03) is now certified with Oracle E-Business Suite Release 11i and 12.  
What's new in Java 1.6.0_33?

See the 1.6.0_33 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 1.6 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 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.

No comments:

Related Posts Plugin for WordPress, Blogger...

Let us be Friends...

Share |

Popular Posts

Labels

11.5.1. to 11.5.5 Cloning Procedure. 11g 11i 11i and R12 11i Autoconfig 11i Cloning 12.1.1 SSL 2 Node RAC Adconfig.sh errors out adgennls.pl adop Advanced Replication Apache version Apex Apex for Oracle database Apex Installation Apex Installation on Oracle E Business Suite. 11i with Apex Apex on 11i Apex on Oracle 11i Apex402 apexins.sql APPL_TOP Character Application Express Application server Issue APPLSYS password Apps Password Asynchronous Replication Autoconfig Autoconfig Managed Beehive Bit of operating system Block block media corrupt BPEL Central Inventory Character Set Conversion Cloning of 11i Cloning of Oracle Applications Clusterware Concurrent CPU 2011 CPU 2012 April CPU 2012 January. CPU 2012 October CRS custom top Custom Top Creation Database . Database Query Dataguard DBMS_REPAIR Demantra . Domain Name E Business Suite Migration EBS 12.2 EPM exp/imp Oracle Applications Flashback table flows_020200 FND_TOP/resource FNDCPASS FNDCPUCF Forms server upgrade Forms startup FRM-92101 Fusion Middleware Hostname Hot Backup Hot cloning HotBackup Hotbackup Cloning of Oracle Apps hrglobal.drv. NLS Saudi Arabian HRMS hyperion Import and Export Oracle Applications Install Oracle Installation of R12 Installation Steps integration Oracle EBS Issues Database issues Oracle EBS Issues with Upgrade 12.1.1 Java Mission Control Java Upgrade java/sql/SavePoint JInitiator Junk Characters Language Translation Linux Linux Migration listener trace Listner version Local Inventory Login Page Master-Master Replication Memory Tuning Multiple Language NLS Non-Autoconfig Enabled OBIEE 11g Installation OBIEE Issues OIM Opatch version OpenSSL ora-01031 Oracle oracle 11g Oracle Announcement Oracle Application servers Oracle Application services Oracle Applications Oracle Applications 11i oracle applications 12.2 Oracle Applications Cloning Oracle Applications Upgrade Oracle Applications. Oracle Apps cloning Oracle BPEL oracle certifications oracle database Oracle Database RMAN Oracle Database upgradation Oracle DB oracle E Business suite 12.2 Oracle EBS oracle EPM Oracle Forms Logo oracle Fusion Applications Oracle Inventory oracle news Oracle OUI Oracle R12 oracle Sun Solaris Oracle Tuning Oracle Virtual Box Oracle Webgate Oracle WMA configuration orcladmin password for Oracle Applications Pasta Configuration pasta.cfg patch PDF Performance Physical Standby Platform migration Printer Configuration Profile Option R12 RAC Rapid Install Rapidwiz Real Application Clusters 10g Recovery RMAN RMAN Recovery SA Gosi Service Oriented Architecture SOA SQLTXPLAIN SSL Configuration step-by-step upgrade Sun solaris Swap Tablespace Trace Enable Trace file Translation Synchronization Patch transport tablespace tuning Tuning SGA uifont.ali Underscore Universal Content Management updates.oracle.com Upgradation of 12.0.5 to 12.1.1 Upgrade Upgrade 11g Upgrade Apps Upgrade DB Upgrade to 11g UTF8 version of oracle applications versions Web server upgrade weblogic windows workflow version XML Publisher version