Apps 11i Jinitiator Conflicts with Other Java Clients for Discoverer

Today we'll take a short breather from OpenWorld coverage, since I'm still doggedly plowing through what seems like a terabyte's worth of Powerpoint presentations.


If you're still debating the value of participating in our Early Adopter Program for replacing Oracle's Jinitiator with the native Sun Java plug-in for your E-Business Suite users, here's another possible conflict scenario with Oracle Business Intelligence 10g that's recently been uncovered.

If you have both of the following combinations in your environment:
  1. E-Business Suite Release 11i configured with Jinitiator 1.3.x
  2. Discoverer 10g 10.1.2 configured with Sun Java 1.4.x or 1.5.x
Then you may encounter conflicts between the Java Virtual Machines for those two configurations.  These conflicts will trigger one or both of the following errors:
  • 'Runtime Error! Program: C:Program FilesInternet Exploreriexplore.exe abnormal program termination'
  • "Register Failk"
If you run into this situation, Metalink Note 396773.1 lists a number of possible workarounds.  It may also be worth looking into our Early Adopter Program, as well, to see if that configuration eliminates the conflict in a less-painful manner than the workarounds.

Related

Comments:

The Register Failk preceeding a crash also occurs if you use a Firefox extension (Adblock) and launch the professional interface. I set up a separate profile for firefox that does not use this extension when I want to use Apps.

Posted by Sunil Desai on November 03, 2006 at 09:47 AM PST #

Sunil,

A smart idea.

Oracle does its QA testing with no Firefox extensions installed (other than those that come when you install Firefox), so strictly speaking, a properly supported configuration would require the same, although this is a little unrealistic.

As a general rule of thumb, browser extensions should be treated as customizations. If you encounter any kind of problem with an Oracle product, you should disable or remove the customization (in this case, the extensions) and try again before reporting the problem.

My advice is that most extensions aren't likely to cause a problem, but anything that may interfere with an application's HTTP input or output, either by modifying page contents or intercepting requests at the HTTP level, should be thoroughly tested before using in a production environment. Greasemonkey and AdBlock are probably the two biggest ones to watch for.

From my experience, AdBlock tends to cause problems with many sites and applications (not just EBS), because it uses expression-based rules to block entire HTTP calls. I suspect the problem here is an overaggressive rule that is preventing a crucial JAR file or JavaScript library from being downloaded.

Unfortunately, AdBlock does not have a whitelist feature, so there's no way to tell it that expression matches for certain sites are actually okay. There are many standalone proxy servers and ad blockers that do support this, and while I can't *recommend* any of these in conjunction with E-Business Suite, I can say that these are probably a better choice for this type of "customization".

Posted by Keith M. Swartz on November 03, 2006 at 10:05 AM PST #

Steven,
We are on 11.5.10.2 RUP4 and currently use the standard Discoverer 4i server. I am migrating to the 10.1.2.0.2 10gAS Discoverer version in its own ORACLE_HOME. Our 11.5.10.2 instance uses JInitiator 1.3.1.21. I noticed that 10.1.2.0.2 Discoverer ships with 1.2.1.24. I know I should not have multiple JInitiator version. In a perfect world I would upgrade both to 1.3.1.26 and be done with it, but management does not want to deploy a new JInitiator company wide again at this time. I know I could use the Sun Plug-in, but I read your conflict notice so I can't do this. Can I use JInitiator 1.3.1.21 for both?
Your recommendation is highly appreciated.
Thanks,
Chris Bittakis

Posted by Chris Bittakis on December 04, 2006 at 09:43 AM PST #

Chris,If Discoverer 10g comes with one version of JInitiator, and E-Business Suite comes with another, the general strategy is to use the highest common denominator.  My quick check of the Discoverer 10.1.2.0.2 BI documentation indicates that the minimum requirement -- at least for Solaris and Windows -- is JInitiator 1.3.1.17.Since your Apps 11i environment uses JInitiator 1.3.1.21, this should theoretically work with Discoverer 10g.  That said, there may be platform-specific wrinkles, so the safest next step for you would be to log an SR (I know, I know -- that's a pain; but it's worth it, in this case).   In your SR, ask the BI Support Engineer to confirm that JInitiator 1.3.1.21 is certified with your version of Discoverer 10g for your platform.Best of luck with that; let me know how this works out for you.Regards,Steven 

Posted by Steven Chan on December 05, 2006 at 07:11 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today