home *** CD-ROM | disk | FTP | other *** search
- __________________________________________________________________
- Installing Java** 1.0.2 for OS/2*: READ.ME
-
- (c) Copyright International Business Machines Corporation, 1997.
- All Rights Reserved.
-
- __________________________________________________________________
- CONTENTS
-
- 1. Before You Install
- 1.1. Saving a Previous Version of Java
- 1.2. Replacing a Previous Version of Java
- 1.3. Java Components
- 1.4. HPFS and FAT Partition Considerations
- 2. Installation
- 2.1. Icon Installation Method
- 2.2. Command Prompt Installation Method
- 2.3. Unattended (CID) Installation Method
- 2.3.1. Modifying the Response File
- 2.3.2. Starting the Unattended Installation
- 2.4. TME-Architected CID Installation Method
- 3. After You Install
- 3.1. Additional Sources of Information
- 3.2. Disabling the Just In Time (JIT) Compiler
- 3.2.1. Using Netscape Navigator**
- 3.2.2. Setting an Environment Variable
- 3.2.3. Specifying a Property on the JAVA invocation
- 3.2.4. Renaming the DLL
- 3.3. Considerations for Files on CD-ROM
- 3.4. Viewing HTML or Java Objects in Warp 3 and Warp Connect
- 3.5. Fixing Incorrect Icons in OS/2 Warp 4.0
- 4. Trademarks
-
- _________________________________________________________________
- 1. Before You Install
-
- Note: In this document, the term partition refers to any
- physical or logical drive.
-
- _______________________________________
- 1.1. Saving a Previous Version of Java
-
- If you previously installed Java and wish to keep a copy of
- your previous Java environment, you can install the new
- Java on a different partition by specifying a different
- target drive during installation. If you have only one
- partition, copy the contents of the \JAVAOS2 directory into
- another directory. When you take either of these steps,
- the install program does not delete your previous Java
- environment and updates the CONFIG.SYS file to ensure that
- the new version is accessed.
-
- _________________________________________
- 1.2. Replacing a Previous Version of Java
-
- If you previously installed Java, the install program
- searches the directories defined in the CLASSPATH statement
- of your CONFIG.SYS file for the Java executable files.
- Based on the CLASSPATH statement and the age of the
- executable files, the install program recommends a
- partition for Java replacement. Java is always installed
- into a \JAVAOS2 directory on the selected partition. When
- the install program prompts you to replace an existing
- file, select:
-
- Yes to all
-
- _____________________
- 1.3. Java Components
-
- The Java for OS/2 product consists of four components:
-
- Runtime
- Toolkit
- Samples
- DBCS Support
-
- The Runtime component is required to execute Java
- applications and applets. To use the other components,
- you must install the Runtime component.
-
- The Toolkit component contains tools and documentation for
- developing your own Java applications and applets.
-
- The Samples component contains sample source code and
- byte code compiled class files. The Samples component
- can be installed and run without installing the Toolkit
- component, but you cannot modify and compile the sample
- source code without the Toolkit component.
-
- The Double Byte Character Set (DBCS) Support component
- provides base OS/2 DBCS support fixes required to exploit
- Java DBCS character display and input on OS/2 Warp* 4.0.
- This component is supported only on OS/2 Warp 4.0; it may
- be installed on earlier versions of OS/2 Warp but does not
- provide DBCS function in Java.
-
- Each of the four Java components can be installed at
- different times as long as the Runtime component is
- installed first.
-
- __________________________________________
- 1.4. HPFS and FAT Partition Considerations
-
- The Java Toolkit and Java Samples components require an HPFS
- partition. If you select a FAT partition during installation
- of these components, the install program warns you that an
- HPFS partition is required.
-
- The Java Runtime and DBCS support components can be
- installed on a FAT partition. However, to use the Java
- Toolkit and Samples components, all of the components must
- be installed in the same partition. If you install the
- Runtime component on a FAT partition, you cannot install
- the Toolkit and Samples components. If you attempt to
- install the Toolkit or Samples components on a FAT
- partition, the install program fails with error code
- x'0060' (960 decimal), and the components are not installed.
-
- Note: If you have only one hard disk with a single FAT
- partition, you have three options:
-
- - Leave your system as it is and install only the Runtime
- component and, if needed, the DBCS Support component.
-
- - Format that partition for HPFS and reinstall all
- software.
-
- - Purchase a disk partitioning program, such as
- PartitionMagic**. With sufficient space,
- PartitionMagic reduces the size of the current
- partition (drive C) and creates a new partition
- (logical drive D), which can be formatted for HPFS.
-
- _________________________________________________________________
- 2. Installation
-
- To install Java 1.0.2 for OS/2, use one of the following
- methods:
-
- ______________________________
- 2.1. Icon Installation Method
-
- To install from the INSTALL.EXE icon, follow these steps:
-
- 1. Open the OS/2 System folder.
- 2. Open the Drives object.
- 3. Open the drive where the Java files were extracted.
- 4. Open the directory where the Java files were extracted.
- 5. Select the INSTALL.EXE icon to start the install program.
-
- The Software Installer program leads you through the
- installation steps.
-
- ________________________________________
- 2.2. Command Prompt Installation Method
-
- To start installation, make sure that you are in the
- directory where the Java files were extracted. At an
- OS/2 Window command prompt, enter:
-
- install
-
- The Software Installer program leads you through the
- installation steps.
-
- __________________________________________
- 2.3. Unattended (CID) Installation Method
-
- Unattended or CID installations of Java for OS/2 can take up
- to 15 to 20 minutes or more. Please ensure that the
- unattended install completes before re-booting your system.
-
- To install using the unattended method, you must modify the
- response file before entering the install command at an
- OS/2 command prompt.
-
- _________________________________
- 2.3.1 Modifying the Response File
-
- Locate the file JAVARESP.RSP in the directory where the
- Java files were extracted. This file is a standard
- Software Installer response file that contains
- keyword-value pairs to control the unattended install.
- The only Java-unique entries in this file are the
- component names.
-
- The FILE variable specifies the target drive (including a
- colon) for the install. Java is always installed in the
- \JAVAOS2 directory on the target drive. If a previous
- version of Java exists on the target drive, the install
- program replaces it.
-
- The COMP variables specify the components to install.
- Component names are OS/2 Java Runtime, OS/2 Java Toolkit,
- OS/2 Java Samples, and OS/2 Java DBCS Support. Modify
- this list to include the components that you want to
- install. The Runtime component is a prerequisite for
- installation of the Toolkit, Samples, and DBCS Support
- components. Consult the Software Installer online
- documentation for further information on variables in
- this file by entering:
-
- view c:\path\EPFIHPLB.HLP
-
- where path is where the Java files were extracted. After
- Java is installed, this file is in the \JAVAOS2 directory.
- Search on the Response file format.
-
- __________________________________________
- 2.3.2 Starting the Unattended Installation
-
- To start an unattended install, enter the following
- single-line command at an OS/2 command prompt:
-
- install /x /a:i /nmsg /o:drive /r:c:\path\javaresp.rsp
- /L1:c:\path\outputfile1 /L2:c:\path\outputfile2
-
- where /r specifies the fully-qualified location of the
- response file. The parameters /L1 and /L2 specify the
- fully-qualified locations of the log files. The command
- above installs the components specified in the response
- file C:\PATH\JAVARESP.RSP.
-
- To delete, update, or restore Java for OS/2, change the
- install parameter /a:i to /a:d, /a:u, or /a:r,
- respectively.
-
- For more information on installing Java using the
- NetView Distribution Manager/2 or the LAN CID Utility
- consult the Software Installer on-line documentation and
- respective product documentation.
-
- _____________________________________________
- 2.4. TME-Architected CID Installation Method
-
- A JAVA.ADF file is provided for use with Tivoli
- Management Environment (TME) architected CID
- installation products, such as Netfinity Server and the
- Tivoli TME-10 Software Distribution Agent. See the
- documentation pertaining to the CID installation product
- being used for instructions regarding the use of .ADF
- files.
-
- _________________________________________________________________
- 3. After You Install
-
- _______________________________________
- 3.1. Additional Sources of Information
-
- The following objects display in the Java folder only if you
- are running OS/2 Warp 4.0. If you are not running OS/2 Warp
- 4.0, you can access the associated documents at the following
- locations, substituting the partition you installed Java on
- for x:
-
- IBM Centre for Java Technology
- http://ncc.hursley.ibm.com/javainfo/
-
- Running Java
- x:\JAVAOS2\runtime.htm
-
- Configure Applet Viewer
- x:\JAVAOS2\cnfgappl.htm
-
- Java Developers Kit for OS/2
- x:\JAVAOS2\index.html
-
- Java Toolkit
- x:\JAVAOS2\toolkit.html
-
- Java API
- x:\JAVAOS2\docs\api\API_users_guide.html
-
- Java Documentation
- http://www.javasoft.com/doc.html
-
- _______________________________________________
- 3.2. Disabling the Just In Time (JIT) Compiler
-
- A Just In Time (JIT) compiler is provided with Java 1.0.2
- for OS/2 which generates machine code for frequently used
- byte code sequences in a Java application or applet
- on-the-fly during execution.
-
- You can disable the JIT to aid in the isolation of a
- problem with a Java application, an applet, or the compiler
- itself in a number of different ways:
-
- _________________________________
- 3.2.1. Using Netscape Navigator**
-
- The JIT can be disabled in the Netscape Navigator for
- OS/2 by selecting the Options pulldown, choosing
- Security Preferences..., and checking the Disable Java
- Compiler box.
-
- ______________________________________
- 3.2.2. Setting an Environment Variable
-
- You can set the environment variable JAVA_COMPILER to
- the name of a non-existent DLL, such as
- SET JAVA_COMPILER=xyz. Specify blanks for the name to
- suppress the "Unable to load DLL" warning message.
-
- ___________________________________________________
- 3.2.3. Specifying a Property on the JAVA invocation
-
- You can set a property on the invocation of JAVA.EXE to
- point to a non-existent DLL or blanks as shown here:
-
- java -Djava.compiler= hello
-
- _______________________
- 3.2.4. Renaming the DLL
-
- You can rename the file JAVAX.DLL in the \JAVAOS2\DLL
- directory to something else, such as JAVAX.BAK. If
- JAVAX.DLL is not found in the LIBPATH, the JIT is
- disabled for both the Netscape Navigator and Java
- applications.
-
- ________________________________________
- 3.3. Considerations for Files on CD-ROM
-
- The CD-ROM file naming specifications have been relaxed
- in recent years to allow the use of long names and names
- in mixed case. The CD-ROM file system shipped with OS/2
- does not support these features.
-
- _____________________________________________________
- 3.4. Viewing HTML or Java Objects in Warp 3 and Warp Connect
-
- Selecting HTML or Java objects in the Workplace Shell on OS/2
- Warp 3 or OS/2 Warp Connect systems results in no information
- being displayed. This is caused by an improper setting for
- the Editor for Java object in the Java for OS/2 folder.
-
- To correct the setting, open the settings for the Editor for
- Java object and remove the /R from the Parameters: field on
- the Program page. Close the settings notebook to save the
- changes.
-
- _____________________________________________
- 3.5. Fixing Incorrect Icons in OS/2 Warp 4.0
-
- If Java for OS/2 is installed on an OS/2 Warp 4.0 system and
- subsequently deleted and re-installed, the icons for the Java
- Applet Viewer from HTML and the Java Applet Viewer from URL
- objects in the Java for OS/2 folder are incorrect.
-
- To correct the icons, run the ICONS40.CMD file by
- entering the name from an OS/2 Window command prompt
- while in the javaos2 directory.
-
-
- _________________________________________________________________
- 4. TRADEMARKS
-
- The following terms, denoted by an asterisk (*) the first time
- they appear in this READ.ME file, are trademarks or registered
- trademarks of the IBM Corporation in the United States or other
- countries or both:
-
- IBM
- NetView
- OS/2
- OS/2 Warp
- Workplace Shell
-
-
- The following terms, denoted by a double asterisk (**) the
- first time they appear in this READ.ME file, are trademarks or
- registered trademarks of other companies:
-
- TRADEMARK OWNER
- ___________________ _____________________________________
-
- Netscape Netscape Communications Corporation
- Netscape Navigator
-
- PartitionMagic PowerQuest Corporation
-
- Java and HotJava are trademarks of Sun Microsystems, Inc.
-
- <end of file>