Release Notes

Contents

• » Introduction
• » Installing the RTE
• » Using the Run Time Environment
• » Redistributing the RTE
• » Bundling the RTE

Introduction

These release notes contain installation instructions and other information specific to the Run Time Environment (RTE) v 1.4.2-4 for the OpenVMS I64 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 Software Development Kit (SDK) v 1.4.2 for the OpenVMS I64 Operating System for the Java Platform (hereafter called the SDK), but without the development tools such as compilers and debuggers. 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 HotSpot Virtual Machine is included with the RTE kit. For more information about this release, refer to the SDK v 1.4.2-4 Release Notes and the SDK v 1.4.x User Guide.

Note: We expect to provide updates to this RTE v 1.4.2-4 release, and we recommend that you install the latest update. To check the availability of newer kits, please visit our software download web page.

IMPORTANT: Please make sure you understand the Copyright (copyright.html, installed file) and License (license.html, installed file) information before using this release.

On OpenVMS, the Java virtual machine has a minimum required value for PGFLQUOTA of 512000 pagelets (250 MB). Beginning with SDK v 1.4.2-2, the maximum size of the Java heap on OpenVMS for Integrity (Itanium) has been extended from 900 MB to 1500 MB. To take advantage of the larger heap, you may need a larger process Page File Quota. Please see section Setting Process Quotas for Better Performance on OpenVMS in the User Guide for more information on maximum heap size and guidelines on setting PGFLQUO according to your heap size.

Installing the RTE

HP suggests that the RTE be installed in its own subdirectory (referred in Figure 1 as <JRE_RUNTIME_BASE>). This allows you to update the RTE independently of updates to your application, and vice versa.

Figure 1: Sample RTE Installation

  
              <APP-DIR>
                  |
 +---------+------+---------------------+
 |         |                            |
BIN       LIB                   <JRE_RUNTIME_BASE>
           |                            |
     APPLICATION.JAR         +----------+--------+-------+
                             |          |        |       |       
                            BIN        LIB    PLUGIN    DOC

                                   Supplied by HP

The files that make up the RTE are bundled into two OpenVMS BACKUP save sets:

JRE-V142-4_A.SAV
JRE-V142-4_A.SAV is a REQUIRED subset of files (approximately 351,000 blocks). Your licensing agreement requires that if you redistribute any part of the RTE, you must redistribute this set of files in its entirety. If you do not distribute all files, the RTE and your application may not work. To obtain a detailed list of the files in this save set, use the following command:

$ BACKUP/LIST JRE-V142-4_A.SAV/SAVE_SET

Note: The HotSpot VM files are included in this save set.

JRE-V142-4_B.SAV
The second save set, JRE-V142-4_B.SAV is an OPTIONAL subset of files (approximately 8,100 blocks). You may need some of these files to fully support your application in an international arena. This set does not need to be deployed in its entirety. Table 1 provides a detailed list of the files in this save set.

To create and unpack the REQUIRED and OPTIONAL save sets, do the following:

1. Create Save Sets:
   Execute the HP-I64VMS-JRE-V0104-24-1.SAV_SFX_I64EXE file (approximately 138,000 blocks), to create the JRE-V142-4_A.SAV and JRE-V142-4_B.SAV save sets:

   $ RUN HP-I64VMS-JRE-V0104-24-1.SAV_SFX_I64EXE

2. Unpack Save Sets:
   Unpack the JRE-V142-4_A.SAV and JRE-V142-4_B.SAV files into the appropriate subdirectories of your application. Continuing with the typical directory structure illlustrated in Figure 1, move the save sets into the [.JRE_RUNTIME_BASE] directory, then issue the following commands (edited to match your actual disk and directory names):

   $! Position yourself to the base directory for the RTE components
$ SET DEFAULT USER1$:[APP-DIR.JRE_RUNTIME_BASE]
$!
$! To unpack the JRE-V142-4_A.SAV save set,
$ BACKUP JRE-V142-4_A.SAV/SAVE [...]*.*
$!
$! To optionally unpack the JRE-V142-4_B.SAV save set,
$ BACKUP JRE-V142-4_B.SAV/SAVE [...]*.*


For information on bundling the RTE with application software for redistribution, refer to Bundling the RTE.

Table 1 lists the files in the optional save set, JRE-V142-4_B.SAV:

Table 1: Files in the Optional Save Set

Using the Run Time Environment

After installing the RTE, a number of symbols and logicals need to be set up to enable you to use the RTE. An RTE setup command file, JAVA$142_JRE_SETUP.COM, is deposited into the [.LIB] directory, resulting from restoring JRE-V142-4_A.SAV. Select the HotSpot VM using this command file. Run this command file as follows:

$ @USER1$:[APP-DIR.JRE_RUNTIME_BASE.LIB]JAVA$142_JRE_SETUP

where USER1$:[APP-DIR.JRE_RUNTIME_BASE. denotes the actual disk and directory name where you installed the RTE.

The Java command-line tool can then be used to launch your Java application using the RTE.

Redistributing the RTE

If you redistribute the RTE, you must follow the terms of the RTE Binary Code License agreement, which includes these terms:

• Do not arbitrarily subset the RTE. You may omit only the files in the JRE-V142-4_B.SAV optional subset.
• Include in your product's license the provisions called out in the RTE Binary Code License.

The following SDK files may be redistributed with the RTE:

• SYS$COMMON:[JAVA$142.BIN]JAVAC.
• SYS$COMMON:[JAVA$142.BIN]JAVA$JAVAC.EXE
• SYS$COMMON:[JAVA$142.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. In other words, your customers will be running the exact code you've tested.
  
  
• 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, 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 our web site.

Table 2 lists the notable differences between the RTE and the SDK:

Table 2: Notable Differences Between the RTE and the SDK

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 the OpenVMS Alpha platform, the following points should be considered:

1. Software vendors should bundle the RTE files and an installer with the Java software they supply to end-users. HP suggests that the RTE be installed in its own subdirectory (called <JRE_RUNTIME_BASE> in Figure 1). This allows you to update the RTE independently of updates to your application, and vice versa.
   
2. In addition to unpacking the files in the RTE, a number of symbols and logicals need to be set up to make your application run within the RTE. When you deploy your application, you will have to include your own .COM files that accomplish these setups. An RTE setup command file, JAVA$142_JRE_SETUP.COM, is deposited into the [.LIB] directory, resulting from restoring JRE-V142-4_A.SAV. This file contains the key commands you will need to merge into your application setup command file.
   
3. The RTE operates with a special set of class libraries — RT.JAR and (optionally) I18N.JAR. Your application must function with just these libraries.
   
4. You are not allowed to redistribute any class files from the SDK, and your application should have no dependencies on these files. You can redistribute the jar files that are part of the RTE.
   
5. HP recommends that you not rely on the CLASSPATH logical that might be on the target system, but explicitly identify the classpath by specifying the -cp option on the Java command line that invokes the RTE. (For more information on using the -cp option of the Java command, refer to Sun's Tools and Utilities documentation.)
   Hence, a typical Java command line when using the RTE will look like:
   $ JAVA -cp "/USER1$/APP-DIR/LIB/APPLICATION.JAR:." "Application"