Sun JRE instead of Jinitiator: Discoverer

The whole company has to move in the end to Sun Java  instead of Jinitiator (also based on Sun Java by the way), so also the Discoverer – application.

Changed the client from Jinitatior 1.3.2 to Sun 5, update 6 (5.0.6).  You can download it here by the way.

As of this release you can no longer specify the exact JRE release. Only configure the ‘Family CLSID’.

Configure Discoverer, middle-tier:
1. cd $ORACLE_HOME/discoverer/config
2. backup configuration.xml
3. edit configuration.xml
4. comment out the original Sun JRE tag using the comment tags:
For example:
<!– <jvm name=”sun” classid=”clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA” plugin_setup=”http://biserver.domain:7779/jpi/j2re.exe” version=”1.4.2″ versionie=”1,4,2,mn” type=”application/x-java-applet” plugin_page=”” disco_archive=”disco5i.jarjar” d4o_archive=”d4o_double.jarjar”/> –>

5. Insert the new Sun JRE tag:
For example:
<jvm name=”sun” classid=”clsid:CAFEEFAC-0015-0000-FFFF-ABCDEFFEDCBA” plugin_setup=”http://biserver.domain:7779/jpi/jre5u16.exe” version=”1.5″ versionie=”1,5,0,mn” type=”application/x-java-applet” plugin_page=”” disco_archive=”disco5i.jarjar” d4o_archive=”d4o_double.jarjar”/>

Table of the Sun version versus the Family CLSID’s:

1.4.2     : clsid:CAFEEFAC-0014-0002-FFFF-ABCDEFFEDCBA
5.0        : clsid:CAFEEFAC-0015-0000-FFFF-ABCDEFFEDCBA
6.0        : clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA

Oracle quote ———>:

“The behavior will be as follows:

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 (

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: to  gives a problem with SSL and a proxy server:

Oracle  quote: ———-> “Discoverer Plus connections fail when using Sun JRE 1.5+ with the browser internet options set to use proxy server and default java console settings. For example, if the browser internet options  -> Connections -> LAN Settings -> Use proxy server is checked, Discoverer Plus fails to start with Sun JRE 1.5.

If the browser internet settings -> Connections -> LAN Settings -> Use proxy server is unchecked,
Discoverer Plus will start successfully with Sun JRE 1.5.

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)

Doc ID: 437439.1 – Plus in SSL Mode with Proxy Server Fails with Unexpected Response 403 from Proxy Error

By | 2009-09-08T10:22:29+00:00 September 8th, 2009|Categories: App. Server|Tags: , , |0 Comments

About the Author:

Leave A Comment