URGENT BULLETIN: All E-Business Suite End-Users Must Manually Apply JRE 6 Updates

[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]

[Update 10:00 AM June 20, 2012: Added reference to Note 1469230.1]

[Update 9:35 AM June 19, 2012: Added reference to Note 1412103.2]

[Update 11:40 AM June 14, 2012: Updated title based upon expanded guidance from Java team]

[Update 9:15 AM June 14, 2012: Updated entire text based on expanded guidance from Java team]

[Update 8:40 AM June 14, 2012: Clarified JRE version references]

[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]



As previously announced, Oracle will shortly stop providing public updates for JRE 6.


To ensure that Java Users remain on a secure version, Windows systems that rely on auto-update will be auto-updated from JRE 6 to JRE 7.

Until EBS is certified with JRE 7, EBS users should not rely on the windows auto-update mechanism for their client machines and should manually keep the JRE up to date with the latest versions of 6 on an ongoing basis.

How to get the latest version of JRE 6

Until November of this year, the latest version of JRE 6 can be found on the Download tab of the Java SE sectionin OTN.  After November of this year further CPU (critical patch updates) to JRE 6 will be available through My Oracle Support.  Having a current EBS support contract grants you the right to download and use these JRE 6 versions on clients accessing EBS.

Within your organization, you may distribute the latest version of JRE 6 to your users and ask them to run the installer on their systems (or use equivalent enterprise desktop distribution mechanisms).

To maintain the security of your users’ desktops it is strongly recommended that you repeat the steps above after each CPU release.

For Oracle Java SE Critical Patch Updates, the next three dates are listed on the Critical Patch Updates, Security Alerts and Third Party BulletinYou can subscribe to the RSS feed on the Bulletin above to receive updates to the CPU schedules.

Reverting back to Java 6 from Java 7

If an E-Business Suite end-user's desktop has been inadvertently upgraded to JRE 1.7, you must:

  1. Uninstall JRE 1.7
  2. Reinstall the latest JRE 1.6 release.

Stay on Java 6 for now

