Contents
Introduction
Thank you for downloading the Run Time Environment v 1.3.1-8 for
the Tru64™ UNIX® Operating System for the Java™
Platform (hereafter called the RTE). The RTE comprises the Java
virtual machine, the Java platform core classes, and supporting
files. It is the runtime part of the Software Development Kit (SDK)
v 1.3.1 for the Tru64 UNIX Operating System for the Java Platform
(hereafter called the SDK), but without the development tools such
as compilers and debuggers. The RTE is packaged with the Plug-in
for the Tru64 UNIX Operating System for the Java Platform software
that enables widely deployed web browsers to use the RTE to run
applets. These Release Notes provide installation instructions for
the RTE and information that may be useful for developers who want
to redistribute the RTE with their software. Also, note that the
Fast Virtual Machine (Fast VM) is the default VM. For more information
about this release, refer to the SDK
v 1.3.1-8 Release Notes.
Note: The RTE and RTE Optional kits are no longer available
as setld kits; they are simply tar kits
that when untarred deliver the contents into the current directory.
IMPORTANT: Please make sure you understand the
Copyright (copyright.html ,
installed file) and License (license.html ,
installed file) information before using this release.
Installation
Presently, this RTE v 1.3.1-8 release does not require any operating
system patches. However, the need for patches may be discovered
after this release becomes available. Therefore, HP recommends that
you check the product
page on the Web site for the latest information.
This release contains mandatory and optional sets:
Installing the RTE
To install the RTE:
Download the compressed RTE kit into the directory where you wish
to install the RTE (e.g., /tmp/java/ , where
the italicized text represents your chosen directory. Note:
This default is used throughout the release notes.) In this directory,
decompress and untar the kit:
cd /tmp/java
gunzip javajre131-8.tar.gz
tar xvf javajre131-8.tar
This creates top-level directory jre131/ , which you
can rename. Note: If you wish to include the RTE Optional
kit, wait until untarring that kit to rename the top-level directory.
Directory jre131/ now contains the files plus the following
documentation:
copyright.html
license.html
release_notes.html
In addition, the following Fast VM files are installed and part
of this kit (where /tmp/java/ represents
the directory of your choosing):
/tmp/java/jre131/lib/alpha/fast32/Xusage.txt
/tmp/java/jre131/lib/alpha/fast32/libjvm.so
/tmp/java/jre131/lib/alpha/fast64/Xusage.txt
/tmp/java/jre131/lib/alpha/fast64/libjvm.so
Using the Run Time Environment
After installing the RTE, you can run your application by invoking
the java command as follows:
/tmp/java/jre131/bin/java ...
where /tmp/java/ represents the location where
you installed the RTE kit.
Installing
the RTE Optional Kit
In the same directory where you previously installed the RTE kit,
download and untar the RTE Optional kit:
cd /tmp/java
tar xvf javajreopt131-8.tar
The optional javajreopt131-8.tar set installs the
following files in /tmp/java/jre131/lib :
Installed Files
|
|
il8n.jar
|
I18N character conversion
classes from sun.io |
font.properties.ar
|
AWT font properties for
Arabic locale |
font.properties.iw
|
AWT font properties for
Hebrew locale |
font.properties.ja
|
AWT font properties for
Japanese locale |
font.properties.ko
|
AWT font properties for
Korean locale |
font.properties.rotation |
AWT font properties for rotating text |
font.properties.th
|
AWT font properties for
Thai locale |
font.properties.zh_EUC_CN
|
AWT font properties for
Chinese locale |
font.properties.zh_HK_Big5
|
AWT font properties for
Chinese locale |
font.properties.zh_HK_EUC_TW
|
AWT font properties for
Chinese locale |
font.properties.zh_TW_Big5
|
AWT font properties for
Chinese locale |
font.properties.zh_TW_EUC_TW
|
AWT font properties for
Chinese locale |
psfont.properties.ja
|
Japanese Postscript®
printer property file |
psfontj2d.properties
|
Postscript® printer
property file for Java 2D printing |
The javajreopt131-8.tar kit installs the following
files in /tmp/java/jre131/bin and /tmp/java/jre131/bin/alpha/native_threads :
keytool
policytool
rmid
rmiregistry
tnameserv
Using the Plug-in
Plug-in v 1.3.1 enables users to run Java applets and JavaBeans™
components on web pages using the RTE as an alternative to using
the default virtual machine for Java 2 that comes with the Web browser.
It is based on the Java Plug-in 1.3.1 provided by Sun Microsystems
and contains similar functionality.
For additional information on topics such as Java Plug-in security,
using Signed Applets, JNI and the Java Plug-in, using Java Plug-in
in Intranet Environments, and how Proxy Configuration works in the
Java Plug-in, please see the Sun
Microsystems Java Plug-in 1.3 Documentation web page; the documentation
is the same for the Java Plug-in 1.3.1.
Note: You must be running Netscape Communicator 4.51 or
higher, or Mozilla 0.7 or higher.
Installing the Plug-in
Note: The following sections assume the RTE kit is installed
in the directory /tmp/java/ . You can substitute
your directory path for /tmp/java/ .
For Netscape 4.x browsers:
Set the NPX_PLUGIN_PATH environment variable to the
location of the Plug-in (the directory in which the javaplugin.so
file is located):
NPX_PLUGIN_PATH=/tmp/java/jre131/plugin/alpha/ns4
For Mozilla and Netscape 6.x browsers:
Create a symbolic link in the browser's plugins directory
to the path of the libjavaplugin_oji.so file. This
file is located at /tmp/java/jre131/plugin/alpha/ns600/libjavaplugin_oji.so .
For example:
cd ${MOZILLA}/plugins
ln -s /tmp/java/jre131/plugin/alpha/ns600/libjavaplugin_oji.so
Start your browser, or restart it if it is already running.
Restart your browser a second time. (This is a workaround to a
browser bug.)
The Plug-in Control Panel
A Plug-in Control Panel lets you change Plug-in options such as
proxies and enabling of the Java console window. It also allows
you to switch the RTE version you want to run with your Plug-in.
To run the Control Panel, enter the following command:
/tmp/java/jre131/bin/ControlPanel
Or you can use the Netscape Navigator® browser to visit the
Control Panel applet page that was installed as /tmp/java/java131/jre/bin/ControlPanel .
For example:
netscape /tmp/java/jre131/ControlPanel.html
Please refer to Sun's
Java Plug-in Control Panel web page for information about additional
features and uses of the Java Plug-in Control Panel.
Selecting the
VM to Use in the Plug-in
By default, the Fast VM is used when running the Plug-in. You can
have the Plug-in use the classic VM by defining the environment
variable JAVA_PLUGIN_CLASSIC_VM before running your
web browser.
To use the Fast VM (with 64-bit pointers), you can define the
environment variable JAVA_PLUGIN_FAST64_VM . If you
do not define this environment variable, by default the Fast VM
is invoked in 32-bit mode.
Setting both environment variables, JAVA_PLUGIN_CLASSIC_VM
and JAVA_PLUGIN_FAST64_VM , invokes the Fast VM in 64-bit
mode.
If you don't set an environment variable, the Fast VM with 32-bit
pointers is invoked by default.
Redistributing the RTE
If you redistribute the RTE, you must follow the terms of the
RTE Binary Code License agreement, which
includes these terms:
The following SDK files may be redistributed with the RTE:
-
/usr/opt/java131/bin/alpha/native_threads/javac
-
/usr/opt/java131/bin/javac
-
/usr/opt/java131/lib/tools.jar
These files include Java 2 SDK tools classes, including the classes
for the javac compiler.
Bundling the RTE
For your end users to run your software, they'll need a Java runtime
environment installed on their systems. The SDK contains a runtime
environment, of course, so your customers could use that if they
happen to have it installed. However, a better bet for most of your
end users will be the RTE, for several reasons:
-
The RTE is redistributable, unlike the SDK. The RTE
Binary Code License agreement allows you to package it with
your software. By distributing the RTE with your application,
you can ensure that your customers will have the correct version
of the runtime environment for running your software.
-
The RTE is smaller than the SDK. The RTE contains everything
your users will need to run your software, but it leaves out
the development tools and demo applets and applications that
are part of the SDK. Because the RTE is relatively small, it's
easier for you to package with your software or for your users
to download themselves from the Software
Download page.
For more information on bundling an application in a Java Archive
(JAR) file, refer to Packaging
Your Application in a JAR File on Sun's site.
When bundling the RTE with application software on Tru64 UNIX,
consider the following points:
-
HP suggests that you include the RTE files under a common directory
(<runtime-dir> ). Include all the required
files from /tmp/java/jre131/bin and /tmp/java/jre131/lib
in the bin and lib subdirectories
of <runtime-dir> , following the same directory
hierarchy and relative placement of files. The internationalization
files installed by the optional subset can be included for language
localization support.
-
HP suggests that all application-specific classes be placed
in a directory other than <runtime-dir> .
Application-specific classes can be individual .class
files, .jar files, or .zip files.
-
If native code support is required, then the native library
must be located in LD_LIBRARY_PATH . The best way
to do this is to install the native libraries in <app-dir>/lib/<sys> .
LD_LIBRARY_PATH should then be set to include these
directories.
-
The application can be invoked by using the java
command-line tool with the -cp option to specify
the application's class path. In the standard installation,
for example, the command might look like this:
/tmp/java/jre131/bin/java -cp <app-dir>/lib/app.jar <classname>
Problem Reporting
To report problems, refer to our Software
Support web page.
|