Replacing JInitiator with Sun Java Plug-in 1.5.0_13

[Oct 24, 2008 Update:  In case you missed it, you may now use any version of the native Sun Java plug-in with the E-Business Suite as long as it meets or exceeds the minimum versions that we've certified.  Also note that we've done an explicit certification with JRE 1.6.0_10 with the E-Business Suite, given that Sun's new Java architecture introduced with that JRE release.]

The native Sun Java Runtime Engine (JRE) 1.5.0_13 is now certified and Generally Available for Windows-based desktop clients accessing E-Business Suite Releases 11i and 12.

Forms Apps architecture: Logical architecture showing desktop clients running Sun JRE or Oracle JInitiator, connecting via HTTP or HTTPS to Oracle Forms running on the Application Server tier

With this certification:
  • E-Business Suite Release 11i users can use Sun's JRE 1.5.0_13 in place of Oracle Jinitator.
  • E-Business Suite Release 12 users can use the same JRE 1.5.0_13 on their desktops

  • Users running the previously-certified JRE 1.5.0_12 to access the E-Business Suite can upgrade their desktop clients to 1.5.0_13
For an overview of why you might be interested in switching your users to the Sun Java plug-in, supported architectures, prerequisites, and other deployment considerations, see:


Thank you for your update.
Just wonder if Oracle has planes to make any improvements in Java Native plug-in area (Jinit replacement).

Background of my question is based on the fact that JDK/JRE starting from 1.5 version include automatic update feature (asking end user if he want to download and install recent updates). I some environments it is almost impossible to prevent end users from doing latest updates them selfs on workstations (it is rather customer IT department problem not Apps DBA).

I see only one good solution in that context: Oracle certifies JRE plug-in with Apps in advance or at the same time then Sun release a new update.

Currently JRE 1.5 14 update in place for a while and many end users updated to that version already.

Thank you in advance for our answer,

PS I understood that Oracle has to run significant amount of test which takes time, but still this is obvious a business need for me to make improvements in certification process in order to provide even better services for us from Oracle.

Posted by Yury Velikanov on December 09, 2007 at 02:49 PM PST #

Yury,I hear you loud and clear.  For JRE releases 1.5.0_12 and 1.5.0_13, we've explicitly tested the E-Business Suite prior to allowing E-Business Suite users to run with these versions.  In the past, some JRE releases have inadvertently omitted focus-related emergency fixes packaged in other versions.  We're operating on the side of maximum caution in verifying that these fixes are now included in the mainline JRE releases right now.  Our current position is, "Trust but verify."Once we're comfortable that each successive new JRE release includes these fixes (i.e. that there's a solid track record that demonstrates the fixes won't be inadvertently omitted in, say, 1.5.0_14), then we'll make the certification requirements less restrictive.  That is, we'll be able to state, "The E-Business Suite is certified with JRE version 1.5.0_13 and higher."I hope that day to come sooner than later, for the reasons that you've outlined.Regards,Steven 

Posted by Steven Chan on December 10, 2007 at 06:18 AM PST #

Hi Steve,

Its great read your blog and also the this article.Depending on this article, I have upgraded and integrated the jinitiator with Jre 1.6 and got into troubles while swtiching between the windows.The forms are just hanging and cant even close the form on which we are working.Please the more details on this SR: 7081258.993

Kindly let me know if there is any solution to overcome this issue.

Thanks and Regards

Posted by Srawan on September 14, 2008 at 09:50 PM PDT #

Hi, Srawan,

Glad to hear that you're switching over to the native JRE, but I'm sorry to hear that you're encountering issues.

I've taken a quick look at your SR. I haven't heard of this issue before, but I'd suspect it's configuration-related. Your Support Engineer is still at the diagnostic stage and things seem to be moving along. Feel free to ping me if your SR gets bogged down in some way.


Posted by Steven Chan on September 16, 2008 at 03:16 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016