Rational Host Access Transformation Services 9.0 - Known issues and workarounds

Product documentation


Abstract

The tables below identify considerations for Rational Host Access Transformation Services (HATS) concerning known issues and workarounds in 9.0.

Content

Table of Contents:



Web browser considerations

The tables below identify web browser considerations for HATS.

Common considerations
  1. When using the Automatic Disconnect and Refresh functions, for optimal results, use the Enable client pull (AJAX) option. If you continue to use the Enable server push (applet) option, Internet Explorer is the recommended browser. Other browsers will work with the HATS applet provided the ie applet setting is not specified as local and the time to wait for disconnect setting is sufficiently large. For more information about the HATS Automatic Disconnect and Refresh functions, see the HATS User's and Administrator's Guide.
  2. The HATS Automatic Disconnect and Refresh option, Enable server push (applet), does not function properly on Macintosh with any supported browser, nor on Windows using Safari. Use the Enable client pull (AJAX) option instead. For more information about the HATS Automatic Disconnect and Refresh functions, see the HATS User's and Administrator's Guide.
  3. The box around a radio button might not display completely. To work around this, remove the following line from the HATSTABLE style in the template style sheet:

    border-collapse: collapse;

Firefox
  1. The overwrite mode client setting is not supported.
  2. The HATS Dojo Enhanced grid widget might not display correctly the first time with WebSphere Application Server V8.0. To work around this, enable HTTP compression in the project settings. Or, if using a remote Dojo location hosted on a public Content Distribution Network (CDN), try using a local Dojo installation.
  3. When typing an underscore (_) character into a screen transformation, it displays as a dash (-) and advances the cursor to the next field on the screen. To work around this, modify the HATS KBS.js file so that Alt-Minus (instead of Shift-Minus) maps to quick field minus. For information about how to remap the keyboard, see the HATS User's and Administrator's Guide.
Internet Explorer
  1. When accessing a HATS portlet using Internet Explorer V6, V7, and V8, after you press the Enter key, the cursor moves to the portal Page tab. You must press the Tab key to tab to the next input field on the HATS portlet page.
  2. With Internet Explorer V7, portlet overlays occur when scrolling between two side-by-side HATS portlets that use either the Industry or Transport templates. As a workaround, add the following statements to the HEAD section of the Industry.jsp or Transport.jsp files as appropriate:


    <!--[if IE 7]>
    <style type="text/css">
    .ibmLayoutContainers{position:relative;}
    </style>
    <![endif]-->

  3. If your HATS screens do not function as expected using Internet Explorer V9, either enable the browser for compatibility mode, or try another browser. To enable compatibility mode, select Tools > F12 developer tools. In the displayed window select Browser Mode: IE9 and select  Internet Explorer 9 Compatibility View.
  4. Dojo widgets do not display correctly when using a project name or Dojo path that includes non-English characters. To correct, use a public Content Distribution Network (CDN) to access Dojo.
  5. When accessing applications optimized for mobile devices with Windows Mobile Internet Explorer, the automatic field advance, keyboard host key support (using a keyboard as a normal web keyboard), overwrite mode, and asynchronous update applet browser functions are not available.
  6. The host and application keypads do not work correctly with Windows Mobile V6 and WebSphere Application Server V8.0. To correct, upgrade to Windows Mobile V6.1.4, or later.
Konqueror
  1. The overwrite mode client setting is not supported.
  2. The function keys (F1 - F24) and the PageUp and PageDown keys on the keyboard do not perform any function for HATS. To enable the use of these keys in your applications, include a host keypad with these keys to enable the user to send them to the host.
  3. Using the keyboard support and pressing the Enter key might interact incorrectly with the host application. To correct this, include a host keypad with the Enter key.
  4. The automatic field advance function is not supported for password fields.
Opera
  1. The overwrite mode client setting is not supported.
  2. The function keys (F1 - F24) and the PageUp and PageDown keys on the keyboard do not perform any function for HATS. To enable the use of these keys in your applications, include a host keypad with these keys to enable the user to send them to the host.
  3. The Tab key cannot be used to focus on the Calendar widget launcher if the launcher is defined as an image or link.
  4. When typing an underscore (_) character into a screen transformation, it displays as a dash (-) and advances the cursor to the next field on the screen. To work around this, modify the HATS KBS.js file so that Alt-Minus (instead of Shift-Minus) maps to quick field minus. For information about how to remap the keyboard, see the HATS User's and Administrator's Guide.
