Friday, March 7, 2008

Upgrade from Jinitiator 1.3 to Java Plugin 1.6.0.x

Lately Oracle announced the end of Error Correction Support for Jinitiator 1.3 for E-Business Suite 11i, effective July 2009.

This is the sign it’s about time to upgrade to the native Java Plug-in… :-)

Among other things, one of the main advantages of upgrading from Jinitiator to the native Java Plug-in is the prevention of conflicts between them.

This upgrade is great news to all are working with Oracle Discoverer Plus (with Java plug-in) and Oracle EBS 11i (with Jinitiator) and experiencing those conflicts.

I’ll skip all the others advantages and disadvantages of upgrading to Java Plug-in as they are well described in Steven Chan’s post - Jinitiator 1.1.8 To Be Desupported for Apps 11i and in Metalink Note: 290807.1 - Upgrading Sun JRE with Oracle Applications 11i.

So I will focus on the upgrade process itself - step by step.

I tested the upgrade on the following test environment:

  • EBS 11.5.10.2
  • Database 10.2.0.3
  • ATG Rollup 5
  • Developer 6i patchset 18
  • OS RHEL4.

Be aware that before upgrading to Java Plug-in you must upgrade to Developer 6i patchset 18 or later (currently the latest patchset is 19).

* You can use my previous post in order to Upgrading Developer 6i with Oracle Apps 11i to patchset 18.

  1. Download JRE plug-in Oracle E-Business Suite interoperability patch - 6863618
  2. Download the Sun JRE Plug-in 
    • Select Java Runtime Environment (JRE) 6 Update X (select the latest available update, currently it’s 5)
    • Select Windows offline installation, multi-language
  3. Rename the downloaded installation file jre-6_uX-windows-i586-p.exe to j2se1600x.exe
    In my case rename jre-6_u5-windows-i586-p.exe to ==>> j2se16005.exe
  4. Copy the j2se1605.exe file to $COMMON_TOP/util/jinitiator on the Apps Tier node
  5. If you are on Developer 6i patchset 18 you should apply forms patches 6195758 & 5884875.
    ** Skip this step if you are on Developer 6i patchset 19.
    • Download Patches 6195758 & 5884875
    • Apply patch 6195758
      • Stop all applications processes by adstpall.sh
      • Unzip p6195758_60827_GENERIC.zip
      • cd 6195758
      • cp -r $ORACLE_HOME/forms60/java/oracle/forms/
        handler/UICommon.class $ORACLE_HOME/forms60/java/oracle/forms/
        handler/UICommon.class.PRE_BUG6195758
      • cp -r $ORACLE_HOME/forms60/java/ oracle/forms
        /handler/ComponentItem.class $ORACLE_HOME/forms60/java/oracle/forms/
        handler/ComponentItem.class.PRE_BUG6195758
      • cp oracle/forms/handler/UICommon.class $ORACLE_HOME/forms60/java/oracle/forms/
        handler/UICommon.class
      • cp oracle/forms/handler/ComponentItem.class $ORACLE_HOME/forms60/java/oracle/forms/
        handler/ComponentItem.class
    • Apply Patch 5884875
      • Unzip p5884875_60827_GENERIC.zip
      • cd 5884875
      • cp -r $ORACLE_HOME/forms60/java/oracle/forms/engine/Main.class $ORACLE_HOME/forms60/java/oracle/forms/
        engine/Main.class.PRE_BUG5884875
      • cp -r $ORACLE_HOME/forms60/java/ oracle/forms/
        handler/AlertDialog.class $ORACLE_HOME/forms60/java/oracle/forms/
        handler/AlertDialog.class.PRE_BUG5884875
      • cp oracle/forms/engine/Main.class $ORACLE_HOME/forms60/java/oracle/forms/engine/Main.class
      • cp oracle/forms/handler/AlertDialog.class $ORACLE_HOME/forms60/java/oracle/forms/
        engine/AlertDialog.class
      • Run adadmin -> Generate Applications Files menu -> Generate product JAR files
  6. Apply the Interoperability patch 6863618
    • Make sure all applications processes are down
    • Enable maintenance mode:
      Execute adadmin -> Change Maintenance Mode (5) -> Enable Maintenance Mode (1)
    • Unzip p6863618_11i_GENERIC.zip
    • Cd 6863618
    • Run adpatch to apply patch driver u6863618.drv
    • cd [PATCH_NUMBER]/fnd/bin
    • Execute the following command where X represent the update number:
      $ txkSetPlugin.sh 1600X
      In my case:
      $ txkSetPlugin.sh 16005
    • Disable maintenance mode:
      Execute adadmin -> Change Maintenance Mode (5) -> Disable Maintenance Mode (2)
  7. Start all applications processes by adstrtall.sh
  8. Verify installation by sign in Oracle EBS and select a forms based responsibility.

