Novell JVM 1.4.0 For NetWare Readme Table of Contents 1.0 Introduction 2.0 Documentation 3.0 System Requirements 4.0 Known Issues 5.0 NJVM 1.4 Product Support 5.1 Products Supported on NJVM 1.4 5.2 Products Currently Being Tested on NJVM 1.4 5.3 Products Not Supported with NJVM 1.4 6.0 New Feature Support 6.1 GUI Environment Utility for GUI Configuration 6.2 Default and Alternative XServers 6.3 Configurable Desktop Menu 6.4 JAVA_CODEPAGE Environment Variable 6.5 JAVA_CASE_SENSITIVE_CANONICAL_PATH Environment Variable 6.6 Default Font Size Modification 6.7 Motif Look-and-Feel for AWT Components 7.0 Known Issues 8.0 Recommendations 8.1 Video Card 8.2 Classes and Libraries 9.0 JVM Installation 9.1 NetWare Dependencies 9.2 Installing NJVM 1.4 9.3 Instructions for Updating AUTOEXEC.NCF 10.0 Performance Tuning 11.0 Support 12.0 Updates to NJVM 1.4 13.0 Legal Notices 1.0 Introduction This release of Novell JVM for NetWare is version 1.4.0 Support Pack 2 (SP2). In this document, Novell JVM 1.4.0 SP2 for NetWare is referred to as NJVM 1.4. NJVM 1.4 supports version 1.4.0_02 of the JDK. Pure Java applications and applets developed on other platforms should run unmodified on the NJVM. Because Novell is committed to providing the best Java server platform, the GUI on NetWare is intended to provide full support of Java Abstract Windowing Toolkit (AWT) and Java Foundation Classes (JFC) libraries. The GUI on NetWare will continue to be fully compliant with the compatibility testing requirements that Sun Microsystems, the owner of Java, establishes in order to remain eligible to receive the Java Compatible designation. Recommendations for tools, third-party class libraries, and hardware follow later in this document. For updated information about Novell's Java products, visit the Novell Java home page (http://developer.novell.com/ndk/jvm14.htm). or the Novell JVM 1.4 for NetWare Download page (http://download.novell.com). 2.0 Documentation To view the documentation for NJVM 1.4, see the Novell Documentation Web site (http://www. novell.com/documentation/lg/jvm14/index.html). 3.0 System Requirements - NJVM 1.4 requires NetWare 6 with Support Pack 2 or later. - LIBC dated January 2003 or later. To download the latest LIBC, go to the Libraries for C (http://developer.novell.com/ndk/libc.htm) section of the NDK. Install the libraries to your local drive then copy all of the nlms to your server. Follow the instructions for installing LIBC in the LIBC Readme. - Memory requirements depend on the size and requirements of the Java applications being executed. However, you should have at least 32 MB available for text-based applications and 64 MB for AWT-based (graphics) applications. - A video card that supports VESA 1.2 or higher. VESA 2.0 is preferred (see section 5.1). 4.0 Known Issues - During an upgrade, sometimes the xlib.nlm does not unload. If this occurs, we recommend restarting the server or you can manually unload xlib.nlm. 5.0 NJVM 1.4 Product Support NJVM 1.4 is a fully certified java virtual machine. This release of NJVM 1.4 has passed all of the tests in Sun's Java Conformance Kit. Novell thoroughly tests JVM releases before making them available to the public. All Novell software products might not be compatible with NJVM 1.4 at this time. Extensive testing occurs for all major NetWare releases and Consolidated Support Pack releases. NJVM 1.4 is being released on the Novell.com download area as a convenience to our customers who want to use the new release. NOTE: The forthcoming releases of Consolidated Support Pack 9 and NetWare 6.5 will include and support NJVM 1.4.1. Until then, review the information in this section to see the status of the products that support NJVM 1.4. This section lists the products that 1) have been tested with and support NJVM 1.4, 2) are currently being tested with NJVM 1.4 but not yet validated to support NJVM 1.4, and 3) will not support NJVM 1.4. This section will be updated in future releases of NJVM 1.4 as Novell products add support for NJVM 1.4. 5.1 Products Supported on NJVM 1.4 - eGuide 2.11 - Portal Services (Novell exteNd Director) - Tomcat - Web Search 5.2 Products Currently Being Tested on NJVM 1.4 The following products have an undetermined support status on NJVM 1.4. Full testing of these products with NJVM 1.4 has not been completed. Use caution when using these products with NJVM 1.4 in a production environment: - Border Manager - ConsoleOne - eDirectory - FTP Server Web Management - GroupWise Monitor - GroupWise Web Access - i-Login - i-Manager - NetStorage - Novell Installation Services (NIS) - Novell Remote Manger - On-Demand - Zen for Desktops 5.3 Products Not Supported with NJVM 1.4 - DirXML 1.1a - UCS - Zen for Servers 3 6.0 New Feature Support 6.1 GUI Environment Utility for GUI Configuration An XSetup utility is provided for configuring the GUI environment. You access this utility by clicking Start > Settings > GUI Environment. It should be used to configure super VGA and accelerated-X servers on NetWare. It also lets you select the video board, keyboard, mouse, and monitor for these video controllers from a set of predefined hardware devices that are supported by the XSetup utility. 6.2 Default and Alternative XServers XVesa is the default GUI environment. The Xi Graphics Accelerated-X XServer is available as an alternative. XVesa supports VESA 1.2 through 3.0. NJVM GUI supports VESA-compliant video controllers. Accelerated-X supports over 540 specific video cards. 6.3 Configurable Desktop Menu A configurable desktop menu is provided with options for adding, modifying, and removing menu items. You can modify the menu by using the menu editor. Click Settings > Menu Editor > on the GUI taskbar menu. To use the menu editor to add a command: 1. Click the menu where you want to add the command, then click New Command. 2. In the text fields in the lower part of the menu, enter the menu name and the command that will run. 3. Save the changes. 4. To verify that the changes appear on the menu, click the taskbar's Novell button. We recommend that the commands be names of .ncf files that contain the actual commands that are to be executed. 6.4 JAVA_CODEPAGE Environment Variable The default code page used on an English NetWare server is 437. This default will remain the same; however, if your instantiation of NJVM 1.4 needs to use a different code page, you can change it via the JAVA_CODEPAGE environment variable. Examples of Usage: - envset JAVA_CODEPAGE=Cp1252 - envset JAVA_CODEPAGE=Cp437 - envset JAVA_CODEPAGE=ISO8859_I or - java -envJAVA_CODEPAGE=Cp1252 YourClassName - java -envJAVA_CODEPAGE=ISO8859_1 YourClassName or - java -Dfile.encoding=ISO8859_1 YourClassName - java -Dfile.encoding=Cp1252 YourClassName These are only examples and do not represent all the code pages that are supported. To view other possible values, see the Java Web site (http://java.sun.com/j2se/1.4/docs/guide/intl/enc oding.doc.html). 6.5 JAVA_CASE_SENSITIVE_CANONICAL_PATH Environment Variable By default, when NJVM 1.4 creates a canonical path, the path might not conform to the same case as the underlying file system entry for the path if an entry exists. If your application needs canonical paths to be the exact case as in the underlying file system, you must define the JAVA_CASE_SENSITIVE_CANONICAL_PATH environment variable. It can be set to any value. Examples of usage: - Environment variable not present Leaves off functionality. - envset JAVA_CASE_SENSITIVE_CANONICAL_PATH= Turns off the functionality if it was set. - envset JAVA_CASE_SENSITIVE_CANONICAL_PATH=ON Turns on the functionality. - envset JAVA_CASE_SENSITIVE_CANONICAL_PATH=(any value) Turns on the functionality. Even setting the variable to OFF will turn the functionality on. - java envJAVA_CASE_SENSITIVE_CANONICAL_PATH=ON YourClassName Turns on the functionality on for the specified application. 6.6 Default Font Size Modification For some character sets, users, and languages, the default font sizes specified by NJVM 1.4 are either too small or too large for comfortable and convenient viewing. NJVM 1.4 has the limited ability to scale up the defaults by a fixed number. This affects only the applications that use the default font size. For example, applications such as NetWare Install have developer-specified font sizes. These remain unchanged. To change the defaults, locate your font.properties file located in sys:\java\lib\. This file is named with an extension composed of the machines's language and locale settings. For example, a machine using English language located in New Zealand uses font.properties.en_NZ and a machine using the Russian language uses font.properties.ru. If your specific language/locale combination is not found, NJVM 1.4 defaults to just the language. If your language is also not found, NJVM 1.4 defaults to the generic font.properties file with no extension. After you find the appropriate font.properties file, add the following line to the file: FontSizeCorrection= Replace with the number you want to increase or decrease the default font sizes by. For example, to change the default Japanese default font size from 12 to 16, open the sys:\java\lib\font.properties.jp file and enter the number 4 on the following line: FontSizeCorrection=4 You can use negative numbers, but these are not recommended because the default font sizes are determined based on minimum size for readability. 6.7 Motif Look-and-Feel for AWT Components In NJVM 1.4, the look and feel for AWT components was changed from the Metal look-and-feel to the Motif look-and-feel, which is similar to many UNIX systems. This does not affect Swing applications. 7.0 Known Issues During an upgrade, sometimes the xlib.nlm does not unload. If this occurs, we recommend restarting the server or you can manually unload xlib.nlm. If any errors occur during the installation, see 9.2 Installing NJVM 1.4. 8.0 Recommendations 8.1 Video Card If you are purchasing a new video card, VESA 2.0 or later support with linear frame buffer access is preferred. Some early cards might not be VESA 2.0 compliant. The PCI and AGP bus types are the preferred types because they are the fastest. The NetWare GUI performs at the same speed with PCI and AGP. 8.2 Classes and Libraries When writing Java applications to run on NetWare, we recommend using the Swing classes from Sun Microsystems. 9.0 JVM Installation 9.1 NetWare Dependencies NJVM 1.4 requires NetWare 6 with Support Pack 2 or later. 9.2 Installing NJVM 1.4 1. Unload NJVM (if loaded) 2. Map a drive or attach to the servers where you want to install the NJVM files. You must have administrator rights to the servers. 3. Run JVM14sp2.exe on your workstation. 4. Follow the rest of the InstallShield instructions to complete the install. 5. Reboot your servers. IMPORTANT: If the error "Error - unable to copy java.zip to SYS:\" occurs during the installation, make sure you have the latest Novell client installed before you attempt to reinstall. IMPORTANT: A message might appear at the end of the installation process indicating that the jsock6x.nlm and jsock.nlm were not unloaded prior to the installation. If this occurs, you must restart your server. An issue in the JVM version 1.4 sometimes prevents these nlms from unloading when you unload java.nlm. NOTE: If any problems occur with the GUI after you upgrade to NJVM 1.4, unload Java and run VESA_RSP at the server console. This resets the GUI to the default settings. 9.3 Instructions for Updating AUTOEXEC.NCF If this file did not automatically update during the install, these instructions explain how to update the file manually. To update the sys\system\autoexec.ncf file, add the following lines right after the Mount All command in the file: - SEARCH ADD SYS:\JAVA\BIN - SEARCH ADD SYS:\JAVA\NWGFX\BIN - startx The startx line is optional; it causes the java GUI to begin running at server startup. We recommend that you delete any other instances of these lines in autoexec.ncf. 10.0 Performance Tuning If you have a Java-based server program on the NetWare server that handles a large amount of traffic, you might need to increase the maximum number of packet receive buffers on the server. This prevents packets from getting dropped. Dropped packets slow performance because client programs have to time out and retransmit. To increase packet receive buffers, you can issue a NetWare console command such as set maximum packet receive buffers = 1000 You can add this command to autoexec.ncf so it is always set when the server comes up. The default native (C) stack size for Java threads on NetWare is 160 KB. For applications that create many threads and do not require such a large stack size, the -ss java command parameter can be used to specify the stack size. (See JavaSoft's documentation for the Java Interpreter for an explanation of the Java command options.) To specify the amount of Virtual memory available to Java applications for non-heap allocations, use the -vm Java command option. The default is 64 MB. The -vm Java command option is unique to NetWare and is not supported by JavaSoft. The following is the syntax for this option: java -vm MyClass 11.0 Support Support for the NJVM is provided by Novell Developer Services through the Developer newsgroup (http://developer- forums.novell.com/group/novell.devsup.jvm/tmainSuppor t.tpt/@overview@last@R@300@T,D) 12.0 Updates to NJVM 1.4 You can download NJVM 1.4 for NetWare from the Novell Web site (http://www.novell.com/download/index.html). 13.0 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. Novell is a registered trademark of Novell, Inc. in the United States and other countries. All third-party products are the property of their respective owners.