If the user does not have any JRE installed on the client PC, then the JRE installed be what you have configured with the plugin_setup parameter; therefore, we would recommend that you stage the latest minor version within the JRE family.

* For 1.5, it will be 1.5.0_16 (http://java.sun.com/javase/downloads/index_jdk5.jsp).

This would require the Discoverer Administrator to:

* Download the latest jre family Windows executable you plan to use on the Windows clients
* copy or ftp (binary) the executable to the Discoverer middle-tier server at: $ORACLE_HOME/jpi/bin/
You may name it whatever you wish, for example: jre142u18.exe or jre150u16.exe
* Update the plugin_setup=”http://biserver.domain:7779/jpi/jre5u16.exe” (in the file configuration.xml), making sure the executable names match

” <——— end of Oracle quote.

Tested it by putting the Sun in the URL:

_jvm_name=sun

_jvm_name=jinitiator

For example, http://machine.domain:port/discoverer/plus?_jvm_name=jinitia

But there’s an issue… Oracle Discoverer – Version: 10.1.2.48.18 to 10.1.2.54.25 gives a problem with SSL and a proxy server:

If the Sun JRE is manually installed on the client PC and the java console settings are changed to uncheck the box for “use browser settings” under the Proxy tab, Plus will start and no errors are encountered. ”

<———– End of Oracle quote.

– Disabled also the automatic Java update. This is explained on the Sun-site here .

Doc ID: 728452.1 – How To Force Discoverer Plus 10g (10.1.2) To Use A Specific Sun JRE/JVM Version

Doc ID: 395822.1 – How To Allow Discoverer Plus 10g (10.1.2) Users To Use Different JRE Plugin’s (Jinitiator or Sun)