For those who worry about performance, take a look at this benchmark:
Benchmark comparison test with Jinitiator 1.3.1.23 and Java Plug-in 1.5.0_05 – performance whitepaper

For more information - Note: 290807.1 - Upgrading Sun JRE with Oracle Applications 11i

Aviad

11 comments:

yusuf said...

Aviad,

Using your blog,I successfully upgraded to JRE from Jinit... Everything works fine.. any idea, when I try to access discoverer using this URL:

http://domainname:port/discwb4/html/discolaunch.htm

Java applet is not opening.. getting the following error :


oad: class oracle.disco.DiscoApplet.class not found.
java.lang.ClassNotFoundException: oracle.disco.DiscoApplet.class
at sun.applet.AppletClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadCode(Unknown Source)
at sun.applet.AppletPanel.createApplet(Unknown Source)
at sun.plugin.AppletViewer.createApplet(Unknown Source)
at sun.applet.AppletPanel.runLoader(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
basic: Exception: java.lang.ClassNotFoundException: oracle.disco.DiscoApplet.class


Tried clearing the cache also.. but doesnt help.. Any Ideas ?


Thanks
Yusuf

Aviad said...

Hi Yusuf,

Try to remove the Oracle Discoverer 4i applet from your browser by:
Open a new IE browser window -> Tools-> Internet Options -> click on Settings button -> click on View Objects -> remove all Discoverer objects.

Aviad

Kishore said...

Hello,
I upgraded from JInit to JRE 1.5.0_14 and all works well. However, I have seen a problem where, when I launch iexpense and try to create an expense, IE Crashes. However it works fine with Mozilla on the same PC.
IE version is
6.0.2900.xpsp_sp2_qfe.070227-2300

Any insight into why this is happening?

Anonymous said...

Hi, I am having a IE crash for a user on a JRE based instance when he try to create expense using iExpense. He is using IE6.
Anything I can check?
Thanks,
Kishore

Aviad said...

I'm not sure what is the problem, but try to uninstall all Java installations from this PC, reinstall the JRE 1.5.0_14 and retest the issue.

mzhaim said...

hi iam using oracle 11i business that uses jiniatator and another application that uses jre when ever i ran these two applications
simulatonously ( each in a different IE instance) every thing runs fine until i try to generate forms from the oracle application i get a run time c++ error but if i am running the oracle application by itself and try to generate forms no error occurs.
i want to know how i can run both application in ie simulatonously

mzhaim said...

hi iam using oracle 11i business that uses jiniatator and another application that uses jre when ever i ran these two applications
simulatonously ( each in a different IE instance) every thing runs fine until i try to generate forms from the oracle application i get a run time c++ error but if i am running the oracle application by itself and try to generate forms no error occurs.
i want to know how i can run both application in ie simulatonously

Aviad said...

Hi Mzhaim,

This is a very known problem of jave version conflict between Jre (probably 1.4 and above) and Jinitiator (1.1 or 1.3).

It is highly recommended to upgrade from jinitiator to native Java plug-in which will eliminate your problem.

Moreover, Check Note: 430359.1 - Internet Explorer Crashes When Forms Is Launched

Aviad

Anonymous said...

Hi,

We recently went live with Sun JRE-6 update 11.
We are currently working on 11.5.10.2 and database 9.2.0.6, Apps on Node-1 and Database on Node-2

Now the users are facing slowness when they open forms that has many fields.
Also another issue is: Alef and Lam Arabic character, as in metalink note: 731703.1.
But the Metalink Note says the issue is resolved in JRE 6 Update 11.But its still there in our case.

Did anyone face this issue or any tips to resolve it ??..

Anonymous said...

Hi, We are using JInitiator 1.1.8.16 in 11.5.9, we want to move to JRE. Is it possible?. We are using java 1.3 in server. Do we have to upgade this java also?. Please suggest

Anonymous said...

we upgrated to java plugin 6u18 using oracle forms 10g, everything works fine, except for 1 thing...on runtime when CTRL+F11 is being used sometimes the field completed that must go into the where clause, it does not, and executes a select * query, but doing the same on jinitiator environment works fine, any help to solve this situation? thanks in advance..