Java JRE 7 Certified with Oracle E-Business Suite

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

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

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

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

Customers can prevent this issue -- and all other JRE 7 compatibility issues -- by ensuring that they have applied the latest certified patches documented for JRE 7 configurations to their EBS application tier servers.  These are summarized here for convenience. If the requirements change over time, please check the Notes for the authoritative list of patches:

  1. Apply Forms patch 14615390 to EBS 11i environments (Note 125767.1)
  2. Apply Forms patch 14614795 to EBS 12.0 and 12.1 environments (Note 437878.1)

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

Where are the official patch requirements documented?

All patches required for ensuring full compatibility of the E-Business Suite with JRE 7 are documented in these Notes:

For EBS 11i:

For EBS 12

Prerequisites for 32-bit and 64-bit JRE certifications

JRE 1.70_10 32-bit + EBS 11.5.10.2

JRE 1.70_10 32-bit + EBS 12.0 & 12.1

JRE 1.7.0_10 64-bit + EBS 11.5.10.2

JRE 1.70_10 64-bit + EBS 12.0 & 12.1

EBS + Discoverer 11g Users

JRE 1.7.0_10 (7u10) is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

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

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and later updates on the 1.6 codeline, and from JRE 7u10 and later updates on the JRE 7 codeline.  We test all new JRE 1.6 and JRE 7 releases in parallel with the JRE development process, so all new JRE 1.6 and 7 releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

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

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

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

Java SE 6 End of Public Updates Notice

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

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

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

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

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6. These Java SE 6 updates will be made available to EBS users for the Extended Support periods documented in the Oracle Lifetime Support policy document for Oracle Applications (PDF):

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

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

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

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

No. This upgrade is highly recommended but currently remains optional. JRE 6 will be available to Windows users to run with EBS for the duration of your respective EBS Extended Support period.  Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 desktop clients. 

Coexistence of JRE 6 and JRE 7 on Windows desktops

The upgrade to JRE 7 is highly recommended for EBS users, but some users may need to run both JRE 6 and 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

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

Applying Updates to JRE 6 and JRE 7 to Windows desktops

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

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

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

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

What will Mac users need?

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

The certification of Oracle E-Business Suite with JRE 7 for Mac-based desktop clients accessing EBS Forms-based content is underway. Mac users waiting for that certification may find this article useful:

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

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

The certification of Oracle E-Business Suite with JDK 7 for EBS application tier servers on Windows, Linux, and Solaris as well as other platforms such as IBM AIX and HP-UX is planned.  Customers running platforms other than Windows, Linux, and Solaris should refer to their Java vendors's sites for more information about their support policies.

References

Related Articles


Comments:

Hello, Steven

Nice to hear it!
Is Win8 certification underway?

Cheers,
Serge

Posted by Serge on December 11, 2012 at 10:51 PM PST #

Hi Serge,

I can confirm that the certification of Windows 8 and IE10 in desktop mode with Oracle E-Business Suite 11i and R12 is currently in progress.

Regards,
Tim.

Posted by Tim Mervyn on December 12, 2012 at 09:25 AM PST #

Steven
Good to hear Java 7 is certified with 11i

1) Can my users run different JRE streams (Couple of them on Java 6 and couple of them on Java 7)
If so what CLSID needs to be in appsweb.cfg (same as before that is mentioned in note 290807.1)

sun_plugin_classid=clsid:8AD9C840-044E-11D1-B3E9-00805F499D93

By setting the above what happens if we run into Bug 14370550, what would be CLSID

Posted by guest on December 12, 2012 at 10:20 AM PST #

Hi Steven,

This is great news! I see this is the client side certification for jre 1.7.0.10. Is the server side going to be certified for use as well?

i.e.
Using Latest Java 6.0 Update With Oracle E-Business Suite Release 12 [ID 455492.1]

Thanks,
Tim

Posted by Tim Cowen on December 12, 2012 at 11:07 AM PST #

Hi,

