Running JInitiator on Vista Desktops

Somewhere in this now-sprawling blog is an article about using JInitiator on Vista.   Sadly, I can't find it.  I've been seeing a few troubling things popping up on the web about various JInitiator hacks, so it's time to reprise that content.

Diagram showing Forms JRE JInitiator desktop client architecture layers

It's not possible to run Oracle JInitiator 1.3 on Microsoft Vista.  Here's why:

  • Oracle JInitiator 1.3 is based on Sun's JDK 1.3
  • Sun's JDK 1.3 is incompatible with Vista.
  • Sun has desupported JDK 1.3, so they have no plans to make it Vista compatible
  • Therefore, JInitiator is fundamentally incompatible with Vista due to its JDK 1.3 dependencies

On Hacking Up JInitiator

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 Happens When Something Goes Wrong?

If you do choose to customize Oracle JInitiator 1.3, you should consider the support implications for your users.  Oracle Support and Forms Development can provide patches only for issues that can be reproduced with an unmodified version of Oracle JInitiator. 

If you encounter any issues specific to your customized version of JInitiator, Oracle's default recommendation will be to roll back to an unmodified version.

What Does Oracle Recommend for Vista?

We recommend using the native Sun Java plug-in (Java Runtime Engine) for Vista client desktops connecting to either Oracle E-Business Suite Release 11i or 12.  The native JRE client is the only certified and supported Java client for E-Business Suite desktops end-users running on Microsoft Windows.

If you haven't already started migrating your end-users to the native Sun JRE plug-in, I'd strongly recommend that you begin this process immediately.

Why Choose the Native Sun JRE over JInitiator 1.3?

Two reasons:

The elimination of Oracle JInitiator simplifies your desktop administration environment. Apps DBAs who have migrated their users to the native Sun JRE no longer have to struggle with compatibility and coexistence problems between JInitiator and other Java runtime clients on the same desktop.

Which JRE Versions Are Certified With Which Browsers?

Apps 11i is certified with the native Sun Java (JRE) plug-in. You can use any JRE release from 1.5.0_13 and higher, or 1.6.0_03 and higher. Your end-users can upgrade their JRE clients whenever Sun releases a new JRE release on either codeline -- without waiting for Oracle to certify these new JRE plug-ins with EBS 11i.

Apps 12 is certified with the native Sun Java (JRE) plug-in.  You can use any JRE relese from 1.6.0_03 and higher.  Your end-users can upgrade their JRE clients whenever Sun releases a new JRE release on either codeline -- without waiting for Oracle to certify these new JRE plug-ins with EBS 12.

The upgrade process is documented here:

Related Articles


Hi Steven,

The article you could not find is here:

You have stated very clearly that Jinitiator will not be supported on Vista as it is based on JDK1.3.

I found it by searching for Vista as a keyword instead of jinitiator

- Vikram

Posted by Vikram Das on March 24, 2009 at 11:21 AM PDT #


How are you, hope you are doing good, the trick to make jinitiator work in Vista is given in the metalink note # 553348.1 (unable To Connect To E-Business Suite On Vista) with reference to the bug # 6074498.


Posted by Jayakumar on March 24, 2009 at 01:38 PM PDT #

Hello Jay,

Thanks for the heads up on the note. I have edited the note and bug to make the situation clearer and give correct advice



Posted by Mike Shaw on March 24, 2009 at 06:22 PM PDT #


I am not seeing the changes yet that were made from metalink.


Posted by Jayakumar on March 24, 2009 at 09:48 PM PDT #

Hi, Vikram,

Thanks for chasing that article down. I *knew* I'd mentioned this at some point.


Posted by Steven Chan on March 25, 2009 at 06:30 AM PDT #

Hello Jay,

It can take a few hours to propogate changes to Metalink from the internal repository, but looks like that has gone through OK now



Posted by Mike Shaw on March 25, 2009 at 04:54 PM PDT #

Hi Steven,

As per Metalink note 789049.1, "Oracle Corporation announces the end of Error Correction Support for Oracle JInitiator version(s) 1.1.8.x on the following platform(s): Microsoft Windows version(s) All, effective 29-MAR-2010."

Usually E-Business customers have an edge over Stand Alone Oracle products as far as desupport of any Oracle Product is concerned. If it is still being supported for Stand Alone Forms, why not support it for E-Business Suite as well?

Posted by Talib Qadir on March 30, 2009 at 12:26 AM PDT #

Hi, Talib,

The Forms team has already desupported JInitiator 1.1.8 for EBS users as of December 31, 2008. This was announced in Metalink Note 472154.1 and this article:

JInitiator 1.1.8 To Be Desupported for Apps 11i -


Posted by Steven Chan on March 30, 2009 at 02:16 AM PDT #


Thanks for the reply. If I understand correctly, Jinitiator 1.1.8 will still be supported till 29-Mar-2010 as a stand alone product or the date 29-Mar-2010 a typo (per Metalink note 789049.1)?

Posted by Talib Qadir on March 30, 2009 at 03:13 AM PDT #

Hi, Talib,

Yes, that's what Note 789049.1 says. I don't think it's a typo, but then, I'm not in Forms Development and can't say for certain.

If you want to verify that officially, I'd recommend logging a formal Service Request via Metalink against the Forms product.


Posted by Steven Chan on March 30, 2009 at 03:22 AM PDT #

Install JInitiator and jre1.6.0.
copy file jvm.dll from: C:\Program Files\Java\jre1.6.0\bin\client -> to: C:\Program Files\Oracle\JInitiator\bin\hotspot

It should resolve your problem with Vista and Oracle Forms

Posted by Chapeleiro on April 19, 2009 at 07:12 PM PDT #

Hi, Chapeleiro,

As I've mentioned quite explicitly in the article above, Oracle strongly recommends *AGAINST* any modifications to JInitiator. We'd consider this kind of DLL substitution to be a customization, with all of the Support implications I've noted above.


Posted by Steven Chan on April 21, 2009 at 02:09 AM PDT #

As one of above solution I has replaced following files :

C:\Program Files\Oracle\JInitiator\bin\hotspot\jvm.dll


C:\Program Files\Java\jre6\bin\client\jvm.dll

still not working..................

IF any solution then let me inform Thanks,Regards.
Naisarg Ravi Thakor.

Posted by naisarg ravi thakor on August 15, 2010 at 02:04 PM PDT #


As I've noted several times, we do not recommend or support hacking up Jinitiator with various JRE components. You should just install the latest JRE 1.6 release instead.

Please see:

Roundup: Oracle JInitiator 1.3 Desupported for EBS Customers in July 2009


Posted by Steven Chan on August 16, 2010 at 03:51 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016