Oracle JInitiator enables end users to run Oracle9i AS Forms Services
applications directly within Netscape Navigator or Internet Explorer on the
Windows 2000, Windows NT4.0, and Windows XP platforms.
Oracle JInitiator is implemented as a plug-in (Netscape Navigator) or ActiveX Object (Microsoft Internet Explorer).
Oracle JInitiator allows you to specify the use of the Oracle certified Java Virtual Machine (JVM) on web clients
instead of relying on the default JVM provided by the browser.
Oracle JInitiator delivers several key benefits to enterprises deploying Oracle9iAS
Forms Services applications:
Full JDK 1.3 support: Oracle JInitiator allows enterprise developers to
develop and deploy Oracle9iAS Forms Services applications taking
full advantage of JDK 1.3 features and functionality.
Full Java Compatible support: Oracle JInitiator utilizes the latest
release of the Oracle certified JDK (OJDK) which is fully compliant with
the Java Compatibility Kit (JCK) test suite.
Easy install: Oracle JInitiator utilizes the plug-in/ActiveX Object installation
mechanism provided by the browsers to install and update itself when necessary.
Oracle JInitiator requires minimal intervention on the end users behalf.
Supports a specific version of MIME type for use in Netscape Navigator
Oracle JInitiator 1.3.1.22 only supports the following MIME type
application/x-jinit-applet;version=1.3.1.22
A version specific MIME type has been added, application/x-jinit-applet;version=1.3.1.22
which provides the administrator with the ability to explicitly
specify the Oracle JInitiator 1.3.1.22 as the version to be used.
MIME Type
Usage Notes
application/x-jinit-applet;version=1.3.1.22
Supported only in Oracle JInitiator 1.3.1.22.
The browser will only use version 1.3.1.22 and if it is not present
will direct the user to the download page for this version.
Supports a version specific CLASSID for Microsoft Internet Explorer
A new CLASSID was created for Oracle JInitiator 1.3.1.22:
clsid:CAFECAFE-0013-0001-0022-ABCDEFABCDEF
To specify the use of Oracle JInitiator 1.3.1.22 in Microsoft Internet
Explorer, the Object tag in the page must contain the CLASSID specified
above. If the objects tags do not specify the exact CLASSID for this release,
it will not be launched. If Microsoft Internet Explorer does not have
this version installed, it will download and install it for the user.
JAR file caching: Oracle JInitiator caches the downloaded JAR file on the
client-machines hard disk. Cache mechanism properties can be modified on
the client via the Oracle JInitiator control panel. The caching mechanism
uses a smart expansion algorithm to store JAR files in an uncompressed format.
This approach provides much more efficient class loading operations and
reduces application startup time dramatically.
Java security identity configuration: Oracle JInitiator automatically creates
the required Oracle identities in the Java security database and associates
the digital X509 certificates with them.
Supported OS and Browser configurations
Oracle JInitiator supports the following browser and OS configurations:
Platform
Internet Explorer 5.5*
Internet Explorer 6.0*
Netscape Navigator 4.7.x**
Windows NT
X
X
X
Windows 2000
X
X
X
* Although JInitiator 1.3.1.22 is certified on Internet Explorer 5.5/6.0. It
is in noway imply that other Oracle Java applications are certified to run on
Internet Explorer. Please consult corresponding documentation from for supported
browsers.
** Oracle JInitiator 1.3.1.22 has been shown (by both internal testing and the
absence of any customer reported issues) not to be sensitive to any particular
version of Netscape 4.7.x. It is therefore certified for use against all versions
from 4.7.x onwards. Currently we test Oracle JInitiator on Netscape 4.78 and
will continue to install and test against the latest version of Netscape 4.7.x
.
About using Oracle JInitiator
Oracle JInitiator does not replace or modify the default JVM provided by the browser. Rather, it provides an
alternative JVM via the standard plug-in architecture of the browser which allows web application developers to
specify the use of the Oracle certified JVM instead.
Oracle JInitiator is automatically downloaded to a client machine from the application server the first time
the client web browser encounters an HTML file that specifies the use of Oracle JInitiator. The installation and
updating of Oracle JInitiator is performed using the standard plug-in mechanism provided by the browser.
Oracle JInitiator installation performs the required steps to run Oracle9i
Forms applications as trusted applets in the Oracle JInitiator environment.
About using with Netscape Navigator
Oracle JInitiator leverages the Netscape Navigator plug-in architecture in order to run inside the browser in
the same way other plug-ins such as QuickTime movies or Shockwave animations operate. Using the Netscape HTML <EMBED>
tag, web application developers can specify plug-ins to be run as part of a web page. This is what makes it possible
for Oracle JInitiator to run inside the web browser with minimal user intervention.
When Navigator first encounters an HTML page that specifies the use of Oracle JInitiator, users will see a "Plug-in
Not Loaded" dialog on the HTML page, which directs the user to the Oracle JInitiator download page. Users
can then download the version of Oracle JInitiator for their operating system and install it. Once Oracle JInitiator
is installed, users must shut down Navigator, restart it, and then revisit the original HTML page. Oracle JInitiator
will then run and use the parameters in the <EMBED> tag to render the applet. The next time Navigator encounters
a web page that specifies Oracle JInitiator, Navigator will seamlessly load and run the plug-in from the local
disk, requiring no user intervention.
About using with Microsoft Internet Explorer
Oracle JInitiator leverages the Microsoft Internet Explorer extension mechanism for downloading and caching
ActiveX controls and COM components. Using the HTML <OBJECT> tag, web application developers can specify
to run ActiveX controls or COM components as part of a web page, including Oracle JInitiator.
When Internet Explorer first encounters an HTML file that has been modified to specify the use of Oracle JInitiator,
Internet Explorer will ask the user if it is okay to download an ActiveX control signed with a VeriSign digital
signature by Oracle Corporation. If the user clicks "Yes," Internet Explorer will begin downloading Oracle
JInitiator. Oracle JInitiator will then run and use its parameters in the <OBJECT> tag to render the applet.
The next time Internet Explorer encounters a web page modified to support Oracle JInitiator, Internet Explorer
will seamlessly load and run Oracle JInitiator from the local disk, requiring no user intervention.
Oracle Java Runtime Environment version
Oracle JInitiator includes a version of Oracle Java Runtime Environment (JRE), which is downloaded and installed
together with Oracle JInitiator.
Oracle JInitiator is based on JavaSoft plug-in 1.3.1, which is in turn based
on JavaSoft JDK 1.3.1.
Changes in Oracle JInitiator
Please refer to the changes file for a list of changes
between the Oracle JInitiator releases.
Copy JINIT_DOWNLOAD.HTM to your web server. Note: You must copy
JINIT_DOWNLOAD.HTM to the location that was specified within the base HTML
file.
Installing Oracle JInitiator on your server
To install Oracle JInitiator on your web server:
Place the jinit13122.exe in a directory that has a virtual mapping associated
with it. This enables client machines to download the installation executable
when required.
(optional) To install Oracle JInitiator on the server machine for testing
purposed, double-click jinit13122.EXE, then follow the installation instructions.
Installing the Oracle JInitiator on your server allows you to test and refine
your configuration before deploying your applications to customers. Note
that this is not a required step and is only required to perform local system
testing.
Adding Oracle JInitiator markup to your base HTML
file
To add Oracle JInitiator markup to your base HTML file:
This example illustrates the Oracle JInitiator markup for a Forms application.
In the example, the blue section is Microsoft
Internet Explorer-specific. The red section
is Netscape Navigator-specific. Adding each section to your base HTML file will
enable your applications to run within both Netscape and Microsoft web browsers.
For more information about the OBJECT and EMBED tags, refer to JINIT_TAGS.HTM.
Modify the link so that end users can download jinit13122.EXE. jinit13122.EXE
should already be on your web server.
Modify the text as desired.
Save your changes.
Configuring Runtime Operation of Oracle JInitiator
The runtime operation of Oracle JInitiator may be configured through the use of the Oracle JInitiator Control
Panel.
Modifying the heap size for Oracle JInitiator
Note : The default maximum heap size for Oracle JInitiator is 64 Megs. This has been set for you when you install
Oracle JInitiator.
To modify the heap size for Oracle JInitiator:
From the Start menu, choose StartSettingsControl Panel.
Then double-click the "JInitiator 1.3.1.22" icon.
Click the Basic tab.
In the Java Run Time Parameters field, specify the maximum heap size by adding a "-Xmx" parameter. For example,
specifying "-Xmx64m" sets the maximum heap size to 64 MB.
Viewing Oracle JInitiator output
To view Oracle JInitiator output, simply double-click the JInitiator icon on your Windows task bar:
This will bring up the JInitiator console.
Controlling JAR Caching Operations
The operation of the JAR caching mechanism provided by Oracle JInitiator can be controlled through the "Cache"
tab of the JInitiator Control Panel:
From the Start menu, choose StartSettingsControl Panel.
Then double-click the "JInitiator 1.3.1.22" icon.
Click the Cache tab.
You will see the following:
Here you can change the following settings:
Enable and disable JAR caching: Check or uncheck the "Enable JAR Caching" checkbox.
Erase all files from the JAR cache: Click the "Clear JAR Cache" button.
Change the JAR cache location: Type a new directory in the "Location" field, or press the folder icon to choose a directory.
Change the JAR cache size: The cache size is the maximum amount of hard disk space used by JInitiator to store cached JAR files.
You can enter a new maximum size using the Maximum field. You can enter the size as a number of bytes, KiloBytes, or MegaBytes using the
drop down list. Alternatively, you can select "Unlimited" to specify that no maximum cache size should be used. Warning: the unlimited
setting may cause your hard drive to become full.
Set the JAR cache compression level: By default, JAR files are stored in the cache with no compression. This provides optimum
performance. However, if you have limited disk space, you may choose to compress cached JAR files. This will allow more JAR files to be
stored in a given maximum cache size. Simply drag the Compression slider to the right. There are ten levels of compression, with the
highest being all the way to the right. Higher compressoin levels allow more JAR files to fit into the cache, but also decrease performance.
The Download Progress Dialog
The initial download of the JAR files used by an applet can take a significant
amount of time. Oracle JInitiator 1.3.1.22 and later contain a progress dialog
to provide feedback to the end user on the progress of these JAR file downloads.
The progress dialog appears when a user navigates to an Oracle JInitiator enabled
web page and remains on the screen until the download is complete. The progress
dialog tracks the progress both with a visual progress bar and a text based
indicator. When the download is complete, the progress dialog automatically
closes and the applet starts.
Progress Dialog User Interface
The progress dialog can be optionally configured to display the name of the product being started and a splash
screen image for the product. The configuration parameters used to control the display are discussed in the
Progress Dialog Parameters section.
The image below shows what the progress dialog appears like when it is configured to display the name of the
product being started.
The image below shows what the progress dialog appears like when it is configured to display the name and a
splash screen for the product..
The progress dialog is unobtrusive to the end user. The end user can put other windows on top of the dialog,
move the dialog, minimize it, and even close it. If the user minimizes the dialog, the title of the dialog
will be updated with the current progress. This allows the user to track the progress even with the dialog
minimized by looking at the Windows task bar:
If the user closes the progress dialog, the download will proceed and the applet will start up normally. The
end user will not see the progress information as the JAR files are downloaded.
Progress Dialog Parameters
The progress dialog is controlled by specifying parameters in the Oracle JInitiator tag in the HTML page used
to launch the applet. The parameters that are recognized by the progress dialog and their actions are listed below.
Property Name
Property Values
Description
java_showprogress
true | false
Setting this parameter to "true" enables the progress dialog.
By default, the progress dialog is not shown.
java_preloadjars
Any jar files
Preloads the jar files specified.
In order for the VM to be able to display a progress bar the VM needs to
know the size of the jar files loaded to the client, and since Forms jar
files are downloaded incrematally when ever they are needed this is the
only way for the JVM to calculate the size of the jar files. You should
only specify the jar files that initially needs to be loaded to the client.
java_appletname
Any string
Optional parameter.
Specifies the name of the product. Defaults to "Applet".
The product name is used in the titlebar of the progress dialog and is
preceded by the word "Starting". Therefore by default the progress
dialog title is "Starting Applet".
java_progressimage
The URL for the image to be used as the splash screen.
Optional parameter.
Specifies the URL to a splash screen image. The image can be
either GIF or JPG format. The image can be any size, and can be
animated. Note that the dialog will not be shown until the image
is downloaded, so the file size of the image will affect the speed with
which the dialog comes up. The image will be shown at the top of
the dialog. If the image is not as wide as the other components
in the dialog, it will be centered in the dialog and blank space will
appear to the sides of the image
java_progressjars
Comma delimited list of JAR files to track progress of.
Optional Parameter.
For backward compability. Lists the JAR files that the progress dialog
should track. If this parameter is not specified, all JAR files
in the applet tag will be tracked by the progress dialog. This parameter
is useful if you have JAR files on your ARCHIVE tag that are not loaded
at startup (that is, on-demand JAR files). Uses the same format as the
ARCHIVE tag to specify the list of the JAR files.
An Example HTML Page using the Progress Dialog
The HTML text below is an example of a HTML page that is used to launch an Oracle Forms application and which
also displays the progress dialog to track the download of the JAR file specified in the ARCHIVE tag.
Settings