Safari
  1. The overwrite mode client setting is not supported.
  2. Keyboard support is limited to the Pause ([attn]) and Esc ([clear]) keys. For applications that run in Safari browsers, consider including a host keypad with all the keys to enable the user to send the keys to the host.
  3. By default the Tab key cannot be used to focus on the Calendar widget launcher if the launcher is defined as an image or link. By default keyboard navigation is not enabled, and the Tab key focuses only on inputs and button elements. To enable this function, in the advanced preferences, select the option, Press Tab to highlight each item on a webpage.
  4. When using a Macintosh Safari browser, sometimes the Enter key appears not to function properly. This problem occurs when the web page being viewed does not contain any edit controls such as a button or text edit field. To correct this, do the following to enable the host keypad and provide a GUI Enter key:
    1. Double-click the project settings document to bring up the Project Settings editor.
    2. Click the Rendering tab.
    3. On the left side of the Rendering panel is a tree view of the rendering options, click the Host Keypad option.
    4. Select the Show default host keypad check box.
    5. Select the check box for each key you want to enable.
    6. You must select the Enter key.

    Once this is done and the application is rebuilt and deployed, the Enter key is available as part of the template used to present the HATS application.

  5. When using Windows 7 and a HATS template with a black background, down arrows for drop-down lists are not visible. To correct, change the background color of the drop-down list to a color other than black.
  6. When using the Windows 7 classic theme, drop-down lists display a blank gray button with no arrow. This is due to a problem whenever a cascading style sheet (CSS) background-color or border-color rule is applied. To correct, remove these rules.


64-bit considerations

The table below identifies 64-bit considerations for HATS.

64-bit considerations
  1. The Java Visual Editor feature of the Rational Software Delivery Platform products is not supported and not installable in the 64-bit environment.
  2. Printing to the native Windows printer is not supported in the 64-bit environment.


Portlet considerations

The table below identifies portlet considerations for HATS.

Portlet considerations
  1. The preview function of the transformation editor does not apply style sheets for portlet projects.
  2. To install a stand-alone HATS administrative console application used to administer HATS portlets created for WebSphere Portal V8, using the WebSphere Application Server administrative console, install the HATS administrative console application .ear file to the WebSphere_Portal server (not to server1). After installing, the URL to access the HATS administrative console is: http://<portalhostname>:<portalruntimeport>/<hatsadminappname>/hatsadmin/admin.
  3. To install a HATS IBM portlet that includes the HATS administrative console used to administer HATS portlets created for WebSphere Portal V8, using the WebSphere Portal Server administrative console, install the HATS IBM portlet .war file. After installing, the URL to access the included HATS adminstrative console is: http://<portalhostname>:<portalruntimeport>/wps/PA_value;/hatsadmin/admin, where PA_value is normally PA_<hatsportletname>. For how to determine the PA_value, see Administering Host Access Transformation Services (HATS) Portlets.
  4. For more information about administering HATS portlets, see Administering Host Access Transformation Services (HATS) Portlets.


Apache Geronimo considerations

The table below identifies Apache Geronimo considerations for HATS.