Different users can run different JRE streams from different desktop clients. If you use the dynamic clsid (8AD9C840-044E-11D1-B3E9-00805F499D93) as you mention then you will not be affected by bug 14370550. Using this clsid means forms will launch seamlessly using the latest version of JRE that is found on the desktop client of any JRE stream.

Therefore the same EBS environment could be accessed by different users running different streams.
For example User 1 has JRE 1.6.0_37 installed, forms will launch using that JRE release.
User 2 has JRE 1.7.0_10 installed, forms will launch on the same environment using that JRE release.

Regards,
Tim.

Posted by Tim Mervyn on December 14, 2012 at 01:34 AM PST #

Hi Tim,

The certification of Java 7 on the server side for Oracle E-Business Suite is currently still in progress. Further information on this will be announced in due course.

Regards,
Tim.

Posted by Tim Mervyn on December 14, 2012 at 01:42 AM PST #

Steven,

Under the section Coexistence of JRE 6 and JRE 7 on Windows desktops, the link for doc 290801.1 goes to doc 393931.1. Also, 290801.1 should be 290807.1.

Thanks!

Richard

Posted by Richard on December 27, 2012 at 08:17 AM PST #

Richard,

You get the Proof-reader Award for the month. Thanks! Corrected.

Regards,
Steven

Posted by Steven Chan on January 07, 2013 at 01:12 PM PST #

Hi Steven

If we upgrade the Plug-In to 1.7, will Mac users still be able to work.
We have a combination of Windows and Mac in our offices.

Thanks
Pieter

Posted by Pieter on January 08, 2013 at 07:04 AM PST #

Hi Steven,
We have EBS 12.1.3 on oracle linux 64 bit, would you please let me know the CPU # that include patch 14614795 so that we can user jre7. I serached but looks so confusing to find the corrent cpu #. The database is 11.2.0.2. Thanks in advance. OAS version is 10.1.2.3

Posted by guest on January 08, 2013 at 10:28 AM PST #

Hi, Guest,

As far as I'm aware, Patch isn't 14614795 included in any CPUs. You can simply download that small patch and apply it.

Regards,
Steven

Posted by Steven Chan on January 08, 2013 at 11:53 AM PST #

Hi Pieter,

Until the certification of MAC with JRE 7 is completed it is advisable to keep MAC users on the JRE 6 stream. By controlling the JRE Plug-in version from the client you can still have both MAC and Windows users accessing the same EBS environment using different streams of JRE. Generally if you simply leave your webserver calling the JRE 6 release with the MAC users running JRE 6 and the Windows users running JRE 7 on their respective desktops then they should both still be able to connect to the environment using their desired JRE version.

If required, further information on running multiple JRE versions is available in the JRE deployment documents 290807.1 (11i) and 393931.1 (R12)

Regards,
Tim.

Posted by Tim Mervyn on January 09, 2013 at 08:09 AM PST #

Hi Steven,

There seems to be a serious vulnerability issue with all 1.7 releases up through 1.7.0_10 per CERT that was announced on the Today show. They are recommending Java be disabled since there is no work around. Now what do we do? The 1.6 tree is EOL next month.

http://www.kb.cert.org/vuls/id/625617

Thanks,
John

Posted by John Wier on January 12, 2013 at 04:50 AM PST #

Hi, John,

EBS customers will continue to have access to Java 6 updates; see

Implications of Java 6 End of Public Updates for EBS Users (Oracle E-Business Suite Technology)
https://blogs.oracle.com/stevenChan/entry/what_does_the_java_6

The guidance on JRE 7 from the Oracle Security team applies to EBS environments, also:

Security Alert for CVE-2013-0422 Released (The Oracle Software Security Assurance Blog)
https://blogs.oracle.com/security/entry/security_alert_for_cve_2013

Regards,
Steven

Posted by Steven Chan on January 14, 2013 at 08:10 AM PST #

Hi Steven.

How does the Homeland Security warning regarding JAVA affect the E-Business Suite?

Thanks.
Dave

Posted by guest on January 14, 2013 at 08:23 AM PST #

Hi, Dave,

The guidance on JRE 7 from the Oracle Security team applies to EBS environments, also:

Security Alert for CVE-2013-0422 Released (The Oracle Software Security
Assurance Blog)
https://blogs.oracle.com/security/entry/security_alert_for_cve_2013

Regards,
Steven

Posted by Steven Chan on January 14, 2013 at 08:43 AM PST #

Thanks Steven.

We are still using the Java 6 plugin - does that mean we are ok or do the warnings apply to us as well?

Thanks.
Dave

Posted by Dave on January 14, 2013 at 08:47 AM PST #

Dave,

I strongly recommend that you read the Security advisory carefully, which states:

"Oracle has just released Security Alert CVE-2012-0422 to address two vulnerabilities affecting Java in web browsers... These vulnerabilities, which only affect Oracle Java 7 versions."

Regards,
Steven

Posted by Steven Chan on January 14, 2013 at 08:51 AM PST #

Steven,

What is the timeframe for EBS R12 certification with server-side Java 7? I don't see any certification information for the EBS R12 (12.1.3)/server-side Java 7 yet.

Thanks,
Alan Wan

Posted by Alan Wan on February 04, 2013 at 08:21 AM PST #

Hi, Alan,

See the section above: "Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?"

Our JDK 7 certification for EBS servers is underway. 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.

Regards,
Steven

Posted by Steven Chan on February 04, 2013 at 10:30 AM PST #

Hello Steven,
We were able to successfully install the 14614795 patch on one of our testing environments and access Forms on that instance using two different windows clients (both using IE; one running jdk 1.6u39 and the other jdk 1.7u13).

I wanted to know if there is a way, an end-user with jdk 1.7 installed can access an environment with EBS running jdk 1.6 ?

Posted by guest on February 07, 2013 at 11:41 AM PST #

Hi,

I hope I am reading your question correctly, if not please clarify.

As I think you have already seen you can set the webserver to use JRE 6u39 which allows you to access EBS using 6u39 from one client and also allows you to access using JRE 7u13 from another client.

If you have both JRE 6u39 and 7u13 installed on a single client and try to access that same EBS environment then you will connect using JRE 6u39 on top of JRE 7u13, you will see both releases in the Java console.

Please see "Coexistence of JRE 1.7.0_10 and JRE 6 on the Desktop Client" within JRE document 393931.1.

Regards,
Tim.

Posted by Tim Mervyn on February 08, 2013 at 10:16 AM PST #

Hi Steve,

We are examining likely server/desktop set up and have been asked to establish the recommended browsers that EBusiness (11i) will work with.
I have read the Oracle document of recommended browsers ID 285218.1

Do you have had any indications in the following areas:

1) Have Oracle any indication when they will be supporting IE10 on Window 8? Is see from a response in this blog this certification process is already underway?

2) Support for MS Office - I see that there is current support for the 32 bit version of Office. Do Oracle have any known plans to certify the 64-Bit version ?

3) I notice no mention is made of Chrome as a browser, again is there been any indication that this will be supported in future?

Kind regards Amral

Posted by Amral on February 13, 2013 at 06:31 AM PST #

Hi Steve,
if we have our EBS R12 and upgrade to JRE7, what will happen to discoverer 10g, is discoverer 10g certified to use JRE 7,
i remember seeing few old ML notes where it was mentioned that Disco 10g was not going to be certified with JRE7.

thanks
Sachin

Posted by sachin on February 13, 2013 at 09:42 AM PST #

Hi, Sachin,

Premier Support for Discoverer 10g ended on Dec. 31, 2011. No Extended Support is available for that release.

Since Discoverer 10g is in Sustaining Support, there are no new certifications planned for that release. This means that JRE 7 will not be certified with Discoverer 10g.

If you need to use JRE 7, you must upgrade to Discoverer 11g. This is a fast and simple upgrade; see:

Discoverer 11.1.1.6 Certified with E-Business Suite (Oracle E-Business Suite Technology)
https://blogs.oracle.com/stevenChan/entry/discoverer_11_1_1_6

Regards,
Steven

Posted by Steven Chan on February 13, 2013 at 10:29 AM PST #

Hi, Amral,

