Bottom of Page | Previous Page | Next Page | Contents

Modifying a HATS project

When you created your project using the HATS Studio Create a Project wizard, the settings you chose on the panels were saved in a project application (.hap) file. You can use the project editor to view and modify those settings. You can invoke the project editor by double-clicking on the Project Settings node under the name of the project you want to modify in the HATS Project View tab of the HATS Studio.

The settings displayed in the project editor are the settings that are used for the entire project. If you want to modify any of the settings, you can use the tabs of the project editor to do so. Changes made in the project editor are automatically recognized when using Run on Server in the HATS Studio by clicking Refresh on the application keypad or by displaying a new host screen in the browser.

The following sections describe each tab of the project editor, and explain how they can be used to modify the project settings.

Overview tab

The Overview tab of the project editor summarizes all of the settings you specified when you created your project. The only item you can modify on this tab is the description of your project.

Each of the section headings on the Overview tab is a link to the other tabs of the project editor.

Connection Settings tab

The Connection Settings tab displays the following items:

The host name and port number fields are entry fields. You can change the name of the host to which your project connects or the port number through which your project connects by typing over the name and number that appear in these fields.

The type of session, code page, and screen size fields have drop-down lists from which you can select certain values for the fields.

The SSL enabled checkbox allows you to enable or disable SSL by checking or clearing the checkbox. If SSL is enabled, you can import the required certificate file using Import. Refer to Enabling SSL security for more information.

Notes:
  1. The values for screen size change depending on the code page and type of host session you select.
  2. If you select a bi-directional (BIDI) code page, refer to Enabling the user to reverse the screen direction.

Advanced Connection Settings tab

The Advanced Connection Settings tab enables you to specify settings for print support as well as any additional IBM WebSphere Host On-Demand connection session parameters you want to use.

Click the Enable print support checkbox if you want print support.

For 3270 hosts, if you check the Enable print support checkbox, you can choose the paper size, page orientation, and the print font you want to use for printing jobs from your project from the drop-down lists for each parameter. Refer to Defining print support for your project for more information.

For 5250 hosts, if you check the Enable print support checkbox, you must specify the URL of the iSeries(TM) for Web Access (IWA) Printer Output window. The default URL is http://hostname/webaccess/iWASpool, where hostname is the name of the 5250 host. The end user of your application can set print options in the IWA Printer Output window. Refer to Defining print support for your project for more information.

You can add, modify, or remove any IBM WebSphere Host On-Demand session parameters using the buttons to the right of the table of parameters. If you click Add, you can select a parameter using the drop-down list next to the Name field. For a list of the valid parameters that you can add and their descriptions, see <otherParameters> tag.

Template tab

The Template tab displays the template used to surround a transformation when applying a transformation is the action of a screen customization in your project. On this tab, you can change which template to use as the default template.

The default template is the template applied to all transformations in the project, and the template applied with the default transformation as the default action of the unmatched screen event. For infomation on how to modify the action of the unmatched screen event, see Screen customization ordering.

When creating or modifying the actions of a screen customization, you can override the default template chosen by selecting a different template.

Text Replacement tab

HATS applications can convert text strings on host screens into different strings on Web pages. These text strings must be protected text strings; that is, strings that are used only on the screen and never passed to the host application as input. For example, you can change the text string used as a field label or prompt, but not the text in an entry field.

The Text Replacement tab displays a table in which you can specify any text you want to replace, the text with which you want to replace the original text, and whether the texts are case sensitive.

Note:
Care should be taken when using text replacement. Text replacement with a disparate number of characters in the strings can cause changes in the HTML representation of the screen. Depending on the widget used for presenting a region of a screen, text on a line of the screen could be contracted, expanded, or forced to a new line.

You can add, modify, or remove any text replacement specifications by using the buttons to the right of the table of values.

Note:
If you select a bi-directional (BIDI) code page, refer to Additions to HATS files.

Event Priority tab

The Event Priority tab displays a list of the screen customizations contained in your project.