EBS customers should continue to run JRE 1.6 (a.k.a. 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. At this time, we cannot provide delivery dates, but you can monitor or subscribe to this blog for updates.

Current known issues with JRE 1.7 in EBS environments

Our current testing shows that there are known incompatibilities between JRE 1.7 and the Forms-invocation process in EBS environments.  In the meantime, EBS customers should not deploy JRE 1.7 to their end-user Windows desktop clients. EBS customers should remain on JRE 6 at this time. 

References

Related Articles

Comments:

Can this setting be applied via a script/command line? It would be helpful to push this across all of our user machines at once to avoid having to visit each workstation.

Posted by Erik Helgestad on June 13, 2012 at 11:37 AM PDT #

Steve,

Some users with Windows7 may not see the "Update" tab when they open Java from the Control Panel, as a Registry entry (or two) are missing for these users. There are some Windows notes regarding a conflict between win32 and win64 versions that may prevent the tab from appearing.

What plan of action should these users and customers take? Remove Java and reinstall?

Regards,
Scott

Posted by guest on June 13, 2012 at 11:48 AM PDT #

Erik, Scott,

Thanks for your questions. I'm investigating both of these with the Java team now.

Regards,
Steven

Posted by Steven Chan on June 13, 2012 at 12:11 PM PDT #

Same issue, no update tab. Please notify me when you have an answer. Thanks !

Posted by Nadine on June 13, 2012 at 01:01 PM PDT #

I'm on Windows 7, and I don't have the Update tab, but I went to the Advanced tab, under JRE Auto-Download, and selected Never. Is that the same thing?

Posted by Chris on June 13, 2012 at 01:28 PM PDT #

I'm also on Windows 7 and have disabled auto download like Chris. Same question - is it the same?

Posted by Steve Harville on June 13, 2012 at 01:50 PM PDT #

Hi, everyone,

I've just added a new section to the article above:

If you can't find the "Update" tab

Hope that helps!

Regards,
Steven

Posted by Steven Chan on June 13, 2012 at 02:12 PM PDT #

Thank you for confirming that work around for Windows 7 64bit and 32bit installations. Should those of us who need to disable across the entire enterprise push out the change to the EnableAutoUpdate and EnableJavaUpdate registry keys?

Posted by Erik Helgestad on June 13, 2012 at 02:15 PM PDT #

Hi, Erik,

I see lots of discussion about those keys in the OTN Discussion Forums. I don't see an official document from the Java team yet. I'm trying to validate this with the Java team directly. Stay tuned.

Regards,
Steven

Posted by Steven Chan on June 13, 2012 at 02:21 PM PDT #

Outdated Java is, and has been, the biggest security threat to users for some time, and restrictions like this are one of the biggest causes of that. I appreciate that you are working towards a solution to support 7, and I also appreciate that you can't give hard dates, but can you at least give a rough idea? A quarter a least?

Large enterprises need a way to estimate the impact of this, and without at least a rough notion of when this will be fixed it is very hard to plan.

Posted by guest on June 13, 2012 at 03:23 PM PDT #

Steven,

Is there a metalink note to this issue?

Thanks, - Praveen.

Posted by Praveen Challa on June 13, 2012 at 03:29 PM PDT #

Steve,

Is that limited to JRE 1.6? Should Auto-Update be disabled for JRE 1.5 too?

Regards,
Murad

Posted by guest on June 13, 2012 at 03:48 PM PDT #

Praveen,

I just updated the article with a pointer to My Oracle Support Note 1467442.1.

Regards,
Steven

Posted by Steven Chan on June 13, 2012 at 04:25 PM PDT #

Hi Steve,

We don't have many users who have core apps in Oracle Financials but we do have many users who uses OAF platform, will they be affected by this change to Java v7?

Regards,
Timmy

Posted by Timmy on June 13, 2012 at 04:26 PM PDT #

Hi, Timmy,

This affects EBS users who use Forms-based modules. That said, you still should have those users stick with JRE 1.6 until we've certified JRE 7 with the E-Business Suite.

Regards,
Steven

Posted by Steven Chan on June 13, 2012 at 04:54 PM PDT #

Hi Steve Chan,

I am quoting you here "Our current testing shows that there are known incompatibilities between JRE 7 and the Forms-invocation process in EBS environments. "

Is is safe to say this is specific to EBS Jars only? And it is not related a 9i forms product. My concern is that most EBS customers use standalone Discoverer 10g. Will they impacted as well ?

Thanks in advance.

Regards,

Sandeep

Posted by Sandeep Radhakrishnan on June 13, 2012 at 09:59 PM PDT #

Hi Steve,

Thank you very much for this critical update.

Regards,
Syed Muneebuddin Daimi

Posted by guest on June 13, 2012 at 10:11 PM PDT #

My question is about Discoverer 10g. Does your notice apply to Discoverer 10g forms as well ? OR is this purely an invocation issue of E-Biz forms as you have described it ?

Thanks in advance,

Sandeep Radhakrishnan

Posted by Sandeep Radhakrishnan on June 13, 2012 at 10:17 PM PDT #

C:\Program Files (x86)\Java\jre6\bin\javacpl.exe have to be executed as administrator, otherwise unchecking "Check for Updates Automatically" will not work.

regards
Krzysiek

Posted by Krzysiek on June 14, 2012 at 12:37 AM PDT #

I am slightly confused by this. I thought the point of Metalink 393931.1 was to tell EBS which version of JRE to use for the client. The client when connecting would then install that version and be tied to that version. Whether the client autoupgraded or not, the JRE version was then fixed to that EBS instance, as multiple JREs can co-exist on the client. I thought EBS would still only use the fixed version regardless of whether the user had upgraded or not until the sysadmin re-ran txkSetPlugin.sh. Similarly in 10g ias, you would configure formsweb.cfg to tell the system which version to use. Is Oracle saying that that is not the case? What have I misunderstood?

Additionally it would be useful if we were able to control Java by Active Directory Group Policy, I am informed that we are unable to do that by our Windows team. Is it possible to feed that back to Java division?

Posted by Rob on June 14, 2012 at 05:34 AM PDT #

If customer has installed 1.7, rather than de-install 1.7, can they disable 1.7 from the Java control panel (Java tab, then view)

Posted by Ethan Strominger on June 14, 2012 at 06:00 AM PDT #

Steven:
our pc are in a domain; in this case we had to change ("update" Tab) with Administrator user and each local users (one by one) and these users must have local administrator permissions.

In Java > "Advanced" tab there is a Settings called "JRE Auto-Download"; here we also need check "Never auto download"?
Thanks for your time and sorry for my English, is not very good yet.
Regards
Martin

Posted by Martin on June 14, 2012 at 06:29 AM PDT #

We have installed the version 6.31 available on Oracle Site. unfortunately we don't have the "Check for Updates Automatically" checkbox.
And we haven't any administrator access on our PC.

Have you got a way to know the value of the "check for updates automatically " ? is there a tool to know it ?

Posted by guest on June 14, 2012 at 07:23 AM PDT #

Please clarify the version numbering.
Is Java is going from 1.6 to 7? (this must surely be an abbreviated reference)
Is Jave going from 1.6 to 1.7? (but nowhere is 1.7 mentioned)
Is Java going to from 1.6 to 7.0? (this would be strange)
Thanks

Posted by guest on June 14, 2012 at 07:58 AM PDT #

in fact, we have install currently version 6.31 on our workstation.

if we read the note, it is said that we must block the auto_update otherwise we will get version 7 which is not compliant with Oracle 11.5.10

how can I know if the "check for updates automatically " set to yes or no since we don't have the "Check for Updates Automatically" checkbox and we are not administrator on our workstation ?

Posted by guest on June 14, 2012 at 08:04 AM PDT #

Steve,
In XP, I get a message than the application is requesting to use an older version of JAVA and offers the selection of 6.1.30.

If users select this, would this be O.K. or is this not a valid workaround?

Thanks,
Luis

Posted by Luis on June 14, 2012 at 08:38 AM PDT #

Steve is there a way to run some mass update for this? We do not want to go to every machine and make this update.

let me know if there is some script

Posted by guest on June 14, 2012 at 08:41 AM PDT #

Hi Steve and guest,

Please visit "Doc ID 290807 : Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i" section "Adding Additional Java Plug-in Versions"

Can this be used as a work-around instead of a mass push into client desktops, if that was possible ? I think most customers would send out an advisory to their employees and have a desktop administrator oversee its implementation.

That note speaks about hard-coding the additional Java plug-in version as a paragraph in the forms_web_config_file, copying over certified jre version to $OA_HTML/bin and then making a change to the profile option "ICX: Forms Launcher". But unfortunately the note also asks you to make that change at the user level. Can we not make this change at the site-level also ?

If push came to shove, we might just have to make do with an sql script to update the profile option at each user level.

Would that be kosher, Steve Chan ?

Regards,

Sandeep Radhakrishnan

Posted by Sandeep Radhakrishnan on June 14, 2012 at 09:04 AM PDT #

Note that I will not publish inflammatory or obscene comments. Please try to keep this discussion focussed on technical issues.

I've clarified JRE versioning references in the article above. JRE 1.6 = JRE 6, and JRE 1.7 = JRE 7.

Murad: If you have JRE 1.5 clients with

Auto-Update enabled, they should already

have been automatically updated to JRE

1.6.

Rob: The changes introduced with JRE's Next Generation Java have altered that behaviour. See Appendix B, "Static vs. non-static versioning and set-up options" in Note 393931.1 for more details. I've passed your feedback on to the Java team.

Luis: We always recommend using the latest JRE version. I would recommend deploying JRE 1.6.0_33 -- the latest version certified today. Regardless of whether you're using JRE 1.6.0_30 or a later version, you should disable Auto Update.

I'm researching the other outstanding questions.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 09:07 AM PDT #

Hi, Guest:

>how can I know if the "check for updates automatically"
>set to yes or no since we don't have the "Check for Updates >Automatically" checkbox and we are not administrator
>on our workstation ?

You should contact your desktop administrators for guidance on this.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 09:11 AM PDT #

Thanks for the piece of information. It helps me to communicate this out to wider audience within my company.

Posted by guest on June 14, 2012 at 09:15 AM PDT #

You indicate this may happen starting July 3rd - but if I go to the java site today and perform check my version - it indicates it wants to install Version 7, update 5. I think the problem can potentially occur immediately. Please confirm.

This really puts us in a bind - any way Oracle can prevent this version from being pushed out until the Ebusiness suite is certified?

Posted by guest on June 14, 2012 at 09:21 AM PDT #

Hi Steve,

We have applications using JInitiator.

But the Checkbox 'Check for updates Automatically' is enabled for all users. Will this also affect the end users? Should we have to uncheck the Checkbox frrm automatic updates?

Thanks & Regards,
Prasanna

Posted by guest on June 14, 2012 at 09:58 AM PDT #

Steven,
I am an administrator to this PC and I can also login as the Administrator and have done so. I went to the Java(32) Update tab and unchecked that check box. I then Ok'd the changes and left.

Then I went back to show another user how to change it and found that it was checked again. Somehow I am not able to keep it unchecked. Can you please advise?

Turtle

Posted by guest on June 14, 2012 at 10:01 AM PDT #

Hi, Prasanna,

JInitiator is well past its Support date. Please see the article linked above:

Roundup: Oracle JInitiator 1.3 Desupported for EBS Customers in July 2009
http://blogs.oracle.com/stevenChan/entry/roundup_oracle_jinitiator_13_desupported_in_july_2

I strongly recommend that you upgrade your JInitiator clients to the JRE plug-in immediately, and follow the instructions above to keep them up-to-date.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 10:11 AM PDT #

Hi,

The reason I ask is that customer is looking into this and has installed JRE 7 on a test workstation (Windows 7 workstation) and after resetting active X settings, custimer is able to get the EBS app to load and work okay (admittedly only quick tests so far).

Can you explanation why/how JRE 7 would cause Oracle EBS forms apps to not work, please?
Can you provide any further direction on this?

Best regards

Clarissa

Posted by Clarissa Rohrmann on June 14, 2012 at 10:28 AM PDT #

Here are some responses from the Java team to some of the outstanding questions.

Turtle: Can not reproduce. Could be some specific setting in his system. Can you file a Service Request with Java Support so that we can investigate this further?

Guest:

>You indicate this may happen starting July 3rd - but
>if I go to the java site today and perform check my
>version - it indicates it wants to install Version 7, update 5.

Java team: We have made JRE 7 the default version on java.com since 7u4. That is the recommend version for most desktop users. Only in cases when a customer must remain in JRE 6 should the instructions above be followed.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 10:33 AM PDT #

Hi, Clarissa,

The article states: "Our current testing shows that there are known incompatibilities between JRE 1.7 and the Forms-invocation process in EBS environments."

Your cursory tests may have only been on OA Framework modules. You will encounter issues when invoking Forms-based E-Business Suite products like Oracle Financials and Order Management.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 10:39 AM PDT #

Turtle-
Locate the javacpl.exe on your system, right click, and run it as administrator. I noticed this on my test machines as well (there are further notes in comments above).

Posted by Erik Helgestad on June 14, 2012 at 10:43 AM PDT #

Hi Steve,

We have already started taking steps to upgrade to JRE. In next few months we can see JRE is in its place.

But before that, wanted to know that whether Automatic updates will work even for jInitiator. Should we have to uncheck "Automatic Updates" for end users using JInitiator.

Thanks & Regards,
Prasanna K

Posted by guest on June 14, 2012 at 10:44 AM PDT #

Hi, everyone,

The Java team has reviewed your outstanding questions about disabling Auto Update. If you're having issues with that, please refer to:

http://www.java.com/en/download/help/java_update.xml

They have expressed regret that they don't have the resources to answer these types of questions here. If you have any questions about mass deployment, or encounter any issues with the guidance on that Java Update page, please log a formal Service Request with Java Support for additional assistance.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 10:48 AM PDT #

Hi, Prasanna,

I'm afraid that JInitiator wasn't part of our impact analysis, since it's been out of support for three years now.

Using first principles only:

Auto-Update updated JRE 1.5 clients to JRE 1.6 when the latter was released.

JInitiator was based on Java 1.3. If you have JInitiator clients that currently have Auto-Update enabled, and they have not already been updated to JRe 1.5 or 1.6, then it is unlikely that they will be updated to JRE 1.7.

But that's based upon logic, alone, and not testing. I would still recommend that you move up to the latest JRE 1.6 release as soon as you can, and then follow the instructions above to keep your clients up-to-date.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 10:58 AM PDT #

Steve: In Control Panel Java > Java > "Advanced" tab there is a Settings called "JRE Auto-Download"; here we also need check "Never auto download"?
Thanks
Martin

Posted by Martin on June 14, 2012 at 11:01 AM PDT #

Erik,
Thanks for the Note. I am only 3 days into Windows 7 as this is a new Laptop. So I thought that because i was an administrator that it did. That fixed my issue.

Regards,
Turtle

Posted by Turtle on June 14, 2012 at 11:02 AM PDT #

The solution for the problem that Turtle described is also addressed here:

http://www.java.com/en/download/help/javacpl.xml

(there is also a link to this on the main java update how-to page http://www.java.com/en/download/help/java_update.xml)

Steve, I would suggest adding both the above links into the body of the main article.

Regards,
Brandon

Posted by Brandon on June 14, 2012 at 12:06 PM PDT #

Hi, Steven,

I couldn't find an answer to one I think was asked earlier - is this just for EBS? We have home-grown 10G forms that we will be converting to 11G as soon as we get WLS running.

Thanks,
Mark

Posted by Mark on June 14, 2012 at 12:36 PM PDT #

Hi Steven,
As per your comment above, I understand that Java or Oracle team is not going to provide the Mass update script or exe for windows workstations?
Shld we wait for an official announcement or proceed with manual one by one user pcs update?
Can you please confirm this once again?
Regards,
Raghu

Posted by guest on June 14, 2012 at 12:46 PM PDT #

Hi Steven,
In the Control Panel - Java - Update (TAB)
do we have to uncheck the "Check for Updates Automatically" also ?

This should have been communicated directly to all DBA & users for their CSI# too

Thanks
Satish

Posted by guest on June 14, 2012 at 01:03 PM PDT #

Mark,

This applies to all Forms 10g-based applications, including both the E-Business Suite and any custom Forms applications that you might have deployed. EBS 12 is based on Forms 10g, so we haven't tested Forms 11g. Please watch My Oracle Support for bulletins about other affected Oracle products, including Forms 11g.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 03:03 PM PDT #

Hi, Raghu,

The Java team has not given me any indication that they will provide guidance or tools for mass-deploying this change in registry settings.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 03:06 PM PDT #

Satish,

Yes, that's right. Please follow the official instructions from the Java team on how to turn off this option:

http://www.java.com/en/download/help/java_update.xml

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 03:08 PM PDT #

Martin,

According to the official instructions from the Java team (http://www.java.com/en/download/help/java_update.xml), turning off the option on the Update tab will be sufficient.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 03:10 PM PDT #

Brandon,

Thanks for the suggestion and for the links. The Java team has specifically posted the revised version of the article, above. At this stage, the article is essentially frozen unless the Java team makes any additional changes.

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 03:11 PM PDT #

Hi Steven,
Thanks the link:
http://www.java.com/en/download/help/java_update.xml

There are some critical patches in Java’s 1.7 that fix a number of serious security vulnerabilities so now by asking us to turn off the update it putting us in a catch 22. If we upgrade then Forms won't work and if we dont' then we have to live with security vulnerabilities.

Any timeline as to when Oracle Appls will be certified with JRE7 ?

Thanks,
Satish

Posted by guest on June 14, 2012 at 03:34 PM PDT #

Hi, Satish,

The revised guidance above describes how you can keep your JRE 1.6 clients up-to-date.

Remember that Java 6 (JRE clients and server-level JDK releases) are supported until December 2016 for E-Business Suite customers. New Java updates for security, performance, and stability will be released to that date. For more information about Java SE Support dates, see:

http://www.oracle.com/technetwork/java/eol-135779.html

Regards,
Steven

Posted by Steven Chan on June 14, 2012 at 03:38 PM PDT #

Steven,

Does it mean the auto-update of JRE 7 will "automatically uninstall" all installed JRE 6 versions?

Because we did a couple of tests on PC with both JRE 1.7 and JRE 1.6 installed. We found that unless we disable (uncheck Enabled under JRE under control panel) or uninstall all installed JRE 1.6, JRE 1.6 is always used to launch R12 EBS forms so seems not a problem.

I think it'd be best if JRE auto-update will NOT uninstall and preserve JRE6, it is possible?

Geoff

Posted by Geoff on June 15, 2012 at 12:40 AM PDT #

Hi Steven,
I reviewed the link http://www.java.com/en/download/help/java_update.xml.
So, we are able to disable java auto update individually.

But, the issue here is to disable this option for all end users of E- business suite in our company. So could you provide the instructions to disable the flag for all users (to put it in grey to avoid manual override by someone)
Thanks in advance
David

Posted by David on June 15, 2012 at 03:09 AM PDT #

Hello Steve,

We tested Java 7 on both an XP and a Win7 PC and have not run into any issues with Oracle EBS. In the alert the there is the statement "Our current testing shows that there are known incompatibilities between JRE 1.7 and the Forms-invocation process in EBS environments" Is there any listing of these known incompatibilites? I would like to see if they are replicated on our test PCs.

Thanks.

Don L.

Posted by Don L. on June 15, 2012 at 08:10 AM PDT #

Turning off the option on the Update tab only remains in effect for the Windows session. Once you log off Windows it reverts back to automatic updates. So setting never check for updates is useless if user is logging off and on Windows. Any way to make this change permanent?

-Ed-

Posted by Ed Heyman on June 15, 2012 at 08:31 AM PDT #

Hi Steven,

I have gone to: http://www.java.com/en/download/help/java_update.xml. It does not adress about the below:

1) In Control Panel Java > Java > "Advanced" tab there is a Settings called "JRE Auto-Download"; need to check "Never auto download" box?
2) In Control Panel Java > Java > "Advanced" tab there is a Settings called "Java Plug-in"; Enable the next-generation Java Plug-in checkbox, should this be unchecked too?

Can you please kindly confirm?

Thanks, Violet

Posted by guest on June 15, 2012 at 09:19 AM PDT #

Hi Guys, how would we disable this for computers on a domain (group policy) and for computers off a domain (workgroup). we have about 3000 on a domain and 2500 off the domain. we do not want to go to each and every pc.

please advise if this is possible

thanks
Hugo

Posted by guest on June 19, 2012 at 01:19 AM PDT #

Hi, everyone -- and Hugo,

In case you haven't already tracked this down, the Java team has suggested that
the following My Oracle Support document may help with some of the questions
that you've been raising here:

Information Center: Installation & Configuration for Oracle Java SE [ID
1412103.2]

Regards,
Steven

Posted by Steven Chan on June 19, 2012 at 10:44 AM PDT #

Reminder -- please keep your comments technically-focussed.

I won't publish inflammatory, obscene, or ad hominem attacks. They're not permitted on Oracle sites, and they're just in poor taste. Try and stay civil -- we're all trying to do what's best for E-Business Suite customers.

Regards,
Steven

Posted by Steven Chan on June 19, 2012 at 12:55 PM PDT #

I reviewed 1412103.2 (a .2, never seen that, must be serious) but didn't find what I wanted. However I found this on a Symantec website, seems to work for 1.6

http://www.symantec.com/connect/blogs/turn-auto-update-sun-java-runtime

Create two files, deployment.config:
deployment.system.config=file\:C\:/WINDOWS/Sun/Java/Deployment/deployment.properties

This can be a URL on a common server for enterprise wide settings. Create the deployment.properties file:
#deployment.properties
#Sun Mar 13 17:58:03 GMT 2011
deployment.javaws.autodownload=NEVER
deployment.javaws.autodownload.locked=
The "locked" line means that users can't override the setting in their own profiles.
Put these two files in a Sun\Java\Deployment subfolder of your WIndows Directory.

I've tried it on my windows 7 machine and it defaults the radio button to never and locks out the panel. Will need some tests for our other OS clients but that'll do me for now.

Posted by Rob on June 19, 2012 at 02:37 PM PDT #

Hi Guys

i have read through the document, still doesnt explain anything about how to disable this via group policy or for alot of computers not on a domain. :(

any ideas? anyone

thanks

Hugo

Posted by Hugo on June 19, 2012 at 10:23 PM PDT #

Can you add to the main article instructions on how to disable auto-update? Some people may not know that you have go to Java in Control Panel (there's no entry for JRE) in order to disable JRE updates.

Posted by Glenn on June 20, 2012 at 08:07 AM PDT #

Glenn: The main article has a link to the following document:

Information Center: Installation & Configuration for Oracle Java SE (ID 1412103.2)

Regards,
Steven

Posted by Steven Chan on June 20, 2012 at 08:19 AM PDT #

Hi, everyone,

The Java team has just posted a new document on My Oracle Support:

FAQ - Java SE Auto Update (Doc ID 1469230.1)

This document addresses many of the outstanding questions you've posted here, including questions about why the Update tab doesn't show up in the Java Control Panel, and more.

If you still have additional questions about Java that aren't answered by this new FAQ, please log a formal Service Request against the Sun Java Support team.

Regards,
Steven

Posted by Steven Chan on June 20, 2012 at 10:02 AM PDT #

Is there a command line method to update the change to disable JRE Auto Update? If so, it will be possible for us to deploy a batch script throughout our enterprise using desktop management tools.

Posted by guest on June 20, 2012 at 12:11 PM PDT #

Hi, Guest,

I would encourage you to review the FAQ that was just posted: Note 1469230.1. I don't know if the Java team plans any subsequent updates to this document, but they explicitly have the following questions listed there:

Q7: Is there a way to change settings for the JRE centrally rather than going computer-by-computer?

Q8: Is there a way to install a given version of Java remotely?

Q10: How to create a centrally administrate deployment.properties file to lock down some of the deployment settings:

I'm not reposting the answers here, to ensure that that note is the central authoritative source for information even if changes are published downstream.

Regards,
Steven

Posted by Steven Chan on June 20, 2012 at 12:20 PM PDT #

if both the versions of JRE (6 and 7) exists on the windows desktop then which version of JRE will be picked to access EBS 11i?

Thanks,
-Mukarram.

Posted by Mukarram on June 21, 2012 at 09:12 PM PDT #

Hi, Mukarram,

Please refer to "Appendix B: Static vs Non-Static Versioning and Set Up Options" in Note 290807.1 for a detailed discussion of this for 11i environments.

In general, the non-static versioning model is used. This means that the latest installed version of JRE will be used, regardless of what's specified in the EBS server-level configuration files.

Regards,
Steven

Posted by Steven Chan on June 22, 2012 at 09:54 AM PDT #

Steven

What is the exact release date for JRE7? Because from the oracle ALERT we have received it was not clear. It mentioned as early as July-3rd.

We need to understand the urgency of the issue and when to request our users to disable the JRE auto-update setting.

thanks
Sami

Posted by guest on June 25, 2012 at 03:35 PM PDT #

As I understand it there is no good solution on running an Forms 10g-based application with both Java 1.6 and Java 1.7 on the same machine.

I found a suggestion that we put in this line in the formsweb.cfg file and then the user can choose which Java-version the application should use.

jpi_classid=clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA

But don't take the wrong java thenyou have to uninstalla java 1.7 again.

If it is a OK way to do it I don't know but we have som customers who shall use both java 1.6 and 1.7

Regard from Denmark

Lone

Posted by guest on June 28, 2012 at 10:37 AM PDT #

Lone,

Given the way you phrased it, I suspect that your comment is for generic Forms-based applications rather than the E-Business Suite. Nonetheless, you may find the discussion about static versioning in our E-Business Suite-specific documentation useful.

Please refer to "Appendix B: Static vs Non-Static Versioning and Set Up Options" in Note 290807.1 for a detailed discussion of this for 11i environments. The equivalent EBS 12 documentation is in Note 393931.1.

In general, the non-static versioning model is used. This means that the latest installed version of JRE will be used, regardless of what's specified in the EBS server-level configuration files.

Regards,
Steven

Posted by Steven Chan on June 28, 2012 at 12:03 PM PDT #

Steven,

please update this blog entry as and when more certification information is available.

Thanks,

Philip

Posted by guest on July 31, 2012 at 05:59 AM PDT #

Hi, Philip,

Yes, please monitor this blog for updates. We're making good progress with the JRE 7 certification with both Oracle E-Business Suite Release 11i and 12, but the overall initiative is still underway. Stay tuned.

Regards,
Steven

Posted by Steven Chan on July 31, 2012 at 09:14 AM PDT #

When is this certification going to be ready? in a month, 6 months?
Can you provide an estimate?

Posted by guest on August 03, 2012 at 11:51 AM PDT #

Hello, Guest,

We're not permitted to speculate about release dates. I can tell you that this certification has been top priority for both the E-Business Suite division and other products within Oracle. We've concluded testing of both EBS 11i and 12. We're working on producing patches for the compatibility issues we've identified.

We'll post more details as soon as they're available.

Regards,
Steven

Posted by Steven Chan on August 06, 2012 at 08:33 AM PDT #

Is Agile included in E-Business Suite in this article? My Agile customer faces some problems after auto-updated to 7, so I wonder if I can announce the same to this Agile customer.

Posted by guest on August 16, 2012 at 04:28 AM PDT #

Hello, Guest,

This bulletin applies only to the E-Business Suite. If you are encountering issues with Agile, I'd recommend that you log a formal Service Request with Oracle Support to get their recommendations for Agile.

Regards,
Steven

Posted by Steven Chan on August 16, 2012 at 08:27 AM PDT #

Hello Steven,

We are using EBS 11.5.10.2, currently most of our users are on version 6 and update 31, I think that translates to 1.6.0_31 something like that, if I understand this correctly we cant update to 7 if we did we cant use EBS at all, is that a true statement? And is it true even R12 version will not work with Java 7? And the reason we are asking is our system admin confirmed that we are having many security issues because we cant update to 7 it seems, its causing much and much everyday on many systems, please let us know what is your suggestion? Are they any closer to make 7 compatible?

Thanks -
Raj

Posted by Raj on August 16, 2012 at 05:23 PM PDT #

Hello, Raj,

We're working on completing our JRE 7 certification with the E-Business Suite right now. Please monitor this blog or other My Oracle Support communication channels for updates; we'll notify you as soon as this certification is completed.

In the interim, EBS users should remain on JRE 6, as noted in the article above.

Regards,
Steven

Posted by Steven Chan on August 17, 2012 at 11:20 AM PDT #

Steven,

Is there a way to prevent EBS from detecting the version of Java being used on a client's machine? We have found that pushing the Java Updates manually is quicker than updating the version that the Apps will push and then letting the users update themselves (in addition to the users not having the permissions to do this).

Is there a way we could tell the Apps "if the java version on the client pc is >= to the version you want to give them, ignore them?" Or something like that?

Thanks!

Richard

Posted by Richard on August 27, 2012 at 12:50 PM PDT #

Steven,

We have found that we can patch the user PCs faster than we can update the Applications and then have the users download and install the Applications version themselves (plus they don't have the rights to do this anyway).

Can we disable the applications from checking the client pc java version? Or maybe have the java version the applications wants to deliver check the version of the java on the user pcs and if they are the same or the client version is more recent, then the applications ignore the client?

Hope this makes sense.

Richard

Posted by Richard on August 27, 2012 at 12:52 PM PDT #

Richard,

Yes, that's the way it should work today. If the desktop client connecting to the E-Business Suite already has a JRE release that is >= to the release specified in the E-Business Suite's configuration, then the already-installed JRE release will be used.

This is documented in Notes 290807.1 and 393931.1, respectively. If you need help with those Notes, please don't hesitate to log a formal Service Request with My Oracle Support; we'll get you back on track quickly.

Regards,
Steven

Posted by Steven Chan on August 27, 2012 at 02:46 PM PDT #

Steven,
we are using EBS 11.5.10.2 and most of our users are on version 6 and update 31, using mostly Firefox.

Today many of them have installed 6 update 35, and they have got stuck and unable to get to Oracle Forms.

Any idea on what should we do? I don´t think we have anything strange, the pop-ups are allowed for our Oracle servers and I cannot find anything else.

Rgds, Covadonga

Posted by guest on September 03, 2012 at 01:52 AM PDT #

Hello, Covadonga,

I'm sorry to hear that you've encountered an issue with this. We've tested JRE 1.6.0_35 and have found no conflicts with Oracle Forms.

Your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our EBS specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.

Regards,
Steven

Posted by Steven Chan on September 04, 2012 at 07:22 AM PDT #

Steve,

Does users need to upgrade client Java version to mitigate "Oracle Security Alert for CVE-2012-4681". We are using JRE 1.6.0_17.

http://www.oracle.com/technetwork/topics/security/alert-cve-2012-4681-1835715.html

Thanks,
Rama

Posted by Rama Ari on September 11, 2012 at 02:39 AM PDT #

Rama,

I'm not permitted to discuss security issues here.

Oracle recommends that all users apply the latest available JRE 1.6 release to E-Business Suite environments. The latest available JRE 1.6 release is JRE 1.6.0_35:

https://blogs.oracle.com/stevenChan/entry/java_jre_1_6_01

Regards,
Steven

Posted by guest on September 11, 2012 at 07:52 AM PDT #

Will JRE 6 still be available on OTN after November, just not the latest version? If it is being removed, when will it be removed?

Posted by guest on October 17, 2012 at 02:42 PM PDT #

Apple's latest java 2012-006 appears to force the use of Java 7 on the Mac for applets. See http://support.apple.com/kb/HT5493. Is there any workaround to allow EBS to run on the Mac after applying 2012-006?

Posted by Nathanael on October 17, 2012 at 03:03 PM PDT #

Hello, Nathanael,

It is technically feasible to install the latest Oracle JRE plug-in on Mac OS X clients. We're testing this configuration right now. We've identified two issues; these issues are cosmetic and annoying, but will not cause data corruption.

We are working with the Java team on fixes for these two issues. We'll announce the Mac-based certification with the Oracle JRE shortly.

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.

Posted by Steven Chan on October 18, 2012 at 02:21 PM PDT #

Hello, Guest,

I'm afraid that I don't have much visibility into the Java team's policies for distributing JRE 6 via OTN. I'll look into this, but you should log a formal Service Request against the Java product if you need an authoritative answer to this one.

Regards,
Steven

Posted by Steven Chan on October 19, 2012 at 08:37 AM PDT #

Hello, readers of this thread:

I'm locking it from future comments now.

EBS customers can get a head-start on the JRE 7 certification by applying a Forms-based patch to their environments today. For details, see:

Planning Bulletin for JRE 7: What EBS Customers Can Do Today
https://blogs.oracle.com/stevenChan/entry/planning_for_jre_7

Regards,
Steven

Posted by Steven Chan on October 19, 2012 at 01:56 PM PDT #

Post a Comment:
Comments are closed for this entry.
About

Search

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