1. We're working on our IE 10 and Windows 8 certifications right now. Is your organisation planning on deploying Win8? I haven't seen much interest from enterprises yet, so I'd be interested in hearing more about your plans.

2. We're planning to certify 64-bit versions of Microsoft Office.

3. Chrome works quite well with the E-Business Suite, but we have no current plans for formally certifying Chrome. If your organisation has plans for deploying Chrome, please drop me a line with more details.

Regards,
Steven

Posted by Steven Chan on February 13, 2013 at 10:35 AM PST #

Hi Steve.
We are at a University and I suspect most Universities operate the same way. Faculty, etc. are free to choose their platforms with guidance from IT which they usually ignore.
This means Chrome, IE10, Windows 8 etc. are all used. Not every organization is able to just deploy certain software. Pretty sure that any PC purchased now will have both Windows8 and IE10 installed.

Posted by Dave on February 13, 2013 at 11:18 AM PST #

Hi, Dave,

Thanks for insight into your situation. I understand that there are many organizations that can't centrally control their client configurations. It will be interesting to see how Win8 demand shapes up over time.

Regards,
Steven

Posted by Steven Chan on February 14, 2013 at 11:21 AM PST #

Hi Steven
Is fix for 14614795 is included in 14825718 or should I roll back 14614795 before taking 14825718 and reapply 14614795.

The change log for note 437878.1 has this information:
Removed Bundle Patch 9593176, Overlay Patch 14614795 and Patch 10081297 from oneoff patches table in Section 2.1.2.
Added latest forms bundle patch 14825718 to oneoff patches table in Section 2.1.2.

Posted by Kumar on February 17, 2013 at 05:37 PM PST #

Hi Kumar,

The JRE 7 fix within patch 14614795 is included in the latest forms bundle patch 14825718 so there is no requirement to re-apply it. Patch 14614795 does however need to be rolled back before applying the new one. See step 3.2 'Note 1' of document 437878.1. Therefore to apply the latest bundle patch:

1. Explicitly roll back patch 14614795
2. Apply the latest bundle patch 14825718

Document 437878.1 is currently being updated to make this requirement clearer.

Regards,
Tim

Posted by Tim Mervyn on February 18, 2013 at 10:24 AM PST #

Hi Tim
Thanks for the information. Thats what I thought. But when I applied 14825718 I thought the jinitiator issue (wherein when we try to open forms, it complains about jinitiator incompatability - when it should not complain about jinit because we are using jre) is fixed but I still get that error after applying patch 14825718.

- Kumar

Posted by Kumar on February 18, 2013 at 05:03 PM PST #

Hi Kumar,

Sorry you are having issues with the patch. If you have not done so already please can you regenerate the jar files with the force option set to yes and try to open forms again.

If the problem persists after this please log an SR with support and we will look into the issue properly.

Regards,
Tim.

Posted by Tim Mervyn on February 19, 2013 at 07:40 AM PST #

Hi Tim:
On further checking found that the problem is not with the patch or post steps. If we have 2 env for examples and one of them is upgraded to jre 17 and the other still uses jre 16 then you cannot launch forms in this 16 environments (FRM-92095). I think solution is to either apply 14825718 in all environments in one go or modify the java control panel runtime settings for 17 to -Djava.vendor="Sun Microsystems Inc."
The problem with applying the patches simultaneously in all the environment is obvious (control and testing)

Posted by Kumar on February 19, 2013 at 05:36 PM PST #

Hi Kumar,

That rather changes the issue. Firstly, the correct way to run JRE 7 to connect to an Oracle E-Business Suite environment requires the pre-req patching as outlined in this article. If one of you environments is not patched then you will likely see the FRM-92095 error as expected. Any other method is simply a workaround that may or may not work and is not recommended as a solution.