Apache Geronimo considerations
  1. Only one HATS web application is supported per .ear file running on an Apache Geronimo server.
  2. To support DBCS and bidi character sets, you must use an encoding filter. For an example, see Default encoding in Geronimo with Tomcat.
  3. To start multiple instances of your HATS web application running on an Apache Geronimo server in the same browser using tabs, you must enable URL rewriting. To do this you must disable cookies for the HATS web application as follows. For more information about how URL rewriting works with HATS, see Unable to open multiple HATS sessions on Microsoft Internet Explorer 8.

    1. In Rational SDP open the Navigator view.
    2. Expand your HATS web application project.
    3. Expand the Web Content folder and then the WEB-INF folder.
    4. Double-click the geronimo-web.xml file to open the editor.
    5. Click the Source tab.
    6. After the </web:context-root> tag, add the following values:

      <web:container-config>
         <tomcat:tomcat xmlns="http://geronimo.apache.org/xml/ns/web/tomcat/config-1.0"
                 xmlns:tomcat="http://geronimo.apache.org/xml/ns/web/tomcat/config-1.0">
          <disable-cookies/>
         </tomcat:tomcat>
      </web:container-config>


    7. Save the file and redeploy the HATS web application to the Geronimo server.

  4. If you start the Geronimo server from the command line instead of using the Rational SDP local test environment, you may get the error message:

    java.lang.OutOfMemoryError: PermGen space

    To correct this issue, do the following steps:
    1. Edit the .bat or .sh file that starts the server.
    2. Add this statement to the file,

      set JAVA_OPTS=-Xmx512m -XX:MaxPermSize=512m

    3. Note: For a discussion about this error, see java.lang.OutOfMemoryError: PermGen space.
  5. When using the Debug on Server function in the local test environment, if you change a Java file in your project, you may get the following type exception in the console:

    java.lang.Exception: AspectJ5 does not weave hotswapped class (screenComboGer/widgets/CustomField).

    To turn off AspectJ5 and avoid these exceptions, modify the config.xml file found in the var/config folder of the Geronimo install and change this line:

    <module name="org.apache.geronimo.configs/aspectj/2.2.1/car"/>

    to this:

    <module name="org.apache.geronimo.configs/aspectj/2.2.1/car" load="false"/>.

  6. If you run Geronimo in the Rational SDP local test environment in debug mode, then stop and try to run it in non-debug mode, the server may not start with any of the following exceptions:

    ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason:
    java.io.EOFException: Chunk stream does not exist at page: 0
    java.io.EOFException: Chunk stream does not exist at page: 0
    .

    ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state:
    abstractName="org.apache.geronimo.configs/activemq-broker/2.2.1/car?
    ServiceModule=org.apache.geronimo.configs/activemq-broker/2.2.1/car,j2eeType=JMSServer,
    name=DefaultActiveMQBroker"
    java.io.EOFException: Chunk stream does not exist at page: 0
    .

    Server Startup failed
    org.apache.geronimo.kernel.config.LifecycleException: start of
    org.apache.geronimo.configs/activemq-broker/2.2.1/car failed
    .

    This problem appears to be due to the version of one of the components in Geronimo called ActiveMQ. For a discussion about this issue, see Problem starting Geronimo (ActiveMQ).

    The solution is to turn off the Job Scheduler support for ActiveMQ. This can be done by modifying the var/activemq/conf/activemq.xml file and adding schedulerSupport="false" to the line below:

    <broker xmlns="http://activemq.apache.org/schema/core"
    brokerName="${activemq.brokerName}"
    tmpDataDirectory="${activemq.data}/tmp_storage" useShutdownHook="false"
    start="false">

    so it looks like this:

    <broker xmlns="http://activemq.apache.org/schema/core"
    brokerName="${activemq.brokerName}"
    tmpDataDirectory="${activemq.data}/tmp_storage" useShutdownHook="false"
    start="false" schedulerSupport="false">

  7. The HATS administrative console is not supported.


Oracle WebLogic Server considerations

The table below identifies Oracle WebLogic Server considerations for HATS.

