IBM(R) WebSphere(R) Host Access Transformation Services (HATS) Refresh Pack V7.0.0.5

Copyright International Business Machines Corporation 2002, 2009. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

This document includes the following information:

  • Print the file content in PDT mode with a local PDT printer.
    • Limitations
    1. UDC conversion tool limitations:
    2. Since User-Defined Area (UDA) ranges are defined based on Windows platforms, UDCs can only be displayed in Windows platforms.

    Changing session properties of the associated printer session for printing Adobe PDFs from the transformation screen

    A new method, getPrinterSession, has been added to the com.ibm.hats.runtime.HostConnection class to enable HATS business logic to have access to the associated printer session. If the host connection is a TN3270E connection and has an associated printer session, the getPrinterSession method returns an instance of the com.ibm.eNetwork.beans.HOD.HostPrintSession class. Otherwise, it returns null.

    The following code sample demonstrates how to use business logic to get the printer session information and provide access to the associated printer session: 

    public static void execute(IBusinessLogicInformation blInfo)
{
    //add code here to perform your business logic
    HostPrintSession printerSession = null;
    String pdfPaperSize = null;
    if (blInfo != null) {
        Map connectionMap = blInfo.getConnectionMap();
        HostConnection hostConnection = (HostConnection)connectionMap.get("HostConnection");
        if (hostConnection != null) {
            printerSession = hostConnection.getPrinterSession();
        } else {
            System.out.println("hostConnection == null");
        }
        pdfPaperSize = getGlobalVariable(blInfo, "pdfPaperSize").getString();
        if (pdfPaperSize != null && "".equals(pdfPaperSize)) {
            pdfPaperSize = null;
        }
    } else {
        System.out.println("blInfo == null");
    }
    
    if (printerSession != null && pdfPaperSize != null) {
        String currentPdfPaperSize = printerSession.getPdfPaperSize();
        
        try {
            if (!pdfPaperSize.equals(currentPdfPaperSize)) {
                printerSession.setPdfPaperSize(pdfPaperSize);
            }
        } catch (PropertyVetoException e) {
            e.printStackTrace();
        }
        
    } else {
        if (printerSession == null) {
            System.out.println("printerSession == null");
        } else {
            System.out.println("pdfPaperSize == null");
        }
    }
}

    More details provided for macro parsing errors

    Currently when you try to save a macro and it contains an error, you see a popup message simply stating that an error exists.

    Starting with HATS 7.0.0.2, the errors in the macro are summarized in the Problems view, whether you are using the macro editor, text editor, or XML editor. The source code of the macro displays a marker, a red circle with a white X in it, which appears on any lines containing an error.

    The macro is saved even when it contains errors, enabling you to find and fix the errors at a later time, if necessary. However, macros containing errors cannot be played at runtime or in the Host Terminal.

    Single Sign On: Support for Kerberos ticket

    Note: This support is limited to rich client projects using the 5250 (not 5250W) host type on Windows Domain clients.

    To enable support for Kerberos tickets, add the following lines inside the <otherParameters> tag in your application.hap file:

    Host On-Demand CustomTable support in HATS

    A custom table file can contain any number of tables, in any combination of keyboard and display tables.

    Keyboard
    This mapping table remaps the user's keyboard characters as input customized for a host application.
    Display
    This mapping table remaps host display characters into screen output customized for the user.

    To enable the use of custom tables in your project:

    1. Open the HATS project.
    2. Edit the connection by double-clicking the name in the Connections directory.
    3. Click Advanced.
    4. Click Add.
    5. In the Add Parameter dialog, select CustomTable from the drop-down list for Name.
    6. In the Add Parameter dialog, enter the name of your custom table file in the Value field.
    7. Click OK to exit from the Add Parameter dialog.
    8. Copy the sample custom table file, CustomTableExample.txt, into in a folder named customtables in the root of the .ear project for your HATS Web application or in the root of the HATS RCP Runtime Extension project for your HATS rich client project. If the folder does not exist, create one. When you install the Rational Software Delivery Platform using the default path, CustomTableExample.txt is located in c:\Program Files\IBM\SDP70\hats\customtables.

    The file format of CustomTableExample.txt is similar to that of Java properties files. Lines that start with # are comments, and variables shown as nn and NN are hexadecimal values. Following is an example of a sample custom table file: 

    ##### Start of file
# Map Local nn to EBCDIC NN in keyboard table
sbcs.keyboard.0xnn=0xNN
.....

# Map EBCDIC NN to Local nn in display table
sbcs.display.0xNN=0xnn
.....
##### End of file

    Note: The CustomTable parameter only applies to the single-byte character set (SBCS).

    Foreground color support for HATS function keys

    The function key component now supports extraction of foreground colors detected in the function keys on the host screen for HATS Web and Portlet projects only. When the button widget is selected to render the function key in the transformation, the text of the button is rendered using the extracted color.

    Color information is extracted for the first host field containing any part of the function key. If the function key is split over two fields, such as "F12=" and "Exit", the color information for the field containing "F12=" is extracted.

    This function is disabled by default. To enable the rendering of the foreground color for the text on a button, check the Enable foreground colors box in the settings panel of the button widget on the Rendering tab of the project settings editor.
    Note: The check box does not appear in the button widget settings in the following wizards if the Function Key component is not selected:

    To enable the rendering of the foreground color for the text on a button using the Source tab of the project settings editor, add the following line to the com.ibm.hats.transform.widgets.ButtonWidget class in the application.hap file: 

    <setting name="preserveColors" value="true"/>

    If you want to implement this function, and you have a template specified in your project that uses the blacktheme.css stylesheet, you need to manually update blacktheme.css in one of the following ways:

    1. Remove the following line from the input.HATSBUTTON declaration: 
      color: lime;
      This enables foreground colors to be rendered on function keys; however it causes other buttons generated by a HATS widget to render in a default color.
    2. Combine the color-related CSS declarations for each color. For example, change: 
      .HBLUE {
	color: #3c9dff;
}