If you want to continue to run one environment using JRE 6 and another using JRE 7 this should not be a problem. JRE basically wants to use the latest available version it finds on a particular client. There are various ways to do this which is too big a subject to go into here but briefly:
1. Run JRE 6 on one client and JRE 7 on another.
2. For Win 7 (64-bit) run through different homes e.g. JRE 7 through IE 32-bit browser, JRE 6 through IE 64-bit browser.
3. Use the latest versions and run from the same client desktop by utilising the Security Baseline or Security Baseline minus one for the release. (Outside of this you get the added complication of pop up windows warning about old Java versions etc.)

For example JRE 7u15 and JRE 6u41 (or JRE 6u39) will coexist seamlessly together on the same client. Therefore if you have an EBS environment calling 6u41 then Java will launch JRE 6u41 on top of JRE 7u15 seamlessly. This will therefore still connect to that environment even if the JRE 7 patch is not applied as it is in effect using the 6u41 codeline.

For more information see the 'Coexistance of JRE 7 and JRE 6 on the Desktop Client' and other topics in Appendix B in the JRE notes listed at the top of this page. (290807.1 or 393931.1)

Regards,
Tim.

Posted by Tim Mervyn on February 22, 2013 at 12:17 AM PST #

Hello,

Do have any idea when EBS R12 will be certified with Microsoft Office 2013(64-bit).

Abdel.

Thanks.

Posted by guest on March 12, 2013 at 11:53 AM PDT #

Hello, Abdel,

See:

Plans for Certifying Microsoft Office 2013 with E-Business Suite
https://blogs.oracle.com/stevenChan/entry/plans_for_certifying_microsoft_office

Regards,
Steven

Posted by Steven Chan on March 12, 2013 at 12:50 PM PDT #

Can we apply the server side patch 14615390 and be ready for Java 7 push from my desktop team? Will this effect the users who have Java 6 on their laptops?

Idea is to push the server patch in April into production but my desktop team might not push the desktop java 7 update until later in the year.

Please advise whether its ok to apply the patch 14615390 irrespective of whether user has java 6 or 7 on their laptop.

Posted by guest on March 14, 2013 at 10:20 AM PDT #

Hello, Guest,

Yes.

The article above (and our documentation) states: "These patches are compatible with JRE 6 and 7, production ready, and fully-tested with the E-Business Suite. These patches may be applied immediately to all E-Business Suite environments."

Regards,
Steven

Posted by Steven Chan on March 14, 2013 at 12:45 PM PDT #

Hi Steven,

Thanks for this post...

I searched through metalink, there dont seem to be a patch for Linux x64 OS. We are currently running on EBS 12.1.3 and 11.1.0.7 DB on Red Hat Enterprise 5 x64. Will this patch be released soon for Linux x64?

Regards
Mahomed

Posted by Mahomed on April 19, 2013 at 12:01 AM PDT #

Hi, Mahomed,

I was under the impression that all of the Linux ports were released. If not, I'd recommend logging a Service Request with your port request.

Regards,
Steven

Posted by Steven Chan on April 19, 2013 at 08:43 AM PDT #

Hi Steven,

Is Java 7 certified for Oracle EBS 12.1.3?

Regards,
Kumar

Posted by kumar on June 10, 2013 at 07:21 AM PDT #

Hi, Kumar,

Yes. See:

Java (JDK) 7 Certified for E-Business Suite 12 Servers
https://blogs.oracle.com/stevenChan/entry/java_jdk_7_certified_for

Regards,
Steven

Posted by Steven Chan on June 10, 2013 at 09:43 AM PDT #

Hi Steven.
I'm trying to find Oracle JRE 6 Update 51 64 bits for Windows.

All Java SE Downloads on MOS (Note 1439822.1) only links to the 32 bit version.

Regards,
Steinar Gravdal

Posted by guest on June 19, 2013 at 06:03 AM PDT #

Hi Steinar,

All the JRE releases including the Windows 64-bit version are available through "Patch 16631640 - Oracle JDK 6 update 51" as listed in document 1439822.1.

"Patch 16631997 - Oracle JRE 6 Update 51 with Auto Update Off" is a special release of the Windows JRE 32-bit release without the Auto-Update function. This is generally used by customers that wish to be able to control when their users get the latest release rather than having them downloaded to the desktop as soon as they become available.

