Native Sun Plug-In to Replace Jinitiator in E-Business Suite Release 12

E-Business Suite Release 12 will replace Oracle JInitiator with the native Sun Java2 Standard Edition (J2SE).

[More cheering from Oracle Apps DBAs]

As most of you know, Oracle JInitiator is an authorised version of Sun Microsystems' Java2 Standard Edition with some specific fixes required to support Oracle Forms.  JInitiator is currently required to run Oracle Forms in the E-Business Suite Release 11i, although we're running an Early Adopter Program that's evaluating the feasibility of eliminating this requirement for Release 11i.

Oracle JInitiator will no longer be required to run Oracle Forms in E-Business Suite Release 12.  Oracle Forms in Release 12 will run directly in the native Sun Java2 Standard Edition plug-in.  This will be our standard configuration for Release 12.

Related Articles:

The above is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.



Stop! You're giving too much away, too quickly! You won't have anything left to talk about when Release 12 does come out!

Seriously, though, I did want to clarify one thing. Oracle JInitiator is not an "extended" version of Java2 SE, and does not include any extensions. What it does contain is bug fixes -- some provided by Sun, and backported from later J2SE versions, and some provided by Oracle and given to Sun, but not yet incorporated into any shipping version of Java. Strictly speaking, it is fully compatible with any other JVM, except that most other JVMs (certainly older ones, not so much the newer ones that are part of the Early Adopter Program Steven mentioned) may expose bugs in Oracle Forms code.

We really can't help it that Oracle Forms was just that much ahead of its time...or at least Java's time. :-)

Happy blogging,

Keith M Swartz
Sr. Architect, Oracle Applications Technology Group

Posted by Keith M. Swartz on April 27, 2006 at 07:37 PM PDT #

Ah, yes, poor wording on my part. Thanks for the clarification, Keith. I've updated the original post appropriately.


Posted by Steven Chan on April 28, 2006 at 03:06 AM PDT #

Dear Steven,

Thank you for a wonderful overview of what lies ahead for some of us!

You mention Jinitator will not be required with 12i, does that mean it will no longer be supported/cannot be used? The reason I ask is that we have a large user base and each desktop has jinitator installed on it. Switching to a new component will require deinstalling jinitator from desktops and installing the new J2SE plugin.

Please advise.

best wishes,

Mo Abba

Posted by Mo Abba on May 06, 2006 at 07:46 PM PDT #

Mo, thanks for the feedback; glad you're enjoying these sneak peeks into the future.We don't have plans to test Release 12 comprehensively with JInitiator since we'll be focussing our QA efforts on the native Sun J2SE plug-in instead.  It's possible that we'll do some spot tests with specific products, but we won't be able to state that the former combination is certified or recommended.So, for Release 12, the use of JInitiator will likely fall into that grey area which governs all uncertified configurations for the E-Business Suite.  Some (as-yet unknown) version of Jinitiator will likely work with Release 12 and you'll need to figure out how to custom-configure your system to use it, but we will officially recommend that all customers use the native Sun J2SE plug-in.Regards,Steven

Posted by Steven Chan on May 07, 2006 at 03:48 AM PDT #

Steven, In SR #6257801.992 the support analyst points to patch #5624390 as the place to get the certified J2SE plugin for Release 12 - however I can't find that patch on Metalink. Just as an fyi, last week I received a new laptop and logged into Release 12 (first Oracle apps logon - no Oracle entries in registry) and it prompted me to Sun website where it downloaded version 5.10 - then it prompted to download 5.11 since that's the latest out from Sun. The Sun 5.10 plugin seems to be working fine - but realize it may not meet certification - can you help reduce some of the confusion here? Thanks Chuck

Posted by Chuck Kennedy on April 06, 2007 at 03:12 AM PDT #

Hi, Chuck,I saw your excellent article in the latest Solution Beacon newsletter alluding to this, too.  The short answer is that the only certified source for Release 12's certified J2SE plug-in is via the Release 12 Rapid Install.  Other Sun J2SE releases aren't certified yet, for reasons I guess I'll be forced to discuss in an upcoming blog article.  Stay tuned (and thanks for posting your comment here, which will prod me to put this article together in a few days).Regards,Steven 

Posted by Steven Chan on April 06, 2007 at 08:59 AM PDT #

Steven, First and foremost, it was most awesome to meet you at Collaborate 07 - you are a most gracious person, even more so considering the responsibilities you carry - thank you for taking the time out of your busy schedule. Did have one followup question to the Release 12 certified J2SE plugin in relation to the management of our Vision instances at Solution Beacon. We're thinking we might want to make the certified version from the Rapid Install available from our Vision website for download, rather than have the client rollover to the Sun website - just trying to figure out the best way to manage the certified J2SE for our Vision instance users and would appreciate your guidance. Thank you and highest regards, Chuck Kennedy

Posted by Chuck Kennedy on April 24, 2007 at 12:46 AM PDT #

Hi, Chuck,It was good to meet you and the rest of the Solution Beacon team at Collaborate, too.From a deployment perspective, R12 sysadmins should be deploying only the special version of the JRE 1.5 that came on the Rapid Install.  I'm not sure I understand your comment about the "client rollover to the Sun website."  Can you elaborate on that?Regards,Steven 

Posted by Steven Chan on April 24, 2007 at 05:46 AM PDT #


