This file contains information that became available too late for inclusion in the publications or the help. This file also contains important support information.
Note: To use the HTML links in this document, you must view it using a standard Web browser (not an HTML reader), and you must be connected to the Internet. Some links will open a different document or Web page. Use your browser's Back button to return to this document.
For installation instructions, please refer to HATS LE Getting Started. Note these additions to the installation instructions:
Because of similarities in Java class names between HATS LE and standard HATS applications, a HATS LE and a HATS application cannot run at the same time on the same application server instance when the server instance's classloader policy is set to "Single" on Version 5.0 or "Server" on Version 4.0 AE/AEs. Please refer to your WebSphere Application Server documentation for information on changing your server instances's classloader policy to "Multiple" on Version 5.0 and to "Application" on Version 4.0 AE/AEs.
In some cases, log files (created while running your application with runtime tracing turned on) are not deleted when uninstalling your HATS LE application. To avoid this problem, before uninstalling your application, completely stop the application server instance where the HATS LE application is running. If these files still exist after uninstalling your HATS LE application, manually delete them (including the "HATSLE.ear" directory under the "installedApps" directory) before reinstalling HATS LE.
If you choose to have HATS LE assign workstation ID values based on a string you supply, be sure to include an equal sign (=) before the wild-card character. For example, if you specify ABC* (without an equal sign) as the string from which workstation IDs will be created, HATS LE cannot always assign unique workstation IDs. If you specify ABC=*, HATS LE will assign unique workstation IDs.
After configuring your application to use an SSL certificate (either the first time you configure the application or if you switch to a different certificate on a subsequent configuration), you will need to stop and restart your application. This is because SSL certificates are stored in a JAR file which may not get picked up by your application server without restarting your application.
Warning: Depending on how your application server is configured for class reloading, your application may automatically restart when you change your SSL certificate. This is because the SSL certificate is stored in a JAR file that the application server is monitoring for changes. When a change occurs, the application server may restart your application to pick up this change. This process will disconnect any users currently using your application.
If you discover that after having selected an SSL certificate and clicked Finish in the Configuration Wizard, the certificate is not being used when you access your application, follow these steps:
You can select which connection parameters can be overridden by your end user in the URL with which they access your HATS LE application.
To configure URL connection parameter overriding, edit the application.hap application settings file. You can edit this file from the Advanced section in the HATS LE Administrative Console. Edit the following section, under the <classSettings> section of the <application> section:
<class name="com.ibm.hats.SessionOverride">
<setting name="prop1" value="true|false" />
<setting name="prop1" value="true|false" />
</class>
Where "prop1" and "prop2" are the names of valid HOD session properties. Please refer to HATS LE Getting Started for more information about the application settings file. All attribute names in the <session> tag of the application.hap file are also valid HOD property names, except for "workstationIDSource". For example, to allow your end users to override the host to which your HATS LE application connects, add the following:
<setting name="host" value="true" />
<setting name="allowAll" value="true" />
<class name="com.ibm.hats.SessionOverride">
<setting name="allowAll" value="true" />
<setting name="host" value="false" />
</class>
If you configure your application to enable your users to override parameters, your end users can then supply these parameters in the initial request they make to your application. For example, to override the host and port number, assuming you have enabled overriding of these parameters, a user could enter this string into his browser:
http://servername/HATSLE/entry?host=mysecondary.host.com&port=992
In cases where you expect to receive non-ASCII input from your users (either in the Configuration Wizard, Administrative Console, or when accessing your HATS LE application), you will need to enable UTF-8 encoding on your application server. For more information on how to configure your application server to support UTF-8 encoding, refer to your WebSphere Application Server infocenter.
For example, here are the steps for WebSphere Application Server Version 5:
You cannot use double-byte characters in the name of any uploaded file, such as an image, stylesheet, or security certificate. If you want to use a file with double-byte characters in its name, rename the file to eliminate any DBCS characters from the file name before you upload the file.
In the Manage Sessions section of the Administrative Console, you can see the IP address of each client that is connected to your HATS LE application (to view, click a session ID from the list of active sessions). In cases when clients connect through the IBM HTTP Server, as opposed to accessing your HATS LE application directly on your application server, the Session Details dialog might show only the IP address, not the fully resolved host name. To see the client host name, open the httpd.conf file in your IBM HTTP Server "conf" directory and add/edit the following: HostnameLookups on. You will need to stop and restart your HTTP server for this change to take affect. This will instruct the HTTP server to do a DNS lookup on the client IP address and determine its host name. Note: Making this change will cause a slight performance degradation, because the HTTP server will have to resolve the IP address before passing the client's request to the application server.
To import your HATS LE project into HATS, you must apply HATS fix pack 4.0.2 or later. Visit the WebSphere Host Access Transformation Server support page to learn about and access support downloads.
While most unprotected entry fields on host screens are empty, some host applications may fill entry fields with underscores (_) or occasionally with periods (.). Although emulator screens have control over whether the cursor is in input or overwrite mode, HTML always places the cursor into insert mode. Because of this, users may occasionally need to manually select overwrite mode. Users of Internet Explorer can use the Insert key to change to overwrite mode. In Netscape, the Insert key does not change the mode, so users can use the Delete key to delete text to be replaced, or highlight the text with the mouse before typing the new text.
HATS LE applications use standard HTML INPUT fields to render unprotected host fields, but HTML does not provide control over the cursor position within these fields. Host screens usually place the cursor at the beginning of an unprotected field, but some do not. HATS LE renders the unprotected field by placing the cursor at the beginning of the field instead of at the host-indicated cursor position. You may need to click on the correct location within such fields to place the cursor at the desired location.
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
Pentium is a trademark of Intel Corporation in the United States, other countries, or both. (For a complete list of Intel trademarks see http://www.intel.com/sites/corporate/tradmarx.htm.)
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. SPARC is a trademark of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, and Windows NT are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.
Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.