input.HBLUE {
	white-space: normal;
	letter-spacing: normal;
}
      to 
      .HBLUE, input.HBLUE {
	color: #3c9dff;
	white-space: normal;
	letter-spacing: normal;	
}
      Repeat this change for each color.

    An alternative to manually editing the blacktheme.css stylesheet is to create a new dummy project and copy the theme CSS files from this project into your project. Be aware that any changes you have made to your CSS files are overwritten.

    Working with Web Services in the HATS Project View

    Prior to this refresh pack, you had to open the Navigator view to do any work with HATS Web Services. Beginning with HATS 7.0.0.2, you can work with Web Services through the HATS Project view.

    If you have created Web Services through the Navigator view prior to this refresh pack, the .wsdl files you created are now visible in the Project view. The files are shown in the WebContent/WSDL folder, and you can use the context menu to work with them just as you did in the Navigator view.

    Prior to V7.0.0.2, the Web Service support files were visible in the Project view in the Source/webserviceclasses folder, but there was no context menu to enable you to work with the support files. There is no migration of the support files to enable the context menu, so this is still true for support files generated before this refresh pack is applied. However, if you would like to be able to have the context menu available for the support files, you must regenerate the support files from the Integration Object. Support files created from Integration Objects after V7.0.0.2 has been applied already have the context menu available to them.

    Apply all connection settings when connection overrides are specified on the transformation connection

    Prior to this refresh pack, when using connection overrides in a HATS project, the HATS runtime creates a basic connection that disables certain functions that are enabled for the default connection of the project. On the basic connection, pooling is always disabled, the connect and disconnect time-outs are ignored, as are the connect and disconnect macros. The other connection settings, such as the host name, port, and SSL enabled are copied from the project's default connection definition, typically main.hco.

    For information on how to specify connection overrides, please refer to Overriding HATS Application Connection Properties in the URL.

    Beginning with HATS 7.0.0.2, you can select whether to create a basic connection or to apply all connection settings. You can also specify the connection to use as a transformation connection at runtime, independent of the Host On-Demand session URL overrides.

    To enable the selection of connection type, a new URL parameter override, connectionName, has been added in HATS 7.0.0.2. The connectionName parameter is optional.

    If Host On-Demand session URL parameters are specified and connectionName is not specified, HATS runtime creates a basic connection as it did prior to this refresh pack.

    If Host On-Demand session URL parameters are specified and connectionName is specified and a connection with that name exists, regardless of whether it matches the project default connection, HATS runtime creates a transformation connection, applies all connection settings associated with the connection name in input, along with the Host On-Demand session URL parameters. HATS runtime creates a new connection pool and associates it with the overrides in input, unless a connection pool matching connectionName and the overrides in input already exist. If a pool matching the overrides already exists, HATS runtime does not create a new pool, but reuses the existing pool.

    Connection overrides can be different for each user accessing a HATS application. HATS runtime creates a connection pool for each user. Ensure that pooling is disabled for the connection.

    Pools dynamically created when connection overrides are specified, regardless of whether the connectionName parameter is specified, are automatically destroyed when the last active connection is terminated, providing that pooling is not enabled.

    You can specify connectionName as the only URL parameter. If connectionName is the only URL parameter specified, and the connectionName and a connection with that name exists, HATS runtime creates a tranformation connection using the connection settings associated with the connection name, rather than using the default connection settings.

    To be able to specify the connectionName parameter as a URL override, the parameter must be enabled for overrides on the Connection Parameter Overrides page on the Other tab in the project settings editor.

    Maintain the order of prompts and extracts in macros

    Beginning with HATS 7.0.0.2, when you create a macro with prompts and extracts, and edit the macro with the editor, the prompts and extracts appear in the macro source file in the order that you recorded them. In addition, when you open the macro in the editor, the cursor appears on the same line it was on when you last saved the macro, instead of appearing at the top of the macro source file.

    Connection parameter overrides for Integration Objects

    Beginning with HATS 7.0.0.2, a new instance method, setHPubConnectionOverrides(Properties overrides), is introduced on the Integration Object to enable overridding of connection parameters. The method sets the connection overrides for the Integration Object. When the Integration Object doHPTransaction() or processRequest() methods are called, if there are connection overrides associated with the Integration Object, a new pool for the Integration Object is created based on the Integration Object's connection pool and overrides. The new pool name can be retrieved using the Integration Object instance method getHpubStartPoolName().

    To specify connection overrides in Web Services, the following instance methods are also added to the Integration Object:

    setHPubConnectionOverrides(String overrides)
    Requires the following pattern in the overrides string in input: 
     
"key1=value1, key2=value2"
    For example: 
     
"LUname=00001, host=ralvms"
    String getHPubConnectionOverrides()
    Returns the overrides in the same pattern.

    To specify connection overrides on existing Integration Objects, without recompiling the Integration Object, a new Java class, com.ibm.HostPublisher.IntegrationObject.HPubPoolFactory, is added. The new class has a static call to create a connection pool based on an existing pool (the Integration Object pool) and the connection parameter overrides. The method returns the name of the new pool, or null if the pool name in input is invalid.

    The signature of the new call is: 

     
public static synchronized String create(String ioPoolName, Properties overrides, 
		 		 	        HttpServletRequest request)

    The create method generates a new connection pool by cloning the connection pool in input, and applying the connection overrides to the Host On-Demand properties associated with it. The new pool name is returned and must be set in the Integration Object using the setHPubStartPoolName() method.

    If the Integration Object is deployed in an EJB container or as a Web service, the third parameter of the create method (HttpServletRequest) can be set to null. In this case, the pool name must be qualified with the HATS application name. For example, the pool name should be my_hats_project/main.

    To use connection overrides, modify the code accessing the Integration Object to call the HPubPoolFactory.create() method or the new Integration Object instance methods before calling the doHPTransaction() or processRequest() methods.

    For chained Integration Objects to work correctly:

    The following is an example of JSP code using the HPubPoolFactory.create() method: 

     
<% // Set the connection overrides  
 java.util.Properties overrides = new java.util.Properties(); 
 overrides.setProperty("LUName", "LU00001"); 
 // Create a new Pool based on a the default pool and the connection overrides  
 String poolName = SignOn.getHPubStartPoolName(); 
 String newPoolName = com.ibm.HostPublisher.IntegrationObject.HPubPoolFactory.create(poolName, overrides, request); 
 // If a valid poolName is returned, make the IO use the new pool 
 if (newPoolName != null) {
    SignOn.setHPubStartPoolName(newPoolName); 
    SignOn.doHPTransaction(request,response); 
 }
 else {
    // Error condition
 }

%>

    The following is an example of JSP code using the IO.setHPubConnectionOverrides() method: 

    <% // Set the connection overrides  
 java.util.Properties overrides = new java.util.Properties(); 
 overrides.setProperty("LUName", "LU00001"); 
 // Apply overrides to the IO  
 SignOn.setHPubConnectionOverrides(overrides); 
 SignOn.doHPTransaction(request,response);     
 // Get new IO pool name to be used in following logic 
 String newPoolName = SignOn.getHPubStartPoolName();  
  