If the checkbox next to the name of a screen customization is checked, that screen customization is enabled for the project. When a screen customization is enabled, and the screen recognition criteria match the host screen, HATS performs the actions specified for that screen customization, and no more screen customizations are checked for matches. When a screen customization is disabled, HATS ignores the screen customization. If you want to test certain screen customizations, you might want to disable other screen customizations. If so, clear the checkbox while you are testing.

HATS applications check each incoming host screen against the list of screen customizations. If there are multiple screen customizations that match a given screen, the first screen customization that matches the screen is applied. The higher priority screen customizations should be near the top of the list. For example, you might have one screen customization that recognizes a few specific screens, and a second one that recognizes a more general set of screens. If the second screen customization is higher in the list than the first, a screen might be recognized by the more general screen recognition criteria and perform the associated actions, rather than recognizing the screen by the more specific criteria and performing the associated actions of the first screen customization.

If you want to change the priority of any of the screen customizations, highlight the screen customization by clicking it. Then click either Up or Down to move the screen customization higher or lower in the list.

For more information, see Screen customization ordering.

General tab

The General tab displays the settings for host components, widgets, keypads, keyboard support, and client locale.

You can customize the default project settings for each of these by clicking on the node in the customization settings tree. To change settings for individual host components and widgets, you must expand them in the tree to see the individual host components and widgets. Some of the host components and widgets do not have any customizable settings. For information on the settings that can be customized with the Insert Host Component wizard, see Component and widget settings.

You can override the default project settings for host components and widgets when you insert them into transformations. Those modified settings only apply to the individual instances of those host component or widget in the transformation. All the other instances of the host component or widget for any transformation in the project still use the default project settings, unless you modify them. For example, you have default settings for the VisualTable component. In a single transformation, you may have two VisualTable components; one that uses the default settings from the project settings, and another that uses modified settings.

Application keypad

You can customize the following settings for the application keypad:

Show default application keypad
Click the checkbox if you want a default application keypad defined in templates or transformations to be displayed in the HTML output when users interact with your application.
Select keys to display
If the Show default application keypad checkbox is checked, you can click the checkboxes next to each of the keys that you want to include on the default application keypad in the HTML output.
Display as
Select the value from the drop-down list to determine whether the selected keys display as buttons or links.

Host keypad

You can customize the following settings for the host keypad:

Show default host keypad
Click the checkbox if you want a default host keypad defined in templates or transformations to be displayed in the HTML output when users interact with your application.
Select keys to display
If the Show default host keypad checkbox is checked, you can click the checkboxes next to each of the keys that you want to include on the default host keypad in the HTML output. If you want to include all the available keys, you can click Select all. You can click Deselect all to clear all of the boxes that are checked.
Display as
Select the value from the drop-down list to determine whether the selected keys display as buttons or links.

Keyboard support

You can customize the following settings for keyboard support:

Turn keyboard support on
Click the checkbox if you want your end users to be able to use the physical keyboard keys to interact with the host. This enables the end user to click representations of host aid keys, such as the function, SYSREQ, or ATTN keys. However, if keyboard support is turned on, the end user will not be able to use those same keys for other functions, such as requesting help for the browser by pressing the PF1 key.
Turn initial keyboard state on
If the Turn keyboard support on checkbox is checked, you can click this checkbox to make the keyboard enabled when the HTML output is initially displayed to the user.

Client locale

You can customize the following settings for the client locale:

Select where to acquire the language to display button captions and messages
Click one of the following radio buttons:
From the browser's "Accept-Language" header
The language used to display button captions and messages is determined by the language specified by the end user's browser.
From the server's primary locale
The language used to display button captions and messages is determined by the locale of the machine where the application is deployed.
Always use the following language
You can select the language to use for button captions and messages from the drop-down list.

Source tab

The Source tab displays the tags and values in the application.hap file for all the settings you selected or defaulted to in your project. As you make changes on other tabs in the project editor, the tags and values displayed in the source file change to match.

You can also make changes to the tags and values in the source file, and they are reflected on the appropriate tabs of the project editor. For information about the tags in the application.hap file, refer to Application files (.hap).

[ Top of Page | Previous Page | Next Page ]