Oracle E-Business Suite Technology

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.

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".

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

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