%>

    With either example, the Integration Object uses a new connection pool created by cloning the original Integration Object's pool and applying the connection overrides. All the settings that apply to the original Integration Object's pool also apply to the new pool, including pooling. Connection overrides can be different for each user accessing an Integration Object. HATS runtime creates a connection pool for each user. These pools, created dynamically when connection overrides are specified, are destroyed when the last active connection is terminated, providing that pooling is not enabled.

    Connection override parameters specified on the Connection Parameter Overrides page on the Other tab in the project settings editor do not apply to Integration Objects.

    Allow a user to switch the associated screen capture when editing a rich client transformation

    Prior to this refresh pack, to associate a different screen capture with a rich client transformation when working in the Java Visual Editor, you have to manually update the screenCapture Java field in the class.

    Beginning with HATS 7.0.0.2, you can use the properties view to change the screen capture for a rich client component rendering or default rendering. Click the button next to the screen capture in the properties view to display a dialog in which you can select different screens. When you click OK, the new screen capture is set for all component renderings and default renderings in the current rich client transformation, and the design view updates all rendering items using the new screen capture.

    Note: There is no migration of rich client transformations created prior to this refresh pack. The static variable screenCapture remains in the transformation, even after you change to a different screen capture. If you want to remove the screenCapture variable, you must remove the variable by editing the transformation source file.

    Non-US English strings included in templates and transformations of a HATS RCP project

    Prior to this refresh pack, non-US English strings included in the templates or transformations of a HATS RCP project were not compiled correctly when the project was exported as a feature. The problem no longer exists when creating projects after installing HATS 7.0.0.2.

    However, if you have existing HATS RCP projects built with HATS 7.0 or HATS 7.0.0.1, you can work around the problem by editing the build.properties file, found in the root folder of each project. Add the following line at the bottom of the build.properties file: 

    javacCustomEncodings.library.jar = src/rcpproject/templates/[UTF-8],src/rcpproject/transformations/[UTF-8]

    Update history

    This refresh pack contains fixes for APARs as well as internal fixes.

    Problems fixed in this refresh pack

    Please see the HATS support page for a more detailed description of these APARs.

    This update includes the following fixes:

    IC52688 - Check box and radio button not being rendered with usual dotted line to show focus.

    IC52693 - Macro recorder does not recognize new screen when "auto enter" is used.

    IC52879 - Not able to add background image to function key button.

    IC52936 - HATS V7 using a basic text PDT for host print conversion, UDC's are converted into X'8140', which is used for undefined characters.

    IC52946 - Input field loses focus if ENPTUI radio button defined on page.

    IC52968 - Certain screens in HATS not accepting input data.

    IC53056 - Font size selection aded to Stylesheet to improve ENPTUI scrollbar sizing.

    IC53176 - Item Selection list renders data outside of roped area.

    IC53181 - Enter not sent after migrating from V5 to V7.

    IC53208 - BIDI: HATS error when HATS 6.0.7 project run on WAS 6.1.0 server.

    IC53213 - Specified LU or Pool name field not updated after multiple exits and entries into the same field.

    IC53310 - The subfile "actions" are being rendered too far apart.

    IC53334 - Missing Data when alternate=Default is used and function keys are in the rendering set.

    IC53658 - 5250 session takes 120 seconds to time out when trying to use duplicate workstation IDs.

    IC53678 - Remapping numpad + sign to "qfldext" causes + sign to be added to the next field.

    IC53732 - Java regular expressions not processed correctly in design view or preview.

    IC53882 - HATS is setting the refresh number that gets passed to the applet before all the combining screens occurs.

    IC53594 - Customer getting errors when trying to generate a portal project from a HATS project.

    IC53709 - ItemSelection component with Checkbox won't select item unless user puts a checkbox by two separate items.

    IC53934 - When navigating from one host screen to the next, the browser window changes size and adds a scroll bar.

    IC54052 - Select all text on focus not selecting text in first input field in rich client project environment.

    IC54086 - Using English Operating System and English HATS but Portuguese regional setting, the HATS Portlet is incorrectly created.

    IC54125 - Input field with hints displays data outside of the roped area.

    IC54144 - Client running out of heap memory.

    IC54163 - HATS project settings displaying a 2 license restriction message when using Integration Objects in a WebSphere J2EE application.

    IC54175 - NotSerializableException: COM.IBM.HATS.COMMON.CUSTOMLOGIC.HATSCUSTOMLISTENER.

    IC54358 - Insert Action not working properly with Japanese codepage 939.

    IC54432 - Using Item Selection component and Radio Button widget, preselected values aren't rendered as selected buttons.

    The following problems were found internally, so there is no additional information about them on the HATS support page.

    34059 - Text replacement with a button or a link does not affect keyboard support.

    35644 - Promted to run license enablement after it has already been run.

    36208 - Widget preview performs text replacement twice.

    36414 - Some extra options on HATS widget settings.

    36427 - BIDI: Wrong orientation of screen in TEXT replacement.

    36460 - A screen customization that applies a deleted RCP transformation causes a runtime exception.

    36514 - Red rectangle marking the recognized field in global rule settings editor shown mirrored for RTL screens.

    36586 - Launch License Settings link doesn't work on welcome page.

    36599 - Migration of HATS 6.0.x project fails in HATS 7.0.

    36803 - Settings - Calendar panel changes not always prompting for save.

    36819 - BIDI: Lines with unprotected fields are not mirrored in JVE preview.

    36843 - BIDI: Wrong encoding in .cvs files.

    36850 - BIDI: Subfile is corrupted when RTL component recognition is checked.

    36869 - RCP: Cannot show fully qualified names when showing file extensions.

    36875 - Macro recording does not default to unique name on second recording.

    36890 - 3270 HATS application fails to run in Portal due to missing security .p12 file.

    36891 - DBCS: The final DBCS was trimmed on O field when SI/SO off.

    36893 - Attach component element to each table cell or row in SWT Table widget.

    36900 - 5250W problems with 27x132 screens and HATS 7001.

    36909 - Screen customization and 1024x768 resolution - can only apply transforms.

    36912 - BIDI: Using bidi profiles causes text in input fields to be underlined.

    36916 - PF key style background image path not always correct.

    36923 - Providing spreadsheet file settings in the Table Widget downloads an empty file.

    36931 - Global Variable view: No difference between shared and local global variables.

    36932 - Global Variable view: Does not display global variables from Blank Screen event.

    36946 - In default rendering, if non-subfile data is between the subfile data or header and the actions, the action items for the subfile widget are not rendered.

    36983 - Host screen captures won't display protected fields in transformation wizard.

    36989 - Memory leak in HATS toolkit may cause unpredictable behavior.

    36993 - Creation of global variables with the same name shows multiple instances.

    37001 - Connection source tab not updated with userlist changes on other tabs.

    37009 - Javascript error in IE. Could not get type property: Invalid argument.

    37015 - 3270E SSL connection fails with ELC0101 error.

    37016 - RCP: 'select all on focus' does not work with auto advance.

    37019 - Class can not be loaded error when the Generate Java bean skeleton option is selected.

    37026 - HPS5145 error when connecting to the host using SSL on ROS.

    37029 - Insert Host Component Wizard in a Web Project is corrupted.

    37037 - Renaming a global variable in a screen combination creates a new screen customization.

    37039 - BlankScreenEvent global variables not renamed and not listed in global variable list.

    37048 - "License limit has been reached" when HATS RCP application is deployed.

    37052 - Set of concatenated global variables fails after removing all global variable actions.

    37066 - Double-click to Edit rendering item causes two wizards to appear.

    37079 - Advanced connection parameter changes don't show up in GUI.

    37081 - Add prompt action for all fields does not preserve default values.

    37126 - New screen customization and screen combination wizards not centered when launched.

    37140 - Creating IOs in HATS EJB project produces compile errors.

    37143 - SBCS:Can't work for custom table file on RCP.

    37158 - A HATS project checked out from CVS fails to appear in the HATS Project View tree.

    37163 - Alternate rendering panel fails to show HATS tag and cannot edit HATS tag.

    37173 - Migration is erroneously copying SignedJs.jar to common folder.

    37217 - Highlight check boxes cut off in new screen customization and screen combination wizards.

    37240 - Host simulator not working when opening host terminal in the macro editor.

    37248 - DBCS: Highlighting displayed incorrect for DBCS character.

    37255 - Can't recognize a subifle when the actions are located in a table.

    37257 - Cannot extract to a global variable in a child macro.

    37284 - BIDI: Wrong orientation of components in RTL screen transformation.

    37285 - BIDI: Noncustomized screen are reversible despite of disabling reverse.

    37289 - BIDI: Text is displayed reversed on VT session.

    37290 - BIDI: Wrong text rendering when prompt GV for RTL screens.

    37304 - BIDI: "Reverse text in widget" checkbox causes reverse shaping problem.

    37305 - BIDI: Filling Data from widget settings saved in visual format.

    37322 - BIDI: Arabic shaping problems in HATS Toolkit with Windows Vista.

    37378 - BIDI: Reverse toolbar orientation doesn't work on RTL screen.

    37388 - Asynchronous update support causes infinite loop during macro run.

    37396 - BIDI: Reverse text checkbox is not working for title row in table.

    37398 - BIDI: Reverse text doesnt work on Radio buttons and Check box widgets.

    37401 - Custom component can't render subfile in dialog.

    37407 - NPE in screen recognition composites and dialog.

    37422 - BIDI: Screen reverse only reverses the text of a customized screen.

    37445 - TN3270E connection accidentally picks up WFEnabled=true.

    37455 - BIDI: Widgets in RTL screen are displayed with LTR orientation in JVE.

    37466 - Editing global rule causes duplicate HATS:Component tag.

    37473 - OIA doesn't correctly reflect the keyboard layer when the focus is set to the password field in RCP.

    V7.0.0.1 Description

    Functions extended by this refresh pack

    Alternate way to input negative numbers in 5250 signed numeric fields

    Beginning with HATS Version 7.0.0.1, you can enter a minus sign in the first position of a 5250 signed numeric field to input a negative number instead of using Field minus and incurring a round trip to the server. When using this feature, you should enable the Automatically delete host field data runtime setting, in the com.ibm.hats.common.RuntimeSettings class found in the source of the application.hap file. You should also clear any unwanted prefilled data from the field before advancing to another field.

    Notes:

    1. Do not enter a minus sign in the first position and also press Field-, Field+, or Field Exit.
    2. The previous method of entering negative numbers into signed numeric fields with Field minus still works.

    Quick Field Exit

    HATS Web applications now have an additional keypress to speed the entry of numeric data for 5250 screens. This new keypress clears the current field from the current caret position to end of the field, and advances the cursor position to the next field. Although this keypress can be used on any field, it was added for use where end users previously used Field Exit. A real Field Exit keypress sends the screen of data to the host and causes the transformation to be redrawn. Screens requiring many Field Exits before being submitted caused usability issues. This feature, combined with the Field Exit Emulation feature, increases the speed of such applications considerably.

    The KBS.js file now has a new mnemonic in its table for keyboard support, [qfldext], for quick field exit. This keypress is assigned to be Ctrl-Enter by default. The assigned keypress can be changed like the other supported keypresses. A true Field Exit is still available, but the mapping for it is now Shift-Enter by default.

    Default keypress combinations for HATS V7.0 Web applications are:

    Quick field exit
    Ctrl-Enter
    Field exit
    Shift-Enter
    Field minus
    Ctrl-Keypad minus
    Field plus
    Ctrl-Keypad plus

    Because rich client applications have a different architecture than Web applications, a quick field exit keypress in rich client applications is not necessary. There is no round-trip delay for a true Field Exit in rich client applications.

    Field Exit Emulation

    This feature modifies the default behavior of a HATS application to automatically supply a Field Exit aid key for a user, when required. A Field Exit aid key is required when certain types of 5250 fields are modified.

    For example, if you are using the Quick Field Exit keypress to advance from field to field, and submit the screen with Enter or some other non-field aid key, a Field Exit might be required for the field containing the cursor when the screen is submitted.

    Prior to this refresh pack, the host might respond with the error message "Enter key not allowed in field," because you did not explicitly supply the required Field Exit before submitting the screen with Enter. Beginning with this refresh pack, the HATS server sends a Field Exit to the host before sending the Enter, avoiding the error message.

    If the previous behavior is required by your application, you can revert to the previous behavior by adding a new project setting in the application.hap file. To disable the new behavior, add the following to the application.hap file: 

    <class name="com.ibm.hats.common.RuntimeSettings">
	<setting name="emulateFieldExit" value="false"/>
