Golden Code (R) Java (TM) Web Start Technology for OS/2 Version 1.2.0_02 README July 23, 2003 ----------------------------------------------------------------------------- Contents 1. Introduction 2. Product Description 3. Hardware/Software Requirements 4. Installation/Configuration 5. Submitting Defect Reports 6. Contacting Golden Code 7. Trademarks ----------------------------------------------------------------------------- 1. Introduction Thank you for using the Golden Code Java Web Start. A overview of the general architecture can be found in the readme.html file contained in the distribution. ----------------------------------------------------------------------------- 2. Product Description Source code for this product was licensed from Sun Microsystems, Inc. This code was carefully analyzed and the operating system specific or dependent portions were written from scratch to operate properly using the native OS/2 system APIs and resources. Since the resulting product was designed and built specifically for OS/2, it integrates well into the OS/2 environment and it takes advantage of all the native features to which an OS/2 application environment has access. ----------------------------------------------------------------------------- 3. Hardware/Software Requirements Hardware/software requirements are the same as described in the readme.txt file included with the Golden Code (R) Run Time Environment (RTE) and Software Development Kit (SDK). Additionally, either the Golden Code JVM 1.4.1, or the IBM JVM 1.3.1 RTE or SDK are required. ----------------------------------------------------------------------------- 4. Installation/Configuration The WebStart distribution is located in the JRE subdirectory after completion of the Golden Code SDK: java141\jre\javaws-1.2.0_02-os2.zip There is no install program other than unzip.exe. Since InfoZip is a freely available tool and ZIP is a very common format, we have chosen to distribute using this mechanism. The javaws-1.2.0_02-os2.zip does not contain any directory structure. Use the -d option of unzip.exe to specify the destination directory. Most installations use the X:\javaws directory, so in this case the syntax of the unzip command would be: unzip javaws-1.2.0_02-os2.zip -d X:\javaws There is no requirement to use this directory, it is chosen as an illustration. However, the volume upon which the product is installed MUST support long filenames at this time. JAVAWS_HOME Environment Variable -------------------------------- This environment variable is used to determine the location of the JAVAWS.CFG file, which contains information about the JRE to use. You may choose to set this environment variable in CONFIG.SYS, and reboot: SET JAVAWS_HOME=X:\javaws More simply, you may use the included REXX "wrapper" named jump.cmd, which is included in the distribution. If jump.cmd is utilized as the only method by which Java Web Start is invoked, there is no configuration of this environment variable required. DO NOT change your LIBPATH. This is unnecessary and will provide no benefits. JAVAWS.CFG Considerations ------------------------- This file contains information required by Java Web Start to determine what Java runtime environment to utilize. # GCD JVM 1.4.1 javaws.cfg.jre.0.path=c:/java141/bin/java.exe javaws.cfg.jre.0.platform=1.4 javaws.cfg.jre.0.product=1.4.1 javaws.cfg.jre.0.location=http://java.sun.com/products/autodl/j2se javaws.cfg.jre.default=0 This file can be modified with any text editor, such as EPM or TEDIT. The path information should me changed to match your particular system configuration. If you intend to use IBM JVM 1.3.1, the format would be: # IBM JVM 1.3.1 javaws.cfg.jre.0.path=c:/java131/jre/bin/java.exe javaws.cfg.jre.0.platform=1.3 javaws.cfg.jre.0.product=1.3.1 javaws.cfg.jre.0.location=http://java.sun.com/products/autodl/j2se javaws.cfg.jre.default=0 Note that the path can be specified either with forward slashes (/) or double backslashes (\\). Comments are denoted with a pound sign (#). The location URL must be present, but currently there is no automated download of the JVM for the GCD JVM or the IBM JVM. If there is a mismatch between the requested JVM version in the JNLP file, and the configured JVM version, a detailed message will be displayed by Web Start indicating the failure. Workplace Shell Program Object ------------------------------ If you would like to have a program object on your desktop, which launches the Java Web Start Application Manager, you can use the javaws_icon.cmd REXX program included in the distribution. Simple answer "Y" when prompted, and it will be created with the proper path information based upon your configuration. Netscape/Mozilla Helper Application ------------------------------------- For users of Netscape or Mozilla web browsers, please set up the Java Web Start MIME type (JNLP) in the Edit->Preferences Helper Applications section. The file extension is "jnlp", the MIME Type is "application/x-java-jnlp-file", and it should be handled by the jump.cmd wrapper REXX program in your Java Web Start software directory. When using Mozilla, there is a problem with using JavaScript technology. See the http://java.sun.com/products/javawebstart/demos.html page for a demo, and also a very good tool for testing your configuration. ----------------------------------------------------------------------------- 5. Submitting Defect Reports To submit a defect report, please send an e-mail to: techsupport@goldencode.com The following information should always be included in a problem submission: * Your name. * Your organization's name (if applicable). * Your reply-to e-mail address. * The serial number of the product license. This can be obtained by running 'java -Xlicenseverify' at the command line. * A detailed description of the problem, including steps on how to recreate the error condition. * If it is possible to isolate the problem with a small test case, the test case should be attached to the e-mail, or instructions on how to download the test case. * The hotspot log file that was created when the problem was encountered, if the problem ended in a crash of the product. Some problems may be caused by underlying defects in the OS/2 operating system or other related IBM software. If a defect is found to be so caused, Golden Code has an arrangement with IBM in which the two companies can effectively work together to resolve such issues. The customer must open an IBM PMR and authorize the IBM personnel to work with Golden Code on this issue. PLEASE NOTE THAT UNLESS YOU MAKE ARRANGEMENTS TO EXCHANGE ENCRYPTED E-MAIL WITH GOLDEN CODE DEVELOPMENT, ANY E-MAIL YOU SEND IS NOT SECURE AND MAY BE VIEWED IN TRANSIT. A secure, web-based defect reporting system for the use of service clients is currently under development. We hope to have it available shortly. ----------------------------------------------------------------------------- 6. Contacting Golden Code E-mail : info@goldencode.com (general), techsupport@goldencode.com (support) Address : Suite 135, 1455 Old Alabama Rd., Roswell, Georgia, U.S.A. Phone : +1 678-352-2301 Fax : +1 678-352-2305 ----------------------------------------------------------------------------- 7. Trademarks 'Golden Code' is a registered trademark of Golden Code Development Corporation. 'IBM' and 'OS/2' are registered trademarks of International Business Machines Corporation. 'WorkSpace On-Demand' is a trademark of International Business Machines Corporations. 'Java', 'Java 2 Platform Standard Edition', and 'Java Compatible' are trademarks of Sun Microsystems, Inc. Other names referenced in this document are the property of their respective owners. ----------------------------------------------------------------------------- Copyright (c) 2002-2003, Golden Code Development Corporation. ALL RIGHTS RESERVED. -----------------------------------------------------------------------------