The Auto-Update function is not available for the 64-bit JRE hence there is no requirement for a separate release of that version.

All these Java patches are bundled with the JDK and the JRE so you simply need to extract the JRE release from the patch for use on the desktop client.

Regards,
Tim.

Posted by Tim Mervyn on June 20, 2013 at 10:58 AM PDT #

Hi Tim thanks a lot.
Got a little bit confused by the JDK name.

Got both versions now.

Regards
Steinar

Posted by Steinar on June 20, 2013 at 01:03 PM PDT #

We are having issues with the latest java version of java 7 update 45. After users upgrade to 7.45, opening forms will give an security warning: "Running applications by UNKNOWN publishers will be blocked in a future release because it si potentially unsafe and a security risk"

Users have to accept the risk each time they enter forms.

The solution is apparently to sign the ebs jar files, but we are finding it hard to find ebs-documentation how to do this.

Could you point me to the documentation needed to sign the jar files?

I also think this should be apart of document "Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12" 393931.1

best regards,
Sturla Thor

Posted by Sturla on October 17, 2013 at 08:06 AM PDT #

Hi Sturla,

We have just published a new version of the Enhanced Jar Signing document that uptakes a number of changes and enhancements to this process.

Please see MOS Document 1591073.1 titled, 'Enhanced Jar Signing for Oracle E-Business Suite'.

Hopefully this will provide you with the answers you require.

Posted by Tim Mervyn on October 18, 2013 at 09:29 AM PDT #

The JDK and JRE upgrade is turning out to be a source of constant confusion to me since I have not handled this before.

Here's what's happened.

This past weekend, I upgraded our forms and reports stack to (what I thought was) the latest/greatest version following note 437878.1. Just now I find out that this note has already been superceeded on Oct 3, 2013. This upgrade (as previously mentioned) was in prep for a JDK/JRE upgrade to the 1.7.0_40 code level.

On this blog and on the forums, I've read that the JRE upgrade is for windows clients and the JDK is for the APP tier guests.

Is this a true statement or partially true?????

However on reading Note 393931.1, there is a portion in Section 3 that details how to run the JRE upgrade script using txkSetPlugin.sh in $FND_TOP/bin.

What JRE upgrade script is being referred to here? I am confused. The 1.7.0_45 upgrade to the desktops was pushed out this past week without any warning to the DBA group or to the user community. As a result, everyone is seeing the heightened level of security being enforced witgh unsigned fndforms.jar files. Now that these upgrades are already in force, I seem to have to work my way through Notes 1591073.1 and 1467892.1.

With my not having completed the steps detailed in Section 3 of Note 393931.1, can this be done after the fact?

Can someone please clarify clearly, what I need to do in my current situation -

a) where our desktops have been upgraded to 1.7.0_45 and no corresponding upgrade scripts have been run on the APP tier guests

b) where my intent is to upgrade JDK on the APP tier guests using note 1467892.1

Oracle Support provides information but never seems to answer my questions (maybe I am not phrasing them correctly).

Thank you.

Posted by Joseph Mathew on October 21, 2013 at 12:45 PM PDT #

Joseph,

I'm sorry that you're finding this confusing. Your desktop administrators should check with your EBS system administrators before upgrading Windows operating system versions, Office versions, IE, Firefox, and JRE clients.

"JRE" upgrades are applied to Windows desktop clients. "JDK" upgrades are applied to EBS application tier servers.

You need to modify your EBS configuration on the application tier to match which version of the JRE you've deployed on the desktop tier (Note 393931.1).

You also need to sign your JAR files to avoid that annoying warning message (Note 1591073.1).

You do NOT need to upgrade JDK 6 to 7 on your EBS application tier (Note 1467892.1) just to make it work with JRE 7 on the desktop tier. In other words, JRE 7 clients will work with EBS application tiers running JDK 6.

You can complete Notes 393931.1 and 1591073.1 after your desktop clients have been upgraded to JRE 1.7. The only downside of doing this afterwards is that your end-users will have see the warning until you've signed your JAR files.

If you forward your Service Request number, I can help ensure that Support is communicating the requirements clearly.