Oracle WebLogic Server considerations
  1. Only one HATS web application is supported per .ear file running on an Oracle WebLogic Server.
  2. To start multiple instances of your HATS web application running on an Oracle WebLogic Server in the same browser using tabs, you must enable URL rewriting. To do this you must disable cookies for the HATS web application as follows. For more information about how URL rewriting works with HATS, see Unable to open multiple HATS sessions on Microsoft Internet Explorer 8.

    1. In Rational SDP open the Navigator view.
    2. Expand your HATS web application project.
    3. Expand the Web Content folder and then the WEB-INF folder.
    4. Double-click the weblogic.xml file to open the editor.
    5. In the left panel, click on Session.
    6. Select the Enable URL rewriting for session tracking box.
    7. In the left panel, expand the Session section and click on Cookies.
    8. Deselect the Enable cookies box.
    9. Save the file and redeploy the HATS web application to the WebLogic Server.

  3. HATS supports web services only when using the Apache Axis runtime on WebLogic.
  4. For information about installing Oracle WebLogic Server Tools, see Installing Oracle WebLogic Server Tools in Application Developer 9.0 for HATS 9.0 results in an incomplete installation.
  5. If security is enabled in WebLogic Server, the HATS administrative console does not function if deployed as-is. You can choose to disable security in HATS or in WebLogic Server, or map HATS roles to WebLogic Server users to run with security.

    Use the following steps to disable security in HATS:

    1. In the Navigator view, expand the HATS web application project.
    2. Open the /Web Content/WEB-INF/web.xml file in the editor.
    3. Click the Source tab and remove or comment the following statements:
      <auth-constraint>
      <description>
      HATS Admin:+:</description>
      <role-name>HATSAdministrator</role-name>
      <role-name>HATSOperator</role-name>
      <role-name>HATSMonitor</role-name>
      </auth-constraint>

    Use the following steps to map HATS roles to WebLogic Server users:

    1. Create a new user using the WebLogic Server administration console or use an existing user.
    2. In the Navigator view, expand the HATS web application project.
    3. Open the /Web Content/WEB-INF/web.xml file in the editor.
    4. Click the Source tab and add the following statements after </wls:container-descriptor>:
      <wls:security-role-assignment>
      <wls:role-name>HATSAdministrator</wls:role-name> //HATS role
      <wls:principal-name>XXXXXXX</wls:role-name> //WebLogic user
      </wls:security-role-assignment>

    Note: Enabling security is needed to administer remote HATS applications in the WebLogic Server using the admin management scope. As documented in the WebLogic default security policy runtime/domain service MBeans, all the roles are allowed to access all the operations in the HATS administrative console. Refer to The WebLogic Server MBean Reference for more details.

  6. By default, Management scope is selected for the .ear file of the HATS application that includes the HATS administrative console. You can change the scope of management to manage other HATS enterprise applications deployed within the same server in the WebLogic domain. It is not possible to access HATS applications outside the server in which HATS administrative console is deployed.
  7. HATS administrative console for Weblogic Server is not supported on z/OS.
  8. Only one HATS administrative application is supported per .ear file running on Weblogic Server.



WebSphere Liberty Profile considerations

The table below identifies WebSphere Liberty Profile considerations for HATS.

WebSphere Liberty Profile considerations
  1. Only one HATS web application is supported per .ear file running on a WebSphere Liberty Profile Server.
  2. To start multiple instances of your HATS web application running on a WebSphere Liberty Profile Server in the same browser using tabs, you must enable URL rewriting. To do this you must disable cookies for the HATS web application as follows. For more information about how URL rewriting works with HATS, see Unable to open multiple HATS sessions on Microsoft Internet Explorer 8.

    1. In Rational SDP open the Servers view.
    2. Expand the WebSphere Application Server Liberty Profile server.
    3. Double-click the Server Configuration [server.xml] file to open the editor.
    4. In the Configuration Structure section, click Add.
    5. Select HTTP Session from the list and click OK.
    6. In the Configuration Structure section, select HTTP Session.
    7. Select the Enable URL rewriting box.
    8. Deselect the Enable cookies box.
    9. Save the file and redeploy the HATS web application to the WebSphere Liberty Profile server.

  3. The HATS administrative console is not supported.


HATS Dojo widget considerations

The tables below identify HATS Dojo widget considerations.

Common considerations
  1. Dojo widgets are supported only in HATS Web applications. They are not supported in the following HATS applications:
    • Mobile device
    • Portlet
    • Rich client
  2. Dojo widgets are not supported with the following HATS functions:
    • Alternate rendering
    • Default rendering
    • Global rules
    • Screen combinations
    • HATS tabbed folders
  3. Dojo widgets are supported for HATS Web applications accessed from iPad devices, subject to the considerations mentioned in iPad support considerations.
  4. For Internet Explorer, Dojo widgets do not display correctly when using a project name or Dojo path that includes non-English characters. To correct, use a public Content Distribution Network (CDN) to access Dojo. For more information, see http://bugs.dojotoolkit.org/ticket/12207.
  5. Dojo elements encompassing large areas of a host screen may not fit into desired layouts. If multiple component elements within a single component creates a problem for your layout, consider specifying smaller host screen regions to lay out individual component elements.
  6. For information about customizing HATS Dojo widgets, see the HATS Web Application Programmer's Guide.
