Understanding HATS resources

Each HATS project contains a set of different types of resources (artifacts). You can see the resource types listed under the project name in the HATS Projects view in the HATS Toolkit. This section defines the key resource types. For definitions of other HATS resources see the Glossary.

Connection: A connection is a set of parameters, stored in an .hco file, used by HATS to connect to a host application.
Screen event: A screen event is a HATS event that is triggered when a host screen is recognized by matching specific screen recognition criteria. There are two types of screen events, screen customizations and screen combinations.
Screen customization: A screen customization is a type of screen event designed to perform a set of actions when a host screen is recognized. A screen customization definition, stored in a .evnt file, includes a set of criteria for matching host screens, and a list of actions to be taken when a host screen matches these criteria. Screen customizations are described in Working with screen events.
Screen combination: A screen combination is a type of screen event designed to gather output data from consecutive, similar host screens, combine it, and display it in a single output page. The screen combination definition, stored in a .evnt file, includes a set of screen recognition criteria for both the beginning and ending screens to be combined, how to navigate from screen to screen, and the component and widget to use to recognize and render the data gathered from each screen. Screen combinations are described in Working with screen events.
Screen capture: A screen capture is an XML representation of a host screen, stored in a .hsc file, used to create or customize a screen customization, screen combination, transformation, global rule, or macro. Screen captures are useful because they enable you to customize an application even when not connected to the host. They are also useful in creating macros which are the core of HATS Integration Object and Web services support.
Screen captures of video terminal (VT) host screens can be used to create or customize a macro using the Visual Macro Editor and as the check-in screen when configuring pooling. They cannot be used to create screen customizations, screen combinations, transformations, default rendering, or global rules.
Macro: A macro, stored in a .hma file, automates interactions with the host. It can send commands to the host, enter data into entry fields, extract data from the host, and be used to navigate screens on behalf of the user. Macros are described in the Introducing advanced macros.
Template: A template, stored in a .jsp file (for Web projects) or a .java file (for rich client projects), controls the basic layout and style (such as color and font) of the application. It also defines the appearance of areas that are common in most of your GUI, such as a banner and a navigation area. Templates are described in Updating your project's template.
Transformation: A transformation stored in a .jsp file (for Web projects) or a .java file (for rich client projects), defines how host components should be extracted and displayed using widgets in your GUI. Transformations are described in Working with transformations.