Regards,
Steven

Posted by Steven Chan on October 22, 2013 at 09:16 AM PDT #

Hi ,
we are planing to upgrade our EBS R12 Java plugins to JRE 7 , and I want to know whether its also certified with Discoverer Plus which currently runs of the existing Java 6 build 1.6.0_30 . we have Discoverer 10g

Thanks

Posted by Ahmed on October 22, 2013 at 10:47 AM PDT #

Hi, Ahmed,

EBS 12 + JRE 7 + Discoverer 11g are certified together.

Discoverer 10g is not. Premier Support for Discoverer 10g ended in Dec. 2011 and there is no Extended Support available. You should upgrade to Discoverer 11g as soon as you can.

See this article for details about Discoverer prerequisites:

Java JRE 1.7.0_45 Certified with Oracle E-Business Suite
https://blogs.oracle.com/stevenChan/entry/java_jre_1_7_07

Regards,
Steven

Posted by Steven Chan on October 23, 2013 at 10:13 AM PDT #

I have an SR open (SR 3-8071745298) for issues arising from Note 393931.1. This is prior to following Note 1591073.1 for signing the JAR files.

Can you please help?

Thanks

Posted by Joseph Mathew on November 11, 2013 at 11:56 AM PST #

Joseph,

I'm sorry that you're still encountering issues with this. We'll follow up directly with the Support Engineer assigned to your SR; please monitor your SR for updates.

In addition, I've contacted Scott Mitchell, your Oracle account manager, with a suggestion that some skilled Oracle DBAs drop in to give you some on-site help to get through this.

Regards,
Steven

Posted by Steven Chan on November 12, 2013 at 09:39 AM PST #

Hi,

Very informative article indeed.

Is Oracle EBS certified to work in Chrome OS? Whats the certification plan for this OS?

Appreciate your usual quick response

Regards

Posted by guest on November 19, 2013 at 12:30 AM PST #

Hi, Guest,

Please drop me an email with details about your organization's plans for deploying Chrome. See:

Plans for Certifying Google Chrome with E-Business Suite
https://blogs.oracle.com/stevenChan/entry/plans_for_certifying_google_chrome

Regards,
Steven

Posted by Steven Chan on November 19, 2013 at 09:25 AM PST #

Hi Steve,

I successfully tested java 7 (update 45) interop with 12.1.3 with mozilla and IE 10 on windows desktop. The instance i prepared to conduct this test was a vision demo instance. When i am trying it in one of our development instnace which has been refreshed from our production,facing many issues, though, i follwed all the steps which were working on the vision demo. Do we have any special considerations for the environment where SSL is enabled...if yes, appreciate if you mention some road map/concrete document...meanwhile, working with the support!:)

kind regards,

Rahul

Posted by guest on December 06, 2013 at 05:26 AM PST #

Hi, Rahul,

SSL enabled on the EBS server-side should be transparent to Windows desktop clients. Good luck with your SR. Feel free to let us know if that gets stuck for some reason.

Regards,
Steven

Posted by guest on December 09, 2013 at 08:38 AM PST #

Hey Steve,

That is right!, successfully tested 12.1.3 oracle instance forms on JRE 7up45 on windows 7, RHEL 6 and Mac machines. It was little tricky on RHEL 6, since,unfortunately, it has not been supported as a client desktop for oracle applications officially. Sincere thanks for your comments!

Kind regards,

Rahul

Posted by guest on December 20, 2013 at 02:57 AM PST #

Hi Steve,

Earlier we run our application on jre6 and oracle forms 6i. Recently the desktop users are blocked after upgrading to JRE7. Could you please provide me the details how to come over with this issue.

Regards
Ravi

Posted by Ravi on March 14, 2014 at 09:09 AM PDT #

Hi, Ravi,

I'm sorry to hear that you've encountered an issue with this.

We can provide general conceptual guidance here, but I'm afraid that this blog isn't the best place to get technical support for specific issues like the one that you're working through.

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

Regards,
Steven

Posted by Steven Chan on March 14, 2014 at 10:20 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

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