Combo box widget
  1. Hidden fields, for example, password fields, are rendered as regular fields. To render as hidden fields, use other HATS widgets, or create your own widget.
Date text box widget
  1. The Dojo date locale must be the same as the operating system locale. If different, the following JavaScript error message is displayed: Bundle not found: validate in dijit.form, locale=xx
  2. In the HATS widget settings window, the tab key does not move focus from the preview panel to the settings panel. See http://bugs.dojotoolkit.org/ticket/11995. This problem is fixed in Dojo 1.6.
  3. For Internet Explorer V8 the use of a prompt message might prevent you from selecting a date from the calendar date picker. See http://bugs.dojotoolkit.org/ticket/12020. This problem is fixed in Dojo 1.6.
  4. Various problems exist with date pattern specification, date selection, and date display. See http://bugs.dojotoolkit.org/ticket/11958. These problem are fixed in Dojo 1.7.
  5. The prompt message displays even after valid data is entered. See http://bugs.dojotoolkit.org/ticket/12157. This problem is fixed in Dojo 1.7.
Enhanced grid widget
  1. The Enter key does not work when focus is on a cell or row of the Dojo Enhanced grid widget. Typically, when the Enter key is pressed, the JavaScript KeyDown event of HATS is invoked. However, if the screen focus is on a cell or row of the Enhanced grid widget, the KeyDown event of Enter key is handled by the Enhanced grid widget itself. Other keys, such as ESC, F1, F2, and so on, work with HATS when focus is on a cell or row. Only the Enter key is consumed. If focus is on a column, the Enter key works with HATS.
  2. For Internet Explorer V8, when the mouse is used to click the arrow to sort ascending, descending, or remove, you must click the arrow more than once. The mouse must display as a hand for sorting to occur. Also, to select and drag a row to a different row in the table, you must first select the row and then separately drag it. In other words, you might not be able to select and simultaneously drag the row. To work around these problems, edit the project template and change the DOCTYPE statement as shown below:

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
  3. Sorting of columns is based on simple string comparison. Therefore some strings, for example, date strings of format mm/dd/yy, do not sort as expected.
  4. The row selector is displayed differently depending on the level of Dojo and the theme.
  5. The position of the vertical column separator is incorrect after using it to resize a column. See http://bugs.dojotoolkit.org/ticket/11943. This problem is fixed in Dojo 1.6.
  6. This widget displays blank data if placed in a center aligned container. See http://bugs.dojotoolkit.org/ticket/12091. This problem is fixed in Dojo 1.6.
  7. When using the Dojo Enhanced grid widget in the Dojo TabContainer widget that is included with the Rational Software Delivery Platform v8.5 products, the Dojo Enhanced grid widget does not render the screen data correctly in preview and runtime. This problem occurs when using Dojo Toolkit 1.6 and later. Currently there is no workaround. To avoid this problem, use Dojo Toolkit 1.4 or 1.5 in the HATS project..

Filtering select widget
  1. Hidden fields, for example, password fields, are rendered as regular fields. To render as hidden fields, use other HATS widgets, or create your own widget.
Text box widget
  1. If you see a label displayed above the input field, you can adjust the width on the <td> tag containing the field in the source to get the desired rendering of the field.
Validation text box widget
  1. The prompt message displays even after valid data is entered. See http://bugs.dojotoolkit.org/ticket/12157. This problem is fixed in Dojo 1.7.


Other Dojo widget considerations

The table below identifies other Dojo widget considerations for HATS.

TabContainer widget
  1. When used in a HATS transformation .jsp file with other HATS non-Dojo widgets, the tabs might not initially display properly, that is, display as partially cut off. This issue is caused by the Dojo theme set after the TabContainer widget is created. When the browser is resized, the issue disappears. To work around this issue, add one of the following scripts after the <body> tag and the <%out.println("-->");%> tag.
    • Call the resize() method on the TabContainer widget.
    • Call dojo.addClass to set the Dojo theme on the dojo.body(), for example,


      <script type="text/javascript">
      dojo.addClass(dojo.body(),"claro");
      </script>


iPad considerations

The table below identifies iPad considerations for HATS.

iPad considerations
  1. Because the iPad device includes a large screen relative to some other mobile devices, it works better with applications that are not created with options optimized for mobile devices. When creating a HATS web project for an iPad device, do not select the Optimize options for mobile devices option.
  2. WebFacing and bidirectional language applications do not support iPad devices.
  3. The iPad keyboard does not support some keys required by host applications, for example function keys (F1 - F24) Enter, Attn, Clear, and other keys. To enable the use of these keys in your application, either include a host keypad or add the keys to your transformed screens.
  4. Consider using drop-down lists and radio buttons with auto submit enabled so users don't have to click the Enter key.
  5. The iPad device does not support Java applets, therefore the HATS Automatic Disconnect and Refresh option, Enable server push (applet), is not supported. Use the Enable client pull (AJAX) option instead. For more information about the HATS HATS Automatic Disconnect and Refresh functions, see the HATS User's and Administrator's Guide.
  6. In Dojo Combo box widgets, no item from the drop-down list is selected by default. If you select the first item in the drop-down list, it does not get selected. To select it, you must first select some other item from the list, then select the first item. This could cause a problem if auto submit is enabled.
  7. Drop-down lists for Dojo Combo box and Filtering select widgets do not appear next to their corresponding input fields. They might be covered by the keypad or display off the transformation area. You might need to scroll or click the down arrow several times to find them. Also, in the horizontal pane all items in the list might not display if rendered close to the bottom of the page. This is not a problem in the vertical pane.
  8. The input field in the Dojo Text box widget does not receive focus until you click in it.
  9. Drag and drop is not supported for the Dojo Enhanced grid widget.
  10. Sorting columns in the Dojo Enhanced grid widget might not work the first time. You might need to click the sort icon and hold it down more than once to get the sort to work.
  11. Print and spreadsheet support requires that the iPad device has applications installed that will open PDF, CSV, and XLS files from the browser.


Android considerations

The table below identifies Android considerations for HATS.

Android considerations
  1. If the screen size of your Android device is small, you might consider creating a HATS mobile project rather than a HATS web project for use with your device. This might provide a better user experience for a smaller screen. For more information, see the section "Developing HATS applications for mobile devices" in the HATS User's and Administrator's Guide.
  2. The Android browser is not supported by WebSphere Portal. To use HATS portlets, you must use Firefox or other supported browsers on the Android platform. For more information, see WebSphere Portal detailed system requirements.
  3. The HATS List widget may appear differently when using the Android browser compared to other browsers.
  4. Item selection from a Drop-down widget rendering a HATS Selection List component may not work correctly with the Android browser. As an alternative use Firefox.
  5. When retrieving table data in spreadsheet file format, if you choose .csv as the spreadsheet format, the downloaded spreadsheet file will be in .xls format with some versions of the Android browser.
  6. When running an Integration Object from a Model 1, JSF, or Struts web page using the Firefox browser, the Tab key may not correctly tab from one input field to another. Both Tab and Next keys work correctly with the Android browser.
  7. When running an Integration Object from a Model 1 web page, the Dojo Grid widget does not display the output page correctly. As an alternative use the HTML Table widget.
  8. Downloading files using the HATS host print function for both 3270 and 5250 does not work with the Android browser. As an alternative use Firefox.
  9. Viewing a PDF using 5250 print support does not work with the Android browser.


Rich client considerations

The table below identifies rich client considerations for HATS.

Rich client considerations
  1. In order to configure a Lotus Notes target platform for testing, you must have both the Lotus Expeditor Client for Desktop version 6.2.0, or later, and Lotus Notes version 8.5.1, or later, installed.
  2. When installing a HATS rich client application into Eclipse RCP 3.5.2, the Eclipse Install New Software wizard does not provide an enabled Finish button on the final page of the wizard. As a workaround, when the final wizard page, Review Licenses, is reached, click the Back button and then the Next button. At this point the Finish button will be enabled and the wizard can be completed.


Language considerations

The table below identifies language considerations for HATS.

Language considerations
  1. Bidirectional (Hebrew and Arabic) applications are supported only on Internet Explorer V6.0 with SP 1 or later, or Firefox 3.4 or later. Bidirectional applications are not supported on mobile devices.
  2. In Arabic and Traditional Chinese Windows 7 environments, the bold font is not correctly displayed in the Rational Software Delivery Platform Help Contents view. To correct this, change the default font of the Message box in the Windows appearance settings dialog. For example, change the default Message box font to Traditional Arabic or PMingLiU as appropriate.
  3. If you type the Yen character using a Japanese keyboard in your browser, the browser will display a backslash "\" on the screen. This is a browser limitation. However, for Japanese code pages, HATS runtime will convert "\" to the Yen character when sending data back to host.
  4. The Japanese Romaji IME cannot be used to correctly input DBCS characters into G fields and J fields on an iPad device. Use the Japanese(Kana) IME instead.
  5. With Internet Explorer V8, AutoIME switching does not work with Dojo Text box and Validation text box widgets. AutoIME switching works correctly with Internet Explorer V9.
  6. In HATS rich client applications, if you use ATOK2011 with Roman input mode, the input mode changes to Kana input mode using the AutoIME function. This is a limitation in the Eclipse environment.
  7. A right-to-left screen customization on a Linux RCP client does not respond correctly. The screen reverse action does not cause the screen customization to be mirrored. Mirroring is achieved in Windows by setting the orientation parameter for the SWT containing pane, but SWT on Linux does not support the orientation parameter.
  8. Developing HATS applications with Arabic sessions on Windows 2008 is not supported. In addition, running Arabic rich client applications on Windows 2008 is not supported, even if the applications are created on other supported client software versions. However, running HATS web applications with Arabic sessions in a browser on Windows 2008 is supported.
  9. Using a non-US keyboard layout, keys entered in combination with the AltGr key can be entered into numeric fields when the "Enable 3270 numeric lock" option is enabled.
  10. In bidirectional projects, using Dojo widgets on Model 1 web pages, incorrect results occur when typing in Autopush mode. For example, if you type abc (in the bidirectional language), switch to the Latin layer, and type _ABC, then the expected rendering is cba_ABC. However, the actual rendering is _cbaABC. To work around this problem, press the End key after typing abc. This problem occurs not only for the underscore character, but also for all neutral characters (including the space character) separating the bidirectional and Latin languages.
  11. The DBCS option on the Rendering tab to Automatically convert SBCS characters to DBCS for G-type and J-type fields is supported only when using Internet Explorer. It is not supported when using Chrome, Firefox. Konqueror, Opera, or Safari.
  12. GB18030 Yi syllables do not display correctly with Chrome 18. For more information, see https://code.google.com/p/chromium/issues/detail?id=126605 .
  13. GB18030 0xE815-0xE864 characters do not display correctly with Internet Explorer 9. For more information, see http://social.technet.microsoft.com/Forums/zh-CN/iezhcn/thread/1eb8af96-8360-4ef6-b056-eb013d9ce168.


Other considerations

The table below identifies other considerations for HATS.

Other considerations
  1. When transforming IBM i applications, HATS does not support the complete set of DDS keywords. For a list of unsupported keywords, see HATS support for DDS keywords.


Deprecated functions

The table below identifies functions that have been deprecated in HATS. While support for these functions continues for now, IBM reserves the right to remove any of these functions in a subsequent release of HATS. For information and alternatives, see the HATS Information Center for the appropriate function.

Deprecated functions
  1. IBM Portlets
  2. HATS EJB applications
  3. Macro Editor and Advanced Macro Editor support
  4. HATS tabbed folders
  5. Automatic Disconnect and Refresh - server push (applet) function
  6. Web Express Logon CMPI_DCAS_KEYRING_FILE and CMPI_DCAS_KEYRING_PASSWORD parameters
  7. Database Access Integration Objects
  8. BusinessLogicInfo API
  9. $FormatNumberToString()$ and $FormatStringToNumber()$ methods
  10. void setHPubErrorPage(java.lang.String value) method

Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Host Access Transformation Services
Documentation

Software version:

9.0, 9.0.0.1

Operating system(s):

AIX, HP-UX, IBM i, Linux, Linux iSeries, Linux pSeries, Linux zSeries, Solaris, Windows, z/OS

Reference #:

7038663

Modified date:

2014-08-08

Translate my page

Machine Translation

Content navigation