By default, Oracle Forms Application Server serves Oracle Forms applications using the built-in Jinitiator JVM. While JVM works swell with cutting edge browsers1 it pretty much crashes most of the other browsers2 and doesn’t work at all in Chrome. There are workarounds but the workarounds do not play well while working with multiple tabs.
Here’s a simple way to make the Application Server serve Oracle Forms Applications using JRE rather than the Jinitiator. Please remember to take a backup of your existing files!
Locate your formsweb.cfg file. It should be in $oracle_home/forms/server directory. Add the below lines to the section corresponding to your config= setting.
baseHTMLjinitiator=basejpi.htm jpi_download_page=https://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-142662.html jpi_classid=clsid:8AD9C840-044E-11D1-B3E9-00805F499D93 jpi_codebase=https://java.sun.com/update/1.5.0/jinstall-1_5-windows-i586.cab jpi_mimetype=application/x-java-applet;version=1.4.2
Here’s a brief explanation of each of these terms:
- jpi_classid – The ClassID of the Sun JVM to use (Internet Explorer specific). Should be set to clsid:8AD9C840-044E-11D1-B3E9-00805F499D93 for dynamic versioning or to clsid:CAFEEFAC-
- - -ABCDEFFEDCBA for static versioning
- jpi_codebase – Download location of the CAB file for the Sun JVM (IE specific)
- jpi_mimetype – JPI_MIMETYPE is a mime-type in a format like “application/x-java-applet;
= ”. For static versioning, should be set to “jpi-version”. For dynamic versioning, this should be set to “version”.
- jpi_download_page – This is the URL where Netscape/Firefox users can download the JRE.
Refer here for a detailed explanation of each of these terms. That’s about it. Reloading the application should result in the JRE kicking in, rather than Jinitiator. Also ensure any jar files that you have are digitally signed, else you will run into an warning about blocking unsigned jar files which might lead to a showstopper bug.