I have seen the numerous posts that explain that BO XI r2 does not support Java runtime Environment 1.6. My problem is that one of our applications has to be upgraded and the upgrade incorporates Java 1.6.
Does anyone know when a patch or hot fix will be released to support Java 1.6?
Alternatively, does anyone know if there is a way to force the Web Intelligence report panel to use a specific version e.g Java 1.5?
Under windows you are in a bad place as it always load the latest version of the Java plug-in into the browser. You have to de-install 6, and turn off auto-update.
Other operating systems (Linux, Solaris) don’t use this “trick” and you can just install the correct .so file in the plugins directory.
A general rule of thumb, you should ALWAYS turn off any auto-update of anything. You do not want things changed automatically without your knowledge. Instead, set it to prompt you for update.
I am not a big fan of M$, but in this case, it is a user error for not configurating correctly.
but please let me try and explain my problem a little further, I realise that Web Intelligence does not work with Java RE 1.6.
We have another production system (lets call it System A) that we use to capture and augment our information, and system A requires Java RE 1.6 to be installed. The problem here is that most of our users need both WebIntelligence and System A to be running on their PCÂ’s. Clearly there will be a conflict between the WebIntelligence requirement of Java RE 1.5 and System AÂ’s requirements Java RE 1.6. WhatÂ’s more is that the developers of system A say that they can force the program to run a specific version of Java (Java RE 1.6).
My first question is, is there a way that Web Intelligence can specifically be forced to open version 1.5 of Java RE?
If not, my second question is, when is BO going to bring out a Patch or Hot Fix or Service Pack to be able to use Java RE 1.6? IÂ’ve been told that there are significant changes to the Run Time environment that could improve performance when using it, so it would be beneficial for the BO team to investigate thisÂ…
What you could do is write some batch files/shell scripts (depending on OS your running for desktops) that changes the JAVA_HOME environment varialbe then calls the application. For instance you could have a batch file/shell script that sets JAVA_HOME to C:\jdk1.6.0 and then runs System A. Then a seperate one that sets JAVA_HOME to C:\jdk1.5.0 and runs Web Inteligence. I have done this before with shell scripts on Linux desktops and it works just fine. Note: I wasn’t doing this with BO but with other applications - some that were JDK 1.4 and some that were JDK 1.5. It esentially “isolates” the application to that JDK version when it’s running. But you have to install the Sun JDK’s to do this. I would think this should work simarly in Windows with a batch file.
I think there is a way to solve your problem provided your System A does not use browser(IE).
I ran into this problem few years back. Here are my thoughts about this issue.
We can point a specific JRE version to be used by the browser ( hence Webi )eventhough there are multiple versions of JREs installed on a given PC.
This is through registry moidfication. I can’t remember exactly now , I think its HKEY local machine - sofware- Javasoft.
But if your other system(System A) also uses browser to access its server then this solution is of no use to you.
If you are still experiencing this issue, let me know I will try to spend some more time recollecting what I have done before.
Thanks for your reply, it seems as though we might have to revert to changing the registery. The other option seems to be loading a different browser e.g. Mozilla and using it to specifically run Infoview and Webi.
Please can you provide some more info about which key’s I have to change in the windows registry to get the browser to use Java RE 1.5 or lower while another Java application can take advantage of the version 6 on the same PC.
(BOB member since 2006-10-10)
(BOB member since 2007-05-16)
(BOB member since 2004-01-16)
(BOB member since 2003-12-04)
(BOB member since 2007-02-26)
(BOB member since 2004-01-09)