What started this post was the essence of the newsletter article from last month. When I logged into Release 12 with a brand new laptop, the apps logon went to the SUN website and pulled in their 5.10 Java plugin which I understand is not certified. We have a self-registration form where people can register to get an appsid and password for our Release 12 Vision instance - from an administrative perspective, looks like we should make the special version of JRE 1.5 from the Rapid Install CD available on our self-registration page for download, else their initial Release 12 logon may take them to the Sun website for a non-certified version. Thanks Chuck

Posted by Chuck Kennedy on April 26, 2007 at 12:53 AM PDT #

Got it, Chuck.  I'm looking into whether there are any deployment options here, other than just staging the special Sun JRE that was part of the R12 distribution.  I'll post more details as soon as possible.Regards,Steven 

Posted by Steven Chan on April 26, 2007 at 05:30 AM PDT #

Chuck,It looks like the best option would be to stage the R12 JRE somewhere on your website.  Users of the Solution Beacon R12 Vision instance would then need to run that JRE rather than Sun's 1.5.0_11.  Another alternative is to ask your users to implement the Windows Registry changes described in the "Static Versioning for MSIE users" section of unpublished Note 393931.1, which I'll send you privately by email.  However, that's suboptimal, since you don't have any control over the Solution Beacon guest users of your environment.Regards,Steven

Posted by Steven Chan on April 27, 2007 at 07:32 AM PDT #


i am running R12 on linux 64bit amd, i want to use the j2se plugin to run the client on the same BOX.

1)is it possible to run client on same box if so what version of J2se for linux 64 bit ????

2)metalink for configuration of the same.

thanks for help in advance

Posted by Raj on December 21, 2007 at 05:24 PM PST #

can you run R12 client from on linux as4 64bit.
using J2se.
and metalink notes for configuration for the same.

Posted by Raj on December 21, 2007 at 05:26 PM PST #

Raj, I'm afraid that this isn't a certified or supported configuration.  Our plans for Linux desktop certifications with the E-Business Suite are on hold; see this article:Linux Clients for the E-Business Suite - can't comment on the feasibility of this configuration since we haven't performed any tests internally with it.  You will find anecdotal comments from several readers of this blog who've tried it themselves, with varying success. Your mileage will vary.Regards,Steven 

Posted by Steven Chan on December 24, 2007 at 03:06 AM PST #

I have question if you experts could ansewer?
Do we need to install j2se plug-in separately to use R12?
But what i know is that it will be installed first time user access the form , from any machine (xp, linux etc.)

am i correct?

Posted by ibnhussain on February 01, 2009 at 01:05 PM PST #

Hello ibnhussain,

If an appropriate version of J2EE is not available already on the client, then it will be prompted for and downloaded when accessing forms for the first time.

You can review Note 389422.1 "Recommended Browsers for Oracle E-Business Suite Release 12" and Note 393931.1 "Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12" for more information. Linux is not a certified platform for the client with EBusiness Suite

Hope that answers your question


Mike Shaw

Posted by Mike Shaw on February 01, 2009 at 04:11 PM PST #

We have Sun JRE V1.6.0_11 installed on XP desktop clients.
When a user uses R12 forms - application tries to install V1.6.0_7 - which is the version installed on the server.
Why won't it use the later installed version on the client ?

Please advise,


Posted by Mindy on July 27, 2010 at 12:00 AM PDT #

Hi, Mindy,

It sounds like you have configured your end-users' desktops to use Static Versioning with IE (Firefox behaves differently). If you configure a desktop to use Non-Static Versioning, it will use the latest JRE version installed on the desktop (overriding the EBS requested version).

See Note 393931.1 Appendix A, "Static vs Non-Static Versioning and Set Up Options" for more details about these different configuration methods.

You should also pay close attention to what happens after JRE 1.6.0_10 and higher (discussed later in the same appendix), since the behaviour changes substantively with those releases.


Posted by Steven Chan on July 27, 2010 at 04:31 AM PDT #

Hi Steven,

Thank you for the info.

I've been strugging to find where we have configured IE to use Static Versioning. However, having done some further troubleshooting I've established that the scenario reported is not occurring consistently.

Scenario 1 :
PC has both 1.6.0_7 and 1.6.0_11 installed - user is able to run R12 forms - no problems.
In other cases the R12 forms will hang. I disable the next generation plug-in fix by amending registry [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Plug-in\1.6.0_11] "UseNewJavaPlugin"=dword:00000000 and running C:\Program Files\Java\jre6\bin\ssvagent.exe -high -jpisetup -old. The user is now able to run R12 forms.

Scenaio 2 :
PC has 1.60_11 - some users can access R12 forms without any problems.
In some cases R12 tries to install V1.6.0_7 and hits the insufficient privlidges problem as the user does not have admin rights.
In other cases the R12 forms will hang - I apply the disable next gereration plug-in fix above and the user can run the R12 forms.

I'm starting to wonder if there is something in the users profile that is dictating which JRE is used ?

This is my first encounter with Oracle applications and Java - any help is most appreciated.


Posted by Mindy on July 29, 2010 at 05:19 PM PDT #

Hi, Mindy,

It sounds like each of your desktops are configured differently. If that's the case, there may be different issues going with each of them, too. This is one of the primary downsides of having desktops that are not centrally administered to a single consistent configuration.

I'd like to get someone in our team to help you work through this systematically. Please log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our ATG JRE specialists engaged; please feel free to forward your Service Request number to me.


Posted by Steven Chan on July 29, 2010 at 11:21 PM PDT #

Thanks Steve.

I will log a formal request.

Best Regards,

Posted by Mindy on July 30, 2010 at 12:00 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016