1 | Golden Code (R) Java (TM) Web Start |
---|
2 | Technology for OS/2 |
---|
3 | Version 1.2.0_02 |
---|
4 | README |
---|
5 | |
---|
6 | July 23, 2003 |
---|
7 | |
---|
8 | ----------------------------------------------------------------------------- |
---|
9 | |
---|
10 | Contents |
---|
11 | |
---|
12 | 1. Introduction |
---|
13 | 2. Product Description |
---|
14 | 3. Hardware/Software Requirements |
---|
15 | 4. Installation/Configuration |
---|
16 | 5. Submitting Defect Reports |
---|
17 | 6. Contacting Golden Code |
---|
18 | 7. Trademarks |
---|
19 | |
---|
20 | ----------------------------------------------------------------------------- |
---|
21 | |
---|
22 | 1. Introduction |
---|
23 | |
---|
24 | Thank you for using the Golden Code Java Web Start. A overview of the general |
---|
25 | architecture can be found in the readme.html file contained in the |
---|
26 | distribution. |
---|
27 | |
---|
28 | ----------------------------------------------------------------------------- |
---|
29 | |
---|
30 | 2. Product Description |
---|
31 | |
---|
32 | Source code for this product was licensed from Sun Microsystems, Inc. This |
---|
33 | code was carefully analyzed and the operating system specific or dependent |
---|
34 | portions were written from scratch to operate properly using the native OS/2 |
---|
35 | system APIs and resources. Since the resulting product was designed and built |
---|
36 | specifically for OS/2, it integrates well into the OS/2 environment and it |
---|
37 | takes advantage of all the native features to which an OS/2 application |
---|
38 | environment has access. |
---|
39 | |
---|
40 | ----------------------------------------------------------------------------- |
---|
41 | |
---|
42 | 3. Hardware/Software Requirements |
---|
43 | |
---|
44 | Hardware/software requirements are the same as described in the readme.txt |
---|
45 | file included with the Golden Code (R) Run Time Environment (RTE) and |
---|
46 | Software Development Kit (SDK). |
---|
47 | |
---|
48 | Additionally, either the Golden Code JVM 1.4.1, or the IBM JVM 1.3.1 RTE or |
---|
49 | SDK are required. |
---|
50 | |
---|
51 | ----------------------------------------------------------------------------- |
---|
52 | |
---|
53 | 4. Installation/Configuration |
---|
54 | |
---|
55 | The WebStart distribution is located in the JRE subdirectory after |
---|
56 | completion of the Golden Code SDK: |
---|
57 | |
---|
58 | java141\jre\javaws-1.2.0_02-os2.zip |
---|
59 | |
---|
60 | There is no install program other than unzip.exe. Since InfoZip is a freely |
---|
61 | available tool and ZIP is a very common format, we have chosen to distribute |
---|
62 | using this mechanism. |
---|
63 | |
---|
64 | The javaws-1.2.0_02-os2.zip does not contain any directory structure. Use |
---|
65 | the -d option of unzip.exe to specify the destination directory. Most |
---|
66 | installations use the X:\javaws directory, so in this case the syntax of the |
---|
67 | unzip command would be: |
---|
68 | |
---|
69 | unzip javaws-1.2.0_02-os2.zip -d X:\javaws |
---|
70 | |
---|
71 | There is no requirement to use this directory, it is chosen as an |
---|
72 | illustration. However, the volume upon which the product is installed MUST |
---|
73 | support long filenames at this time. |
---|
74 | |
---|
75 | JAVAWS_HOME Environment Variable |
---|
76 | -------------------------------- |
---|
77 | |
---|
78 | This environment variable is used to determine the location of the |
---|
79 | JAVAWS.CFG file, which contains information about the JRE to use. You may |
---|
80 | choose to set this environment variable in CONFIG.SYS, and reboot: |
---|
81 | |
---|
82 | SET JAVAWS_HOME=X:\javaws |
---|
83 | |
---|
84 | More simply, you may use the included REXX "wrapper" named jump.cmd, which |
---|
85 | is included in the distribution. |
---|
86 | |
---|
87 | If jump.cmd is utilized as the only method by which Java Web Start is |
---|
88 | invoked, there is no configuration of this environment variable required. |
---|
89 | |
---|
90 | DO NOT change your LIBPATH. This is unnecessary and will provide no |
---|
91 | benefits. |
---|
92 | |
---|
93 | JAVAWS.CFG Considerations |
---|
94 | ------------------------- |
---|
95 | |
---|
96 | This file contains information required by Java Web Start to determine what |
---|
97 | Java runtime environment to utilize. |
---|
98 | |
---|
99 | # GCD JVM 1.4.1 |
---|
100 | javaws.cfg.jre.0.path=c:/java141/bin/java.exe |
---|
101 | javaws.cfg.jre.0.platform=1.4 |
---|
102 | javaws.cfg.jre.0.product=1.4.1 |
---|
103 | javaws.cfg.jre.0.location=http://java.sun.com/products/autodl/j2se |
---|
104 | javaws.cfg.jre.default=0 |
---|
105 | |
---|
106 | This file can be modified with any text editor, such as EPM or TEDIT. The |
---|
107 | path information should me changed to match your particular system |
---|
108 | configuration. |
---|
109 | |
---|
110 | If you intend to use IBM JVM 1.3.1, the format would be: |
---|
111 | |
---|
112 | # IBM JVM 1.3.1 |
---|
113 | javaws.cfg.jre.0.path=c:/java131/jre/bin/java.exe |
---|
114 | javaws.cfg.jre.0.platform=1.3 |
---|
115 | javaws.cfg.jre.0.product=1.3.1 |
---|
116 | javaws.cfg.jre.0.location=http://java.sun.com/products/autodl/j2se |
---|
117 | javaws.cfg.jre.default=0 |
---|
118 | |
---|
119 | Note that the path can be specified either with forward slashes (/) or double |
---|
120 | backslashes (\\). Comments are denoted with a pound sign (#). |
---|
121 | |
---|
122 | The location URL must be present, but currently there is no automated |
---|
123 | download of the JVM for the GCD JVM or the IBM JVM. If there is a mismatch |
---|
124 | between the requested JVM version in the JNLP file, and the configured JVM |
---|
125 | version, a detailed message will be displayed by Web Start indicating the |
---|
126 | failure. |
---|
127 | |
---|
128 | Workplace Shell Program Object |
---|
129 | ------------------------------ |
---|
130 | |
---|
131 | If you would like to have a program object on your desktop, which launches |
---|
132 | the Java Web Start Application Manager, you can use the javaws_icon.cmd REXX |
---|
133 | program included in the distribution. Simple answer "Y" when prompted, and |
---|
134 | it will be created with the proper path information based upon your |
---|
135 | configuration. |
---|
136 | |
---|
137 | Netscape/Mozilla Helper Application |
---|
138 | ------------------------------------- |
---|
139 | |
---|
140 | For users of Netscape or Mozilla web browsers, please set up the Java Web |
---|
141 | Start MIME type (JNLP) in the Edit->Preferences Helper Applications section. |
---|
142 | The file extension is "jnlp", the MIME Type is |
---|
143 | "application/x-java-jnlp-file", and it should be handled by the jump.cmd |
---|
144 | wrapper REXX program in your Java Web Start software directory. |
---|
145 | |
---|
146 | When using Mozilla, there is a problem with using JavaScript technology. |
---|
147 | See the http://java.sun.com/products/javawebstart/demos.html page for a |
---|
148 | demo, and also a very good tool for testing your configuration. |
---|
149 | |
---|
150 | ----------------------------------------------------------------------------- |
---|
151 | |
---|
152 | 5. Submitting Defect Reports |
---|
153 | |
---|
154 | To submit a defect report, please send an e-mail to: |
---|
155 | |
---|
156 | techsupport@goldencode.com |
---|
157 | |
---|
158 | The following information should always be included in a problem submission: |
---|
159 | |
---|
160 | * Your name. |
---|
161 | * Your organization's name (if applicable). |
---|
162 | * Your reply-to e-mail address. |
---|
163 | * The serial number of the product license. This can be obtained by running |
---|
164 | 'java -Xlicenseverify' at the command line. |
---|
165 | * A detailed description of the problem, including steps on how to |
---|
166 | recreate the error condition. |
---|
167 | * If it is possible to isolate the problem with a small test case, the |
---|
168 | test case should be attached to the e-mail, or instructions on how to |
---|
169 | download the test case. |
---|
170 | * The hotspot log file that was created when the problem was encountered, |
---|
171 | if the problem ended in a crash of the product. |
---|
172 | |
---|
173 | Some problems may be caused by underlying defects in the OS/2 operating |
---|
174 | system or other related IBM software. If a defect is found to be so caused, |
---|
175 | Golden Code has an arrangement with IBM in which the two companies can |
---|
176 | effectively work together to resolve such issues. The customer must open an |
---|
177 | IBM PMR and authorize the IBM personnel to work with Golden Code on this |
---|
178 | issue. |
---|
179 | |
---|
180 | PLEASE NOTE THAT UNLESS YOU MAKE ARRANGEMENTS TO EXCHANGE ENCRYPTED E-MAIL |
---|
181 | WITH GOLDEN CODE DEVELOPMENT, ANY E-MAIL YOU SEND IS NOT SECURE AND MAY BE |
---|
182 | VIEWED IN TRANSIT. A secure, web-based defect reporting system for the use of |
---|
183 | service clients is currently under development. We hope to have it available |
---|
184 | shortly. |
---|
185 | |
---|
186 | ----------------------------------------------------------------------------- |
---|
187 | |
---|
188 | 6. Contacting Golden Code |
---|
189 | |
---|
190 | E-mail : info@goldencode.com (general), techsupport@goldencode.com |
---|
191 | (support) |
---|
192 | Address : Suite 135, 1455 Old Alabama Rd., Roswell, Georgia, U.S.A. |
---|
193 | Phone : +1 678-352-2301 |
---|
194 | Fax : +1 678-352-2305 |
---|
195 | |
---|
196 | ----------------------------------------------------------------------------- |
---|
197 | |
---|
198 | 7. Trademarks |
---|
199 | |
---|
200 | 'Golden Code' is a registered trademark of Golden Code Development |
---|
201 | Corporation. |
---|
202 | |
---|
203 | 'IBM' and 'OS/2' are registered trademarks of International Business Machines |
---|
204 | Corporation. 'WorkSpace On-Demand' is a trademark of International Business |
---|
205 | Machines Corporations. |
---|
206 | |
---|
207 | 'Java', 'Java 2 Platform Standard Edition', and 'Java Compatible' are |
---|
208 | trademarks of Sun Microsystems, Inc. |
---|
209 | |
---|
210 | Other names referenced in this document are the property of their respective |
---|
211 | owners. |
---|
212 | |
---|
213 | ----------------------------------------------------------------------------- |
---|
214 | Copyright (c) 2002-2003, Golden Code Development Corporation. |
---|
215 | ALL RIGHTS RESERVED. |
---|
216 | ----------------------------------------------------------------------------- |
---|
217 | |
---|