</class>

    If there is already a <class> section by this name, just add the <setting> line inside the section.

    Host code mapping for codepages 1390 and 1399

    The following information was not included in the HATS V7 documentation library.

    There have been host-to-PC code mapping inconsistencies between IBM Personal Communications and Host On-Demand products on a number of DBCS code points when Japanese host code page 1390 or 1399 is used. In Host On-Demand, the UseHODCDRA1399 flag controls the Unicode remap to correct the inconsistencies. The following table summarizes the mapping with and without the UseHODCDRA1399 flag:
    Summary of Unicode mapping
    EBCDIC code point Unicode code point
    (UseHODCDRA1399 = true)    		 Unicode code point
    (UseHODCDRA1399 = false)
    0x4260 U+FF0D (Fullwidth hyphen-minus) U+2212 (Minus sign)
    0xE9F3 U+2212 (Minus sign) U+FF0D (Fullwidth hyphen-minus)
    0x43A1 U+FF5E (Fullwidth Tilde) U+301C (Wave Dash)
    0xE9F4 U+301C (Wave Dash) U+FF5E (Fullwidth Tilde)
    0x447C U+2225 (Parallel To) U+2016 (Double Vertical Line)
    0xDFE5 U+2016 (Double Vertical Line) U+2225 (Parallel To)
    0x444A U+2015 (Horizontal Bar) U+2014 (EM Dash)
    0xDDB7 U+2014 (EM Dash) U+2015 (Horizontal Bar)
    0x426A U+FFE4 (Fullwidth Broken Bar) U+00A6 (Broken Bar)
    0xE9F5 U+00A6 (Broken Bar) U+FFE4 (Fullwidth Broken Bar)

    Beginning with this refresh pack, HATS has adopted the Host On-Demand setting. The default for UseHODCDRA1399 is false in HATS V7 beginning with this refresh pack. To enable the UseHODCDRA1399 flag in HATS:

    1. Select the HATS project.
    2. Select the specified connection in the HATS connections folder.
    3. Click Advanced.
    4. Click Add.
    5. Select UseHodCDRA1399 under Name.
    6. Set the parameter value to true.
    7. Click OK.

    Asynchronous update enabled by default in new RCP applications

    In HATS V7, asynchronous update support was available for RCP applications, but by default it was disabled. With this refresh pack, the default for all new RCP applications is to enable the asynchronous update support. When asynchronous update support is enabled for an RCP application, an icon appears in the operator information area (OIA).

    This change to the asynchronous update support provides the following advantages:

    Business logic and custom logic modified to support migration of HATS V6.0.x applications to HATS V7

    If Abstract classes in the com.ibm.hats.common.customlogic package have been extended for customer applications before HATS V7.0, there will be compilation and possibly runtime failures with applications migrated to HATS V7.0. Also, any new application development for HATS 7.0.0 that extends these classes are required to implement unused deprecated APIs.

    This refresh pack contains modified business logic in the com.ibm.hats.common.customlogic package to alleviate two conditions:

    Five new "advanced" classes in the com.ibm.hats.common.customlogic package replace other classes that are deprecated:

    Deprecated and new "advanced" classes in the com.ibm.hats.common.customlogic package
    Deprecated class New advanced class
    AbstractCustomScreenRecoListener AbstractAdvancedCustomScreenRecoListener
    AbstractCustomMacroActionListener AbstractAdvancedCustomMacroActionListener
    IApplicationInfoListener IAdvancedApplicationInfoListener
    ICustomScreenRecoListener IAdvancedCustomScreenRecoListener
    ICustomMacroActionListener IAdvancedCustomMacroActionListener

    The HATS 7.0.0 method signatures, containing the IBusinessLogicInformation class, have moved from the existing classes to the "Advanced" classes. The HATS 6.0.x method signatures, containing the deprecated BusinessLogicInfo class, remain in the existing classes. The existing classes are modified to extend the new "Advanced" classes.

    Implementations have been added to the existing classes for each abstract method signature being inherited from the corresponding "Advanced" class. Each of these implementations bridge the invocation of the new signature to the old signature by creating a BusinessLogicInfo object from the IBusinessLogicInformation object and invoking the old signature. These changes enable customer applications created prior to HATS V7.0 to work properly, without modification, preserving the namespace and the associated functionality.

    After this refresh pack is installed, new customer applications should use the new classes.

    5250W HATS rich client applications can use 5250W to connect to a WebFacing server

    In HATS V7, RCP applications could not connect to a WebFacing server by specifying the 5250W host connection type. With this refresh pack, HATS rich client applications support 5250W connections to a WebFacing server.

    Rich client application connections to the WebFacing server include the benefit of not requiring online transaction processing (OLTP) capacity. This significantly reduces the overall cost of using HATS with 5250 applications by removing the interactive feature requirement associated with TN5250 session connectivity.

    Calendar Widget enhancements: Increment or decrement the selected year in the calendar widget

    Prior to this refresh pack, the calendar widget controls only allowed you to increment or decrement the selected date month by month. With this refresh pack, in addition to selecting the month by scrolling forward or backward, you can now select the year by scrolling. In the HATS interface, the year control has the same look and feel as the current month control. In addition, all of the rules for the month control, such as range start, range end, and default range, are implemented in the year control.

    When using the calendar enhancement, if you scroll the selected month from December to January, the year is incremented. Similarly, if you scroll the selected month from January to December, the year is decremented.

    Enable overwrite mode for non-bidirectional RCP applications

    In HATS V7, only Web applications or bidirectional rich client applications can enable overwrite mode for input fields. You can either select overwrite mode as a project theme when creating a project, or enable it initially in the client settings of a HATS application. When overwrite mode is enabled, text is overwritten when users type in an input field.

    With this refresh pack, overwrite mode can be enabled for all HATS applications, including non-bidirectional rich client applications.

    In HATS applications using DBCS codepages:

    Note: Although the Select all text on focus setting functions like overwrite mode, it is still available as a client setting because it can coexist with overwrite mode. The Select all text on focus setting functions as stated in the HATS User's and Administrator's Guide, regardless of the status of the overwrite or insert mode.

    Text filter added to HATS Projects view

    A text filter entry field has been added to the HATS Projects view to aid you in searching for HATS artifacts. An asterisk (*) can be used as a wild card to represent parts of the resource name. For example, using a filter of *.css or *css returns the same matches. Other filters that you could use are *.jsp or *jpg.

    Notes:

    1. A wildcard is appended to the end of the text that you enter into the filter field. For example, if you enter *.j in the filter field, an asterisk is appended to the *.j, resulting in a filter of *.j*. This filter would show you all .jsp and .jpg files.
    2. Filtering is not case-sensitive.

    To clear the text in the filter field, click the "x" beside the filter.

    Update history

    This refresh pack contains fixes for APARs as well as internal fixes.

    Problems fixed in this refresh pack

    Please see the HATS support page for a more detailed description of these APARs.

    This update includes the following fixes:

    IC50610 - HATS runtime customizes a host screen that is different than the recognized screen customization event.

    IC51053 - Autotab advance occurs even if the user doesn't type anything.

    IC51218 - Busy.jsp is displayed in the wrong language.

    IC51579 - HATS V6 disconnect event not processed when browser running asynchronous update applet is closed (by pressing X in corner).

    IC51661 - Macro record does not recognize "PageUp/PageDn" as AID key.

    IC51843 - The ">" symbol incorrectly performs as a ">=" condition.

    IC51903 - HATS asynchronous update applet stops working, meaning that users must manually refresh screens.

    IC51956 - Memory leak involving HODWatcher objects if IOGV.setGlobalVariable is called before HATS entry servlet.

    IC52164 - Ampersand in drop-down string fails at runtime.

    IC52181 - The characters ü, ö, ä are not displaying in rich client.

    IC52255 - Hang in HATS project view when right clicking on an IO that has many inputs and outputs

    IC52464 - Input fields come up as blanks.

    IC52545 - The menu text for "item selection" component is not rendered.

    IC52818 - HATS using DBCS codepage sends just character(s) typed in one type of input field, but Host On-Demand and Personal Communications send them with padding.

    IC52883 - HATS V7 new project wizard returns an invalid project description if the Use default location check box is cleared.

    The following problems were found internally, so there is no additional information about them on the HATS support page.

    27486 - Move the Use project defaults check box to right for bar and line graphs.

    30357 - Component tags in template not processed in Studio preview.

    30444 - Some objects, when created, are not showing or selected in the HATS Projects View.

    30446 - Color screen recognition dialog should not allow a marquee rectangle.

    31277 - HATS Administration: Number of host connections error handling.

    31347 - HATS Administration runtime tracing inadvertently enables HOD PS Event and OIA Event tracing.

    31571 - EAR file name should not change if manually modified.

    33241 - Maintain cursor position in HATS macro editor on save.

    33685 - Screen combination wizard panels should not change width.

    33691 - Open Welcome Page displays name in the console when opened; closes sections already opened.

    34059 - Text replacement with a button or link does not remove keyboard support for other keys not defined.

    34181 - If a Web project is selected, but the cursor focus is on an editor page, some icons on the toolbar are not available.

    34211 - Some widgets malfunctioned after replacing some strings.

    34991 - Double-click on a rendering set should open the rendering set in the Edit window.

    35632 - Last screen of a Host Simulator trace disappears when no submit or enter key has been pressed.

    35670 - Template is corrupted in Host screen preview.

    35730 - HATS administration language preference setting ignored and reset.

    35850 - Publishing a HATS Portlet on Portal 6.0 fails.

    36133 - In the Simplified Chinese RCP runtime environment, the text of host keypad buttons is truncated.

    36168 - Characters in the host screen capture display are incomplete.

    36390 - Project theme is changed when project is imported.

    36392 - BIDI: Integration Object extract shows incorrect text in RTL screen.

    36394 - Incorrect transformation selected when editing apply action.

    36427 - BIDI: RTL screen displayed as LTR when defining text replacement.

    36435 - Data in transformation not correctly aligned.

    36439 - Default component widget settings in Properties view incorrect.

    36448 - DBCS: Cannot input complete DBCS amounts into the O-Field.

    36451 - BIDI: Recognition of opposite component in alternative tag not working.

    36453 - BIDI: Wrong rendering of text in subfile headers.

    36464 - Exception logged when trying to use HATS administration for a HATS portlet.

    36510 - BIDI: Custom caption source shown wrongly for some RCP widgets.

    36514 - BIDI: Red rectangle in Global Rule settings editor shown mirrored for RTL screen.

    36520 - Project theme and template choices not saved for Web projects.

    36527 - DBCS: The cursor is in the wrong position on O-Field.

    36535 - JVE: Edit Host Component problem with Tabbed Folder

    36536 - RCP projects with an item selection component and radio button widget with auto submit have problems.

    36537 - Migrated portlet transformations flagged with errors by Rational Application Developer.

    36549 - Increase drop down list box size.

    36550 - Label and image decorators not appearing in HATS Projects view.

    36557 - Transformation created by Screen Combination Wizard is too large.

    36558 - When RCP applications use the 3270E print useWindowsPrinter=true, you cannot delete jobs.

    36569 - Wrong HATS tip displayed for new component class.

    36579 - HATS Administration and EJB project ears do not inherit license settings.

    36581 - Outlines of input fields are not complete on Linux.

    36585 - Style set to "HATSBUTTON" for Subfile action buttons.

    36589 - Specific subfile screen not rendered with small region in RCP.

    36595 - Field widget truncated at runtime and preview, but not in JVE.

    36603 - DBCS: DBCS characters are accepted on "SBCS Numeric Only" field.

    36604 - When combining screens and using Internet Explorer, the selected item loses focus if the page is partially redrawn.

    36606 - Provide more user-friendly message in Export Runtime Features wizard.

    36608 - Selection list with an empty action causes a Javascript error.

    36614 - RCP: Disabling keyboard support should allow for "enter".

    36616 - Add "New Update Site" to Project View context menu.

    36626 - Action buttons aligned in an invisible table.

    36627 - Text replacement across fields broken.

    36629 - End screen recognition "Anywhere on screen" option is not working.

    36633 - DBCS: Do not accept SBCS Space and DBCS on the either field.

    36635 - Cut and paste in HATS Host Terminal does not work.

    36641 - Admin_xx.properties is missing some language names.

    36643 - Wrong matching of Unicode numbers in RTL screens.

    36656 - Dependencies not calculated correctly for hostaccess launch configuration.

    36657 - ArrayIndexOutOfBoundsException with screen combination and table component.

    36658 - HATS portlet steals focus on click when multiple portlets on page and autoAdvance=true.

    36659 - Visual table not displayed by Netscape, Mozilla, or Firefox.

    36661 - Autoadvance is not working correctly for the Opera browser.

    36662 - RCP: Project names with periods don't behave as expected.

    36665 - Not easy to extend provided perspective.

    36666 - Script error in Studio running portlet project.

    36669 - DBCS: The final DBCS was trimmed when SO/SI is off.

    36671 - DBCS: Wrong data rendering in RTL tables in Model I Pages.

    36676 - DBCS: The final DBCS was trimmed on O field when SO/SI is off.

    36677 - Update font to Monospaced in Subfile Web.

    36678 - HATS main connection name is missing the (default).

    36684 - Right-click RCP application to see the context menu gives a Null Pointer Exception.

    36685 - Window > Show view > HATS EJB Project View causes stack overflow.

    36686 - Text on Application Keys is invisible.

    36702 - Slow performance for design view.

    36703 - The disconnectOnClose parameter does not work with URL rewriting.

    36708 - Add tracing and correct null pointer to Web application doGet method.

    36725 - Extract allows creation of table with duplicate column names.

    36735 - DBCS: DBCS characters allowed for connection names and Integration Objects.

    36738 - Message should be given when specifying a nonexistent macro.

    36746 - Don't allow random delay settings to be blank.

    36754 - DBCS: Wrong DBCS amounts on G/J Fields when using MaxLength.

    36756 - DBCS: Error after creating transformation name in RCP

    36757 - Update was.policy to System z and System i instead of zSeries and iSeries.

    36760 - RCP application dropping some characters during rapid updates.

    36761 - View Print Jobs button not displayed on host preview screens.

    36763 - BIDI: ARABIC shaping is corrupted.

    36766 - List and drop-down (entry) widgets don't appear in runtime.

    36768 - Table component selection works differently with 43*80 screen size than 24*80.

    36770 - Component settings for table component won't allow last column exclusion.

    36771 - Deleting screen customizations via context or delete key does not prompt for confirmation.

    36775 - Unchecking Include empty rows box not working with Table component in a Web application.

    36777 - BIDI: Wrong rendering of text in drop down list items.

    36789 - Interoperability: SIGNOFF ENDCNN(*YES) not properly handled.

    36807 - "Reverse screen" key in a Web project displayed as a button instead of a link.

    36812 - RCP: Table widget can't preview.

    36814 - BIDI: Wrong cursor position on auto field reverse.

    36815 - BIDI: Garbage symbol in input field after auto field reverse.

    36822 - BIDI: Inserted global variable does not honor screen orientation.

    36824 - Default ear file name does not change when the target server changes.

    36830 - Don't show RCP projects as targets for Integration Object Web page creation.

    36838 - DBCS: IME error when moving the cursor from a J-field or to an A-field or N-field on Windows Vista.

    36843 - BIDI: Wrong encoding in .cvs file.

    36845 - BIDI: Application error when creating screen combination.

    36846 - BIDI: Toolbar is not reversed on screen reverse.

    36847 - BIDI: Widget orientation does not change in screen combination.

    36848 - BIDI: Reverse text in widget not working for subfile widget.

    36849 - BIDI: Subfile component settings list is empty.

    36851 - DBCS: Accepted data is incorrect on A-Field if maxLength > original.

    36853 - Disconnect macro causes HPS5029 error on shutdown.

    36856 - RCP trace files display newest records before oldest.

    36868 - The ENPTUI scrollbar is not painting correctly for a rich client application when the theme in the Windows Display Properties is set to Windows Classic.

    36872 - DBCS: SO/SI disappears when using copy and paste into an O-Field.

    Additional software support

    Beginning with the HATS 7.0.0.3 refresh pack, HATS includes support for Windows Vista SP1.

    With Windows Vista SP1, the default Japanese font support is JIS2004, which HATS does not support at this time. Some characters entered with JIS2004 machines display as different character shapes than those displayed on a JIS90 machine, and some of the characters might not display on JIS90 machines at all. In addition, it is also possible that displayed characters and printed characters could have different shapes.

    Japanese customers who want to continue using JIS90 on the Vista operating system can install Microsoft service pack KB927490, which can be downloaded and applied through Windows Update as additional software.

    Beginning with the HATS 7.0.0.2 refresh pack, HATS includes support for Lotus Expeditor 6.1.1. With Lotus Expeditor 6.1.1, there is no need to uninstall HATS V7.0 rich client applications before installing the applications updated by HATS refresh packs.

    If you install the WebSphere Application Server Version 6.1 Feature Pack for Web Services, you can create HATS Web services for the IBM WebSphere Java API for XML-Based Web Services (JAX-WS) runtime. If you plan to create HATS Web services for the JAX-WS runtime, be aware of the following:

    Beginning with the HATS 7.0.0.1 refresh pack, HATS includes support for the following software:

    Development
    Windows Vista
    Runtime
    Windows Vista
    HP-UX 11iv2 (11.23) and 11iv3 (11.31) running on HP Integrity (Itanium)
    Client browser
    Internet Explorer
    Firefox 2.0

    Refresh pack limitations, known problems, and workarounds

    The following limitations apply after the installation of this refresh pack:

    Installing HATS maintenance

    HATS maintenance is delivered as a zip file and contains all fixes available since HATS Version 7 was first released.

    Note: Installation of this refresh pack requires the following:

    If either of these requirements is not satisfied, HATS will not appear in the Update Packages selection list.

    Follow these steps to install HATS maintenance:

    1. Download the HATS_7.0.0.5.zip file from the HATS support page to your system.
    2. Unzip the HATS_7.0.0.5.zip to a temporary directory.
    3. After unzipping the file, you have this file structure: temporary_directory\hats\updates.
    4. To find and install HATS maintenance, add the temporary_directory\hats\updates directory as a repository:
      1. From the IBM Installation Manager menu bar, select File > Preferences.
      2. On the Preferences panel, click Add Repository.
      3. On the Add Repository panel, click Browse.
      4. On the Select a Repository panel, browse to the temporary_directory\hats\updates directory, select the repository.config file, and click Open.
      5. On the Add a Repository panel, click OK.
      6. On the Preferences panel, click OK.
    5. From the IBM Installation Manager main panel, select Update Packages.
      Note: Do NOT select Install Packages.
    6. Select IBM Software Development Platform.
    7. Click Next.
    8. Select the version of HATS you want to update to in the selection list.
    9. Click Next.
    10. On the Update Packages panel, accept the terms of the license agreement.
    11. Click Next.
    12. Click Update.
    13. When the update installation is completed, click Finish to exit from the update package installation.

    After installing the HATS maintenance and restarting the Rational Toolkit, the HATS projects in the current workspace are automatically updated with the new files.

    HATS project files overwritten by the installation of HATS maintenance are saved. If HATS maintenance is uninstalled or disabled, HATS projects are not automatically restored to their former state. We recommend that you back up your existing HATS projects using a code repository, export them as zip files, or export them as project interchange files before applying HATS maintenance. See HATS project updates for more information.

    If your workspace contains rich client applications, see Installing the HATS runtime plug-ins into your rich client platform for important information.

    HATS project updates

    The project update process creates a backup folder in the project named Save_pre_7.0.0.5. This folder contains all of the files that were overwritten by the package update process. These files are saved so that you can compare and merge them with your newly installed HATS files. Do not worry if you see errors in the task view; these files are no longer used by the application. When you are satisfied that all the saved files have been compared and merged, you can delete the Save_pre_7.0.0.5 folder.

    Note:

    If you need to roll back to this version of HATS in the future, the files in this folder are required to perform the roll back. See Removing installed maintenance for more information.

    Installing the HATS runtime plug-ins into your rich client platform

    After applying a HATS service update, if you have changed the target platform of your workspace (Windows > Preferences > Plug-in Development >Target Platform) from the default Rational Software Delivery Platform, you are prompted to install the HATS runtime features and plug-ins into your target platform the first time you start RAD. For example, if the target platform of your workspace is Lotus Expeditor, you are prompted to install the updated HATS runtime plug-ins into this platform. After the plug-ins are installed, you are prompted to reload the target platform using the Windows > Preferences > Plug-in Development >Target Platform panel. Once the plug-in list is refreshed, you should see updated versions for the com.ibm.hats.core, com.ibm.etools.terminal.beans, and com.ibm.hsrendering plug-ins.

    Applying a service update to a client

    To apply a service update to a client that already has a HATS rich client application installed, follow the instructions in the HATS User's and Administrator's Guide for Exporting the HATS runtime features. This exports the updated versions of the HATS runtime features and plug-ins. To make these updates available to a client, you can either modify your existing update site to include the updated features, or you can create a new update site. See Creating an update site in the User's and Administrator's Guide for more information. Because a HATS service update does not update your rich client projects, there is no need to re-export or re-install your HATS rich client applications.

    If you used the New Product Configuration wizard to create a product package that includes Eclipse, HATS runtime plug-ins, and its dependencies, you need to regenerate this package and distribute it to your client machines. Instructions for creating a new product configuration can be found in the Packaging an Eclipse client environment for distribution section of the HATS User's and Administrator's Guide. There is no automated way to update plug-ins within an Eclipse environment that was packaged using the steps provided in the HATS User's and Administrator's Guide. This is a known issue.

    Removing installed maintenance

    After installing the HATS maintenance and restarting the Rational Toolkit, the HATS projects in the current workspace are automatically updated with the new files.

    You can remove installed HATS maintenance by selecting Roll Back Packages from the IBM Installation Manager main panel. Use the rollback feature if you have applied an update to a product package, and decide later that you want to remove the update and revert to the earlier version of the product. Installation Manager uninstalls the updated resources, and reinstalls the resources from the previous version. When you roll back to a previous version, it is restored with same features that were associated with the version.

    During the rollback process, Installation Manager must access files from the earlier version of the package. By default, these files are stored on your system when you install a package. If you changed the default setting or deleted the files on the Roll Back preferences page, Installation Manager will require access to your installation repository or media. If you installed the product from a repository, you must have listed the repository from which you installed the previous version of the product in your repository preferences (File > Preferences > Repositories).

    To roll back an updated package, complete the following steps:

    1. Select Roll Back Packages from the IBM Installation Manager main panel.
    2. From the Package Group Name list, select the package group that contains the package that you want to roll back.
      Note: The HATS package is installed under the IBM Software Development Platform.
    3. Click Next.
    4. Select the version of HATS that you want restored after the roll back.
    5. Click Next.
    6. Read the summary information and click Roll Back to roll back the package.
    7. When the roll back is completed, click Finish to exit from the Roll Back Packages panel.

    When you roll back HATS, HATS projects are not automatically restored to their previous level. See Manually restoring your workspace for more information.

    Uninstalling HATS from Rational Application Developer with WebSphere Developer for System z

    When HATS is installed on a system that has Rational Application Developer V7.0.0.2 along with WebSphere Developer for System z V7 or V7.0.0.1, there might be problems in uninstalling HATS. For more information, refer to http://www-1.ibm.com/support/docview.wss?rs=103&context=SS6UCR&dc=D600&uid=swg21258176&loc=en_US&cs=UTF-8&lang=en.

    Manually restoring your workspace

    Following a roll back of installed HATS maintenance, to manually restore your workspace to the state before HATS maintenance was installed, follow these steps:

    1. Shut down Rational Toolkit.
    2. Restore your HATS projects by copying the files in the Save_pre_7.0.0.5 folder back to their original locations.
    3. Restore your HATS EAR projects:
      1. Copy RSDP_shared_dir\plugins\com.ibm.hats_7.0.x\product.xml to the following locations:
        1. Each HATS EAR project
        2. Each RCP runtime extension project, if you have rich client applications
        3. Each HATS Web application linked to a WebFacing application for interoperability
          Note: The product.xml file must be renamed to hats_product.xml.
        where RSDP_shared_dir is the shared directory under the installed the RSDP product, and 7.0.x is the version you want to restore. The default for RSDP_shared_dir is C:\Program Files\IBM\SDP70Shared.
      2. Copy the following files to the root of each EAR project:
        • com.ibm.hats.core_7.0.x.x/lib/bidibean.jar
        • com.ibm.hats.core_7.0.x.x/lib/hatscommon.jar
        • com.ibm.hats.core_7.0.x.x/lib/hatsruntime.jar
        • com.ibm.hats.core_7.0.x.x/lib/hodwel.jar
        • com.ibm.hats.core_7.0.x.x/lib/ibmjlog.jar
        • com.ibm.hats.core_7.0.x.x/lib/hatsservice.jar
        • com.ibm.hsrendering_7.0.x.x/hsrendering.jar
        • com.ibm.eNetwork.beans.HOD_10.0.x.x/habeansnlv2.jar
        • com.ibm.eNetwork.beans.HOD_10.0.x.x/WFCommon.jar
        • com.ibm.eNetwork.beans.HOD_10.0.x.x/hasslite.jar
        • com.ibm.hostsim_7.0.x.x/hostsim.jar
    4. Reset the maintenance flag in the HATS preferences file:
      1. Edit the RSDP_shared_dir\plugins\com.ibm.hats_7.0.x\product.xml, Copy the build date to the system clipboard. The build date is included in the <date> tag under the <build> tag.
      2. Edit the workspace_dir\.metadata\.plugins\org.eclipse.core.runtime\.settings\com.ibm.hats.prefs file, where workspace_dir is your workspace folder. The default for workspace_dir is C:\Documents and Settings\user\IBM\rationalsdp7.0\workspace.
        Replace the value for the projectBuildDate keyword with the date you copied from the <date> tag under the <build> tag in the product.xml file.
      3. Save the file.

    Using silent install and uninstall

    As an alternative to using the graphical installation wizard in IBM Installation Manager, you can use the command line to install or roll back to a previous HATS version silently.

    Shown below are examples of the content of the HatsSilentUpdateInstall.rsp and HatsSilentUpdateUnInstall.rsp files. You can copy the sample code in the files to your hard drive and edit them to match your configuration. The files contain comments that explain their use. The value specified for each parameter must be enclosed in double quotes. Parameters that might need updating are:

    HatsSilentUpdateInstall.rsp 

     
<agent-input clean=true
<!-- ************************************************************************* 
Input parameters are samples only. Modify the parameter as needed before installing.
 
At a command prompt from IBM Installation Manager directory, for example, enter 
C:\Program Files\IBM\Installation Manager\eclipse\launcher.bat -silent -input <path\responsefile> -log <path\logfilename> 
************************************************************************** -->
<!-- create the profile if it does not exist yet --> 

<profile id="IBM Software Development Platform" 
         installLocation="C:\Program Files\IBM\SDP70"> 
</profile>
 
<!-- Specify repositories to be used during silent install --> 
<server> 
       <repository location= 
       "C:\HATS\Fix-builds\hats\updates\repository.config"> 
       </repository> 
</server>
 
<install>
        <offering profile="IBM Software Development Platform" 
         id="hats_offering" 
         version="7.0.4.200710150705">
        </offering> 
</install> 
</agent-input>

    HatsSilentUpdateUnInstall.rsp 

    <agent-input>
<!-- *********************************************************************************************************************
Input parameters are samples only. Modify the parameter as needed before uninstalling.

At a command prompt from IBM Installation Manager directory, for example, enter
C:\Program Files\IBM\Installation Manager\eclipse\launcher.bat -silent -input <path\responsefile> -log <path\logfilename>
********************************************************************************************************************** --> 
<!-- create the profile if it doesn't exist yet  -->
<profile id="IBM Software Development Platform" installLocation="C:\Program Files_IBM\SDP70">
</profile>

<!--  Use this command to rollback to the specified offerings from the version currently installed on the specified profile.  -->

<rollback>
         <offering profile= "IBM Software Development Platform"
          id= "hats_offering" 
          version= "7.0.0.5xxxxxxxxxx">
         </offering>
</rollback>

</agent-input>

    Updates, limitations, and known problems

    Updates, limitations, and known problems about Host Access Transformation Services are documented in the form of technotes on the IBM Software Support Web site.

    As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. The following link launches a customized query of the live Support knowledge base. To create your own query, go to the Advanced search page on the IBM Software Support Web site:

    View all technotes for Host Access Transformation Services

    Contacting IBM Software Support

    IBM Software Support provides assistance with product defects.

    Before you submit your problem to IBM Software Support, ensure that your company has an active IBM software maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

    If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the "Contacts" page of the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location.

    To contact IBM Software support, follow these steps:

    1. Determine the business impact of your problem.
    2. Describe your problem and gather background information.
    3. Submit your problem to IBM Software Support.

    Determine the business impact of your problem

    When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria:

    Severity 1 The problem has a critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.
    Severity 2 This problem has a significant business impact: The program is usable, but it is severely limited.
    Severity 3 The problem has some business impact: The program is usable, but less significant features (not critical to operations) are unavailable.
    Severity 4 The problem has minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented.

    Describe your problem and gather background information

    When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:

    Submit your problem

    You can submit your problem to IBM Software Support in one of two ways:

    If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.

    Trademarks

    The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

    Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

    Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

    Other company, product, or service names may be trademarks or service marks of others.