Page 1 of 3

Recommended Client Java Plug-in (JVM/JRE) For Discoverer Plus 10g (10.1.2) [ID 465234.1] Modified 07-SEP-2010 In this Document Purpose Scope and Application Recommended Client Java Plug-in (JVM/JRE) For Discoverer Plus 10g (10.1.2) References Type BULLETIN Status PUBLISHED

Applies to:
Oracle Discoverer - Version: 10.1.2.0.0 to 10.1.2.3 - Release: 9.0.4 to 10.1.2 Information in this document applies to any platform.

Purpose
This document explains the client-side java virtual machines (JVM) that Oracle BI Discoverer Plus supports and recommends.

Scope and Application

This is a high-level overview intended for Oracle BI Discoverer Administrators, implementors and end users. Oracle BI Discoverer Administrators or implementors will have to perform some of the configura Discoverer middle-tier server.

Recommended Client Java Plug-in (JVM/JRE) For Discoverer Plus 10g (10.1.2)
What JVM's do we currently Support? Note: This information is taken from the Oracle Business Intelligence Discoverer 10g (10.1.2) Configuration Guide with some additional updated information. The following terms are synonymous in this document: java virtual machine (JVM) java runtime environment (JRE) java plug-in java plugin

OracleBI Discoverer Plus currently supports the following default Java Virtual Machines (JVMs): Oracle JInitiator 1.3.1.(18+) Oracle/Sun Java Plug-in 1.4.2_(06+) Oracle/Sun Java Plug-in 1.5.0_(02+) Oracle/Sun Java Plug-in 1.6.0_(04+) Apple JVM 1.4.2_(05+) is required for Discoverer Plus using the Safari browser on Mac OS X (Apple now supports the standard Oracle/Sun JVM with Leopard 10.5.x and greater)

Note: As of April 17, 2008, Discoverer Development certified that Oracle/Sun JRE 1.6.0.03+ will work with Discoverer 10g 10.1.2.2 + cumulative patch 6 and higher versions. See Note 237607.1 Recommended Patch Levels For All Discoverer Versions' for Discoverer patches. If using version 1.6, we recommend 1.6.0_20 or higher See: http://www.oracle.com/technetwork/topics/security/alert-cve-2010-0886-094541.html to be in-line with Application Server 10g certifications listed on OTN and E-Business Suite certifications in Note 290807.1 for 11i and Note 393931.1 for r12. We also recommend this version due to some Oracle/Sun JRE bugs that affect the Discoverer Plus applet load times and interface performance. You can configure Oracle/Sun JRE 1.6 in the Discoverer $ORACLE_HOME/discoverer/config/configuration.xml file on the server using the following tag (all one line): JRE 1.6.0_06 Example

Note: These are just examples showing how you can configure the JVM with the minor version. You can set the minor version or family version since all Java applets are run using the higher) of the JRE software that is installed on the client machine. We recommend using the family version, see: Note 728452.1 for setting the family version details, but in summary, you can replace the with: clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA
<jvm name="sun" classid="clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA" plugin_setup="http://<machine.domain>:<port>/jpi/jre6u20.exe" version="1.6" versionie="1,6,0,mn" type="application/x-java-applet" plugin_page="http://java.com" disco_archive="disco5i.jarjar" d4o_archive="d4o_double.jarjar"/>

You would stage the Oracle/Sun JRE 1.6.0_20 executable (named jre6u20.exe in this example) in: $ORACLE_HOME/jpi/bin The original Windows 32-bit client executable downloaded from the Oracle/Sun website is:jre-6u20-windows-i586-s.exe; however, you may rename the executable to any name you like as long as executable and the plugin_setup parameter names match. You can test the manual download of the plugin by placing the plugin_setup URL directly in the client browser to ensure it is accessible. For the latest available JRE version released by Oracle/Sun, the plugin_page parameter can point to http://java.com Prior versions are found on the Oracle/Sun archive page: http://java.sun.com/products/archive/ Beta versions (which are not supported until officially released) are found at: http://java.sun.com. In some cases, you may need to test a beta version on a client machine to determine if a enhancement is in place.

Note: Additionally, if you are connecting to an SSL enabled environment using JRE 1.6.0_xx, please ensure the following parameter is checked in the 'Java Control Panel' on the desktop Control Panel -> Java -> Advanced -> Security -> 'Use SSL 2.0 compatible ClientHello format'

JRE 6 is not truly SSL 2.0 compatible. TLS 1.0 clients that support SSL Version 2.0 servers must send SSL Version 2.0 client hello messages. TLS servers should accept client hello format if they wish t 2.0 clients on the same connection port. Without this parameter checked, the Discoverer Plus applet will not launch and the following error(s) will appear in the java console:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=465234.1

28/02/2011

Page 2 of 3

javax.net.ssl.SSLException: Received fatal alert: unexpected_message at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source) at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) ...

and / or
Attempt 1. RMI protocol over https transport : Unable to accept SSL certificate from web server at https://bi-server.domain:port. Received fatal alert: unexpected_message.

Note: As of 21-MAY-2008: We have had several reports of slow performance for page rendering and exporting via the Discoverer Plus applet that occurs with JRE 1.6 and not JRE 1.5 or 1.4. these issu been related to the following bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6566201 This should be corrected in 1.6.0_10 and greater. Please see the following note for a solution: Note 747189.1 'Discoverer 10g (10.1.2) Plus Applet User Interaction Has Bad Performance With Sun Java Plug-in 1.6.0_03 or Higher'

You might want to change the JVM in the following circumstances: if you want to use a newer version of the JVM to improve performance. if a different JVM is already installed and you want to use that JVM. if you want to deploy Discoverer Plus on a non-Windows Operating System that requires a different JVM (e.g. for which Jinitiator is not available). If you want to synchronize and use the same JVM or JVM version as another java enabled application. (e.g. - Oracle E-Business Suite or Oracle Forms).

Note: If you use a different JRE, you must ensure that it is certified to work with Oracle Business Intelligence Discoverer. Generally, if a parent version of the JRE is certified (e.g. 1.5.0), then the m also certified (e.g. 1.5.0_xx). You can find pointers to the certification information here Note 233047.1 'How To Find Oracle BI Discoverer 10g and 11g Certification Information'

If Discoverer Plus users use Apple Mac OS X client machines, you must specify the Oracle/Sun Java Plug-in on the Discoverer middle tier (for more information, see Section 5.9.1, "How to specif Virtual Machine for Discoverer Plus") or use the URL parameter override described below. If Discoverer Plus uses a Unix/Linux client machine, you must specify the Oracle/Sun Java Plug-in or use the URL parameter override described below. See section 3.10, "How to start Discoverer Plus over HTTP in Netscape Navigator for the first time on a UNIX client machine"

You can specify a different JVM in one of three ways: to toggle between the Oracle/Sun Java Plug-in or Jinitiator version installed with OracleBI for all users, use Oracle Enterprise Manager (for more information, see Section 5.9.1, "How to spec Virtual Machine for Discoverer Plus"). to toggle between the Oracle/Sun Java Plug-in or Jinitiator version installed with Oracle BI for an individual user, then invoke Discoverer Plus with the following URL parameter: _jvm_name=sun _jvm_name=jinitiator For example: http://machine.domain:port/discoverer/plus?_jvm_name=jinitiator Note 395822.1 'How To Allow Discoverer Plus 10g (10.1.2) Users To Use Different JRE Plugin's (Jinitiator or Oracle/Sun)'

to choose your own or update the Oracle/Sun Java Plug-in or Jinitiator version, edit the configuration.xml file directly (for more information, see Section 5.9.2, "How to specify your own Java V Discoverer Plus") What JVM do we recommend and why? We recommend the Oracle/Sun JVM (default configuration) due to a variety of factors: The Discoverer Plus applet code is based on newer versions of the Oracle/Sun Java Development Kit (JDK); whereas, Oracle Jinitiator is based on the older Oracle/Sun 1.3 JDK. Therefore, can be incompatibilities that are not feasible to fix. In general, these usually relate to focus, pagination and rendering issues. The Oracle/Sun JRE technology is matured; therefore, we do need to provide JRE fixes in our own Jinitiator JRE (the original reason it was created). The Oracle/Sun JDK 1.3 is deprecated; therefore, we can no longer get fixes from Sun on that JDK. Oracle Jinitiator is only for the Windows operating system. The Oracle/Sun JRE is ported to multiple operating systems. The direction of Oracle is to use the Oracle/Sun JRE: E-Business Suite 11i is certified to use the Sun 1.5 and 1.6 JRE Reference: Note 290807.1 'Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i' E-Business Suite 12 does not certify Oracle Jinitiator, only the Oracle/Sun JRE/JVM Future versions of Oracle Forms (applet) and Discoverer may not certify the Oracle Jinitiator JVM. Note: Static Versioning Is Not Directly Supported With The Oracle/Sun Java Plug-In: The Oracle/Sun Java plug-in version 1.5.0_02 and later does not support static versioning by default when using Microsoft Internet Explorer. If you have multiple versions of the JRE plug desktop, the latest version installed will run.

For example: If Oracle Discoverer Plus is set up to run Oracle/Sun JRE 1.4.2.0_06 in the configuration.xml file on the server and both Oracle/Sun JRE 1.5.0_12 and JRE 1.6.0_05 are installed on the de environment will launch using JRE 1.6.0_05 rather than JRE 1.4.2.0_06

Why do we recommend disabling automatic updates for the Oracle/Sun Java Plugin? The Oracle/SunJava Plug-in is generally updated more rapidly than we can re-code,package jar files, run QA regression testing and certify for compatibility.

Generally, when third party related software is released after the production release of the Discoverer product release, certifications of this type typically occur at the next available full patchs release, depending upon the significance of the updates and timing of patch releases.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=465234.1

28/02/2011

Page 3 of 3

For example: Note 427930.1 'Discoverer Plus 10g (10.1.2) Does Not Start After Update To Oracle/Sun Java Plug-in 1.6' In this example, the Discoverer Plus applet did not load correctly due a bug in the Oracle/Sun JRE 1.6.0_01 and JRE 1.6.0_02 versions. How can we disable automatic updates for the Oracle/Sun Java Plugin? Disabling Oracle/Sun Java Plugin automatice updates is done via the Java Console For Oracle/Sun Java Plugin 1.4.x click here . For Oracle/Sun Java Plugin 1.5.x click here. For Oracle/Sun Java Plugin 1.6.x click here .

References
NOTE:395822.1 - How To Allow Discoverer Plus 10g (10.1.2) Users To Use Different JRE Plugin's (Jiniatiator or Sun) NOTE:396773.1 - MS IE Browser Crashes With 'Abnormal Program Termination or 'Register Failk' When Accessing Discoverer 10g From E-Business Suite 11i (forms) or Oracle Forms NOTE:427930.1 - Discoverer Plus 10 (10.1.2) Does Not Start After Update To Sun Java Plug-in 1.6 NOTE:579913.1 - Discoverver Plus 10g (10.1.2.2) Performance is Slow Using SUn Java Plug-In (JRE/JVM) 1.6.0_05 NOTE:728452.1 - How To Force Discoverer Plus 10g (10.1.2) To Use A Specific Sun JRE/JVM Version NOTE:747189.1 - Discoverer 10g (10.1.2) Plus Applet User Interaction Has Slow Performance With Sun Java Plug-in 1.6.0_03 or Higher

Related

Products Middleware > Business Intelligence > Discoverer > Oracle Discoverer Keywords CERTIFICATION; CONFIGURATION.XML; JRE; PLUG-IN; JINITIATOR; DISCOVERER PLUS; JAVA PLUG-IN; SUNS JAVA PLUG-IN

Back to top

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=465234.1

28/02/2011