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, view it using a standard Web browser (not an HTML reader), and 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.
Thank you for choosing Host Access Transformation Services (HATS). For the latest information, please visit the Host Access Transformation Services Information Center.
When running on WebSphere Application Server V6, client response time and application server performance could degrade if HATS applications repeatedly execute JSPs that invoke HATS Integration Objects. An additional symptom of this problem is more frequent garbage collection on the application server. In extreme cases, this could cause an OutOfMemory condition.
To resolve the problem, ensure that you have installed WebSphere Application Server V6.0.0.2.
The process of mapping modules to servers when installing an application on WebSphere Application Server has changed for WebSphere Application Server V6. If you install an application using the WebSphere Administrative Console and are using a Web server to serve the application, ensure that the application being installed is mapped to both the application server and the Web server during the installation process. If the application is mapped to the WebSphere Application Server only, attempts to execute the application fail with an "HTTP 404: Page Not Found" error, because the WebSphere Application Server plugin is not updated to include the installed application. Mapping the application to a Web server causes the plugin to be updated to include the application.
For additional information, refer to the following section in the
WebSphere Application Server 6.0 Information Center:
Installing application files with the console,
See step 5, "Map modules to servers."
If your HATS project is contained in an EAR project with a name that ends in .ear, the Web browser might not launch when using the Run on Server function. For example, this could happen if you migrated your HATS V5 project from CVS, and it was contained in the default HATS EAR project, HATS.ear.
To run the application, open an external browser, and access the URL of the HATS application (for example http://localhost:9080/myHATSapplication/).
You can also rename the EAR project.
When using HATS Administration on WAS V6, the management scope cannot be changed. If you attempt to change the management scope, you see the following error:
There was a problem in trying to manage the scope you selected.HATS logs the following error:
HPS5109 Hostname [your_host_name]:2809 cannot be resolved.
To avoid this problem, include HATS Administration support files in each HATS .EAR file deployed on WebSphere Application Server V6. If a BOOTSTRAP_ADDRESS other than 2809 is used on the application server, ensure that the correct bootstrap port number is included in the runtime.properties file for the adminPortNum setting.
When migrating a HATS V4 project checked out from CVS, you get an error message, and the log file reports that the habeansnlv.jar could not be deleted.
To avoid this problem, turn off EAR validation in the Studio preferences before checking out the projects from CVS. To turn off EAR validation, click Windows > Preferences > Validation, and clear the check box next to EAR Validator.
When using the Rational Studio J2EE Migration wizard to migrate a HATS EAR project, and you elect to migrate the project structure, the Problems view shows an error and several warnings, although the
Migration finished successfullymessage is issued.
The error message states:
The Project cannot be built until build path errors are resolved.
To avoid this error, do not select the Migrate Project Structure option when using the J2EE Migration wizard.
This problem should be fixed with a Rational Studio service update, V6.0.0.1.
After checking out and migrating HATS projects and EAR projects created with previous releases of HATS, the projects are at J2EE 1.3 level. You can migrate to J2EE 1.4 level using Rational Studio J2EE Migration wizard. However, at the end of the migration, sometimes you get a failure message stating that the J2EE version level migration failed.
This failure message is misleading. You can verify the success or failure of the migration by checking the J2EE levels of the migrated projects. To check the J2EE levels, highlight the project, right click, and select Properties > J2EE. Ensure that the J2EE specification level is 1.4.
This problem should be fixed with a Rational Studio service update, V6.0.0.1.
When graph data is returned from the host, it is in a string buffer. The individual points on the graph are converted to numbers and stored. An invalid number, or a blank (" "), causes a value of zero (0) to be returned. The default value of zero (0) causes invalid points to be plotted on the graph.
A new setting, setBlanksToZero, was added to the graph widgets. This new setting can be used for horizontal bar graphs, line graphs, and vertical bar graphs.
Setting the value to true substitutes a zero (0) for any blank encountered in the host component when the graph is added to the transformation. Setting blanks to zeros skews the range of the graph unless the other values in the graph are close to zero (0).
The default value of the setBlanksToZero setting is false, so that blanks are left as they are in the data. Therefore, unless you want to replace blanks with zeros in your transformation, no action is required.
To enable this function, edit the source of your transformation.jsp file in the HATS Studio. Locate the <HATS:Component> tag for the particular widget (horizontal bar, line, or vertical bar graph), and add the following to the end of the widgetSettings attribute:
setBlanksToZero:true|
When you insert a selection list or function key component rendered with a link or radio button widget into a transformation, the text of the component might wrap. You can highlight the widget and resize as desired.
When using the visual table recognition option to recognize subfile screens, some data records might appear to be missing. This occurs when the data records do not have the same table structure as the other subfile data records (for example, rows without an action input field in the column where other subfile data records have an action field).
To avoid this problem, use the field or field table recognition option for the screen.
When a table or subfile component is inserted into a transformation, it might disappear in the Design view after you drag-and-drop and resize the component in the free layout table. This is a RAD v6.0 Page Designer problem.
To overcome this problem, set the width of free layout table to be larger than the width of subfile or table component after insertion.
When the end delimiter of Action items is a space, the description of the Action items can be truncated, if it contains multiple words. For example, for the action list:
Options: 2=Approve 4=Not Approved 5=Displaythe action drop-down list is rendered as
{2=Approve}, {4=Not}, {5=Display}
Note that "4=Not Approved" is rendered as only "4=Not".
When creating a transformation with the the New Transformation wizard, if you select the option to prepopulate the transformation with the default rendering, the resulting transformation does not use either the subfile V5 component nor the field table component to recognize the screen, even if these components are configured in the default rendering set. Instead, the transformation uses the next components in the default rendering set to recognize the screen, and renders the screen with the widgets associated with those components.
Rational Studio enables you to add Web features to existing Web projects by viewing the properties dialog and selecting listed Web features (highlight the Web project, right click, and select Properties).
Although HATS is listed as a Web feature, adding it to an existing Web project is not supported. If you want to create a Web Project that contains HATS, click File > New > Project, and select HATS Project.
If you create a new project for a server that is already running, and you use the Run On Server function, you might get an "HTTP 404: File Not Found" error.
If you double click on the server in the server view, the following message is issued:
WebSphere Server Warning Some project entries defined in the server configuration are not valid. Do you want the editor to fix the project entries automatically?If you select Yes, save the configuration, and restart the server, both applications run.
When creating or editing personal certificates in JKS, JCEKS, or PKCS12 keyring files using the certificate management utility, you might see a tool tip indicating that you are viewing a "List of personal certificates. Default indicated with *.".
This tip is incorrect for these types of keyring files; with these formats, you cannot select a default personal certificate. The tool tip should simply state that you are viewing a "List of personal certificates".
You can not start a new HATS application instance while passing in any COMMAND parameter. Instead of starting a new application, the end user gets a Disconnected page indicating that the application ended due to inactivity. The end user can restart the application by clicking Restart.
In some situations, you might prefer to automatically start a new application instance programmatically, even if the application has timed out. A new parameter enables the HATS application designer to indicate that a new instance should be started by adding the parameter to the HTTP request sent to the server. The new parameter is allowStartWithCommand, and the only valid value is true.
For a GET request, add the parameter to the query string as follows:
http://myServer/myApp/entry?COMMAND=refresh&allowStartWithCommand=true
For a POST request from a form, use this coding:
<form action="entry" method="post">
<input type=hidden name="allowStartWithCommand" value="true"/>
<input type=submit value="GO"/>
<input type=hidden name="COMMAND" VALUE="refresh"/>
</form>
If the HATS application is still active or there is no COMMAND parameter, the new parameter has no effect.
Although HATS has included support for a number of host features, the following host features are not supported by HATS:
In addition, manipulation (click-and-drag) of the ENPTUI scrollbar slider button is only supported on the Internet Explorer browser.
This error can occur when you try to create a Web service in a new workspace. You should create and start the server before starting the Web service wizard.
To view this information, open the Rational Software Development Platform help and search for the text "Creating a Web service from a Java bean."
If your HATS project is contained in an EAR project with a name that ends in .ear, the Rational Studio Web service wizard seems to hang, and then fails with
Could not restart server.For example, this could happen if you migrate your HATS V5 project from CVS, and it was contained in the default HATS EAR project, HATS.ear. After this occurs, all of the artifacts necessary for working with a Web service have been created.
Ensure that the application has been published properly to the server, and then test the Web service.
This problem should be fixed with a Rational Studio service update, V6.0.0.1.
If you look at the Rational Studio log after a HATS project has been deleted, you might see the following:
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.runtime".
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:2691)
at org.eclipse.swt.SWT.error(SWT.java:2616)
at org.eclipse.swt.SWT.error(SWT.java:2587)
at org.eclipse.swt.widgets.Widget.error(Widget.java:381)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:283)
at org.eclipse.swt.widgets.Table.getSelection(Table.java:1315)
at org.eclipse.swt.custom.TableTree.getSelection(TableTree.java:324)
at org.eclipse.jface.viewers.TableTreeViewer.getSelection
(TableTreeViewer.java:320)
This exception does not affect any HATS functions.
When using HATS Studio to build Model 1 or Struts Web pages from HATS Integration Objects, you might see a NoClassDefFoundError for com.ibm.HostPublisher.IntegrationObject.HPubHODCommon. Although this message is flagged as an error, the Web pages still execute without problems.
When creating a HATS EJB Project, the following pop up might appear:
Deployment of EJB016EJB did not complete successfully due to the following error: java.lang.IllegalStateExceptionAfter creating EJB Project, the EJB tooling API creates the Deployment code, and sometimes the code fails.
If you receive this message during creation of a HATS EJB project, use the Deploy menu item on the context menu for the project in the HATS Studio Navigator view to create the deployment code for the EJB project. Highlight the project, right click, and select Deploy.
When you open HATS Administration in WebSphere Portal, the portlet containing the HATS Administration Console is not listed.
You can administer all the portlets by using the Administration Console of a portlet that you are not trying to manage.
Another option is to create a separate HATS Administration application to administer the portlets.
HATS Administration Console does not run in a secure portal environment. The reason for this is that HATS Administration Console defines security roles, but WebSphere Portal does not enable mapping of users or groups to the security roles.
When you attempt to access HATS Administration Console after deploying a portlet on a the portal server, the server attempts to authenticate the user because of the security defined for the portal. However, authentication fails because the security roles authorized to access the Administration Console have not been mapped to any users.
When subsequent portlets are added to the PortletEar after an initial portlet has been run on the Portal server in the test environment, you might see a blank page when running the subsequent portlet.
To avoid this problem, delete the Portal server configuration and restart the Portal server.
A HATS portlet with text replacement does not work on the WebSphere Portal V5.0 test environment. If you want to include text replacement within your portlet and want to test the project internally, you can create a HATS project and test it on the WebSphere 5.1 test environment before generating a portlet from the HATS project.
There should not be any problems when the portlet is deployed externally.
If you are viewing the documentation when you try to uninstall HATS, you might see the following error message:
An error occurred and product uninstallation failed.
If you look in the hatsuninstall.log, you can see that a directory is being deleted, but the deletion is accompanied by the message:
The directory is not empty.This means that the directory is still in use; it is active.
If you see the message that the uninstallation failed, continue through to the end of the uninstallation. Reboot the machine and delete the HATS installation directory to ensure a clean uninstallation.
Internet Explorer is the only browser supported for the Thai language
Thai column realignment is not available on iSeries Access for Web 5250 Print support
Some characters are displayed incorrectly in the Internet Explorer browser because the SimSun 18030 font (simsun18030.ttc) in the Microsoft GB18030 support package does not have the complete GB18030 repertoire.
For more information about GB18030 support, please refer to http://www.microsoft.com/globaldev/DrIntl/columns/015/default.mspx#Q25.
When you create a new project, and use the Navigator view to read the runOnServer.properties file, the DBCS characters are displayed incorrectly. The DBCS characters in a .properties file should be local MS Windows encoding, such as SHIFT-JIS or BIG5.
If you select the runOnServer.properties file in the Navigator view using File > Properties, and change the encoding from ISO-8859-1 to correspond to the MS950 encoding for Windows 2000, the .properties file displays the DBCS characters correctly.
Note: When you are finished viewing the file, be sure to reset the encoding to ISO-8859-1 so the system can read the file. Do NOT save the runOnServer.properties file with the changed encoding.
When generating a Web service on a DBCS system, the WSDL is created with incorrect encoding resulting in the following error:
IWAB0639E Error in generating Java files and deployment descriptors from WSDL file
java.io.UTFDataFormatException: Invalid byte 1 of 1-byte UTF-8 sequence.
at org.apache.xerces.impl.io.UTF8Reader.invalidByte(Unknown Source)
at org.apache.xerces.impl.io.UTF8Reader.read(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.scanLiteral(Unknown Source)
at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanAttribute(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:460)
at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:505)
at com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:445)
at com.ibm.ws.webservices.wsdl.Parser$WSDLRunnable.run(Parser.java:293)
at java.lang.Thread.run(Thread.java:813)
In the Navigator view, you will see an error icon on the WSDL file.
The WSDL file has been saved with native encoding, and Rational Studio opens it
using UTF-8.
To avoid this error, change the encoding of the WSDL file to UTF-8.
To display the Korean Won sign correctly in the Internet Explorer browser, you need to change the template used by the project and use the font that supports the Korean Won sign display (for example, set "font-family: GulimChe;" in the corresponding style class).
When using regular expression support for Korean text replacement, you cannot use a space character as part of the replacement text.
If you select the Match with screen reverse option, replacing text with HTML is not affected by screen orientation. However, replacing plain text (without HTML) is affected by screen orientation and is reversed along with the rest of the screen content.
The URL component is supported only in Left-to-Right screens. If a URL component is recognized on a Left-to-Right screen, the URL is highlighted as a link on the transformed page. The link to the URL opens the Web page for the URL, whether the user has reversed the screen or not.
However, if the URL component is recognized on a Right-to-Left screen, the URL is saved in a reversed format, such as moc.ibm.www\\:ptth. In this case, the URL is not highlighted on any screen, whether the user has reversed the screen or not, and the link does not open any Web page for the URL in reversed format.
This problem occurs when text replacement is added while using the Insert Host Component wizard. If you do the following:
To enable bidirectional characters to be entered, manually change the keyboard layer language from English to the bidirectional language.
In the "Enabling display terminal for HATS on iSeries" section of Appendix A. Enabling graphing support and display terminal on iSeries, the HATS Getting Started for iSeries manual discusses the use of Remote AWT Abstract Windowing Toolkit (RAWT) for enabling the display terminal on OS/400 Version 5 Release 2 (V5R2).
For OS/400 Version 5 Release 3, RAWT is not supported. The HATS Getting Started for iSeries manual suggests that Native AWT (NAWT) be used for graphics operations and display.
Note: RAWT and NAWT are mutually exclusive.
NAWT is now the suggested mechanism for enabling display terminal for HATS on iSeries for both OS/400 V5R2 and V5R3, as well as for enabling graphics support. Use NAWT to provide your Java applications and servlets with the full capability of the Java 2 Software Development Kit's (J2SDK), Standard Edition AWT graphics functionality. RAWT, due to its excessive overhead, should be not be used when NAWT functionality is available using J2SDK 1.4 on iSeries.
To use NAWT for enabling display terminal, follow the two lists of steps described in the "Alternative method of enabling graphics support for HATS on iSeries" section. However, in step 16 of the second list of steps, use the OS/400 V5R3 property names for both releases.
You can view display terminal sessions using one of the following methods:
where hostname is the hostname of the WebSphere server. Using either method, use the VNC password created in step 6 of the first list of steps in the "Alternative method of enabling graphics support for HATS on iSeries" section.
In the "Multiple SSL CA certificates in a single EAR file" section of Chapter 17. Security and Web Express Logon, the HATS User's and Administrator's Guide lists the path to the gencert command. The path is not correct.
The text should read:
"To ensure that each SSL connection works at runtime:
In the "Related HATS Settings" section of Appendix A. HATS screen-settling reference, the HATS User's and Administrator's Guide describes the use of the negotiateCResolution contention resolution setting, but it does not mention that the setting appears in the table of advanced connection settings on the Advanced tab of the Connection Editor. The setting is only used when the host type is TN3270E. The default value for the setting is true. If you want to modify the value, edit the setting and change the value to false.
Note: The negotiateCResolution setting is added to the advanced connection settings table on the Advanced tab of the Connection editor by the New Project wizard or the New Connection wizard for projects with TN3270E connections. The setting does not appear in projects or connections that are migrated from HATS V5.
In the "$HMLSQLUtil$" section of Chapter 9. Variables and imported Java classes, the HATS Advanced Macro Guide describes the use of the HMLSQLUtil macro variable, but has several incorrect references to HMLSessionUtil. The title and the header of the Method Summary table, as well as the examples for the methods, reference $HMLSessionUtil()$.
The references to $HMLSessionUtil()$ should be $HMLSQLUtil()$.
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.