December 1st, 1999
Contents:
1. General Information
2. Package contents
3. Requirements
4. Installation
5. Tips and tricks
6. Known issues
Two implementation variations of the Java Runtime Environment are available.
The "green threads" implementations use their own
mutlithreading, and the "native threads" implementations
use the multithreading mechanism of the underlying operating system.
|
the package for HP-UX, based on the green-threads implementation of the JRE |
|
|
the package for Linux, based on the green-threads implementation of the JRE |
|
|
the package for Sun Solaris, based on the native-threads implementation of the JRE |
|
|
the installation program for Win32, based on the native-threads implementation of the JRE |
|
|
the documentation-file for the Hyperwave Java Virtual Folders |
|
|
this readme file |
|
|
Winsock 2 upgrade for Windows 95 |
|
|
changes from previous versions |
|
Operating System Versions: Solaris 2.5.1 and above.
JRE-Version: use the packaged Version of the JRE, which can be 1.1.8 and above.
For requirements specific to the Java Runtime Environment for Sun, read the information provided on
and the information shipped with the JRE itself:
jre_config.txt
readme.sparc
The last file includes essential information about operating system requirements.
Operating System Versions: HP-UX 10.20 and 11.00
JRE-Version: use the packaged Version of the JRE, which can be 1.1.7 and above.
For requirements specific to the Java Runtime Environment for HP, read the information provided on
and the JRE release notes shipped with the JRE itself:
jre.release.notes
Compatibility: glibc 2.1.x and XFree386 Version 3.3.x
JRE-Version: use the packaged Version of the JRE, which can be 1.1.7 and above
Operating Systems: MS-Windows 95 / 98 / NT4.0.
Note: The JRE requires two additional components to be installed:
the dynamic link library msvcrt.dll with a version number of 6.00.8337 and above. This library is installed on the operating system's "system"-directory by the installation program. Previous versions of the library are replaced. If you have stability problems with the JRE, check if the appropriate dll is installed.
Winsock 2, if you intend to use the JVF under Windows 95. Winsock 2 is NOT included in the JVF installation program and therefore needs to be installed seperately. You can download Winsock 2 from either the FTP-Directory, where you downloaded this Readme-file or from here. For additional information about Winsock 2 see the README-file which is included in the JRE.
The installation packages include the JVF application plus a "private" Java Runtime Environment, which is installed into a subdirectory of the installation-directory you chose.
Copy the Java Virtual Folders package for your architecture to the directory where you want to install Java Virtual Folders, e.g. your home directory. If you are a system administrator you can install the Java Virtual Folders globally in a place like /usr/local.
Unpack the Java Virtual Folders package.
e.g. for Linux this is done as follows: gzip
-dc hwjvfLINnat.tgz | tar xvf -
This will create a directory called HWJVirtualFolders/.
Add the HWJVirtualFolders/jvf script to your path. You have two choices for doing this:
extend the path environment variable by the HWJVirtualFolders/ directory, e.g. setenv path=(~/HWJVirtualFolders $path) or
link the script to a directory which is currently in the path, e.g.
cd /usr/local/bin
ln -s /usr/local/HWJVirtualFolder/jvf
Now you can start the Java Virtual Folders by executing jvf
The first time you start the Java Virtual Folders, they create a .hwjava directory in the users home directory. This directory is used to store the various configuration files.
Note: It is recommended to set the access rights of the .hwjava directory to read/write access only for the owner. (e.g. chmod 700 .hwjava)
Run the installation program hwjvf.exe and follow the steps prompted by the installation wizard.
If you are not working behind a firewall and you do not connect over a proxy you can configure your server entries to use port 418 (HGCSP connection). This will speed up working with the Java Virtual Folders and decrease network traffic to the Hyperwave Information Server.
After 24 hours of inactivity the HGCSP connection will be closed and will not be restored automatically by the following requests thus leading to error messages. You may remove the server and add it again or restart the Java Virtual Folders to reestablish the connection.
The JVF perform caching for server-objects, which requires significant amounts of memory. The memory limit for the JVF is defaulted to 48MB. If you observe problems due to insufficient memory you can increase the value associated to the parameter -mx by modifying the wrapper-script (UNIX) or the shortcut (Win32). The value -mx32m (e.g.) corresponds to a limit of 32MB.