Introducing Host Access Transformation Services

This book provides the information you need to understand the IBM® Rational® Host Access Transformation Services (HATS) product, install HATS Toolkit, and use it to develop simple applications. After you have familiarized yourself with the concepts in this book and used HATS, you can find more advanced information in the HATS User's and Administrator's Guide, the HATS Web Application Programmer's Guide, the HATS Rich Client Platform Programmer's Guide, the HATS Advanced Macro Guide, and Developing WebFacing Applications.

What is HATS?

With HATS, you can create Web applications, including portlets, and rich client applications that provide an easy-to-use graphical user interface (GUI) for your 3270 applications running on IBM System z® platforms and your 5250 applications running on IBM i operating system platforms. HATS applications can access 5250 applications without requiring Online Transaction Processing (OLTP) capacity. In this book, these character-based 3270 and 5250 applications are referred to as host applications. You can also create service-oriented architecture (SOA) assets using Web services that provide standard programming interfaces to business logic and transactions contained within host applications. Data from virtual terminal (VT) emulation screens can also be accessed.

HATS applications can be given a modern appearance. HATS Web applications, including portlets, can be developed with an interface that matches your company's Web or portal pages, and your users can access them through their Web browsers. HATS Web applications can also be developed to provide access from mobile devices such as cellular phones, data collection terminals, and personal digital assistants (PDAs).

HATS rich client applications can be developed to run in an Eclipse Rich Client Platform (RCP) implementation, in Lotus Notes®, or in the Lotus® Expeditor Client to provide native client applications targeted for a user's desktop. For more information about the Eclipse RCP environment see http://www.eclipse.org/home/categories/rcp.php. For more information about Lotus Notes see the Lotus Notes Information center at http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp. For more information about the Lotus Expeditor Client see the Lotus Expeditor Information Center at http://publib.boulder.ibm.com/infocenter/ledoc/v6r2/index.jsp.

Note:
Throughout this document, configuration settings that apply only to HATS Web applications, including portlet and EJB applications unless otherwise noted, are marked with  Web-only . Configuration settings that apply only to HATS rich client platform applications are marked with  RCP-only .

HATS has two components:

The following figure shows the stages of development, deployment, and runtime for a HATS Web application. If the application is a portlet, the stages are similar except that the portlet is installed and run on a WebSphere Portal system.

  1. The developer uses the HATS Toolkit to develop and test a HATS Web application.
  2. When ready, the developer deploys the HATS application by exporting it as a Java™ EE application and installing and running it on a WebSphere Application Server system.
  3. Using a Web browser, the user accesses the HATS application.
  4. The HATS runtime connects to the target host system through either a Telnet or a WebFacing server.
  5. As the user interacts with the host through the HATS application, the HATS runtime transforms host screens to a GUI.
Figure 1. HATS Web application
HATS Web application

The following figure shows the stages of development, deployment, and runtime for a HATS rich client application.

  1. The developer uses the HATS Toolkit to develop and test a HATS rich client application.
  2. When ready, the developer exports the HATS application as an Eclipse feature, creates an update site containing the application feature, and uploads it to a Web server for deployment.
    Note:
    Different methods can be used for deploying HATS rich client applications. For example, Lotus Expeditor Server can be used to centrally manage the software deployed to Lotus Expeditor Client systems. For more information see the HATS User's and Administrator's Guide.
  3. The user, running a rich client platform, downloads and installs the HATS application feature from the update site.
  4. The user starts and accesses the HATS application using the rich client platform environment.
  5. The HATS runtime connects to the target host system through either a Telnet or a WebFacing server.
  6. As the user interacts with the host through the HATS application, the HATS runtime transforms host screens to a GUI.
Figure 2. HATS rich client application
HATS rich client application

A HATS example

Imagine you need to create a GUI for a host application. With HATS you have a choice of providing the GUI using a Web application (including portlets) or a rich client application. For more information about the use of HATS portlets and rich client applications, including advantages, considerations, and limitations, see the WebSphere Portal and HATS chapter and the Developing and deploying rich client applications chapter in the HATS User's and Administrator's Guide.

The following figure shows a screen from the host application:

Figure 3. A host terminal screen
A host terminal screen

If you decide to create a Web application that provides the GUI, you use a wizard to create a simple HATS Web project. You give your project a name and specify the host machine where the host application runs. You take all the defaults and add no customization. After just a few minutes, you use the preview function to see the host screen transformed to this:

Figure 4. A default Web transformation
A default Web transformation

As you can see, HATS has added a banner across the top of the screen and a navigation area on the left, but has made minimal changes to the original host screen. This Web page may not yet be what you want to show to your users. Now you do some customizations. You change your template. After each modification you make, you preview the screen to evaluate your changes. Soon your page looks like this:

Figure 5. A customized Web transformation
A customized Web transformation

After a very short time, you have transformed the host screen into an attractive Web page that provides all the function of the host screen and more, and is accessible through a Web browser. You decided to switch to a template more suited to your business. You hid unnecessary information, and created a table to display only required input fields. You provided a drop-down list of valid values for an input field and use of a calendar widget for another input field. Finally, you changed the size and location of some of the text and provided navigation buttons.

If you decide to create a portlet, you can generally follow the same steps for creating a Web application and then use the HATS function to generate a portlet from a Web application.

If instead of creating a Web application, you decide to create an application that runs on a rich client platform, you also perform basically the same steps. You use a wizard to create a simple HATS rich client project. You give your project a name and specify the host machine where the host application runs. You take all the defaults and add no customization. After just a few minutes, you use the preview function to see the host screen transformed to this:

Figure 6. A default rich client transformation
A default rich client transformation

As you can see, HATS has added a banner down the left side of the page, but has made minimal changes to the original host screen. This GUI may not yet be what you want to show to your users. Now you do some customizations. You change your template. After each modification you make, you preview the screen to evaluate your changes. Soon your transformation looks like this:

Figure 7. A customized rich client transformation
A customized rich client transformation

After a very short time, you have transformed the host screen into an attractive GUI that provides all the function of the host screen and more, and is accessible using a rich client application. You decided to switch to a template more suited to your business. You hid unnecessary information, and display only required input fields. You provided a drop-down list of valid values for an input field, changed the size and location of some of the text, and provided navigation buttons.

Whether creating a Web application or a rich client application, you might decide that this is enough customization, but with HATS you can add much more. For example, you can:

How to add these and other types of customization is discussed in the remainder of this book and in the HATS User's and Administrator's Guide.

What's new in HATS

HATS V7.5

Visual Macro Editor

HATS V7.5 includes as standard support the HATS Visual Macro Editor function previously available as a technology preview.

The Visual Macro Editor is a tool for visually developing HATS macros. Macros are scripts that navigate through and interact with 3270, 5250, or VT host applications. Macros are used in HATS transformation applications and HATS Web Services. The Visual Macro Editor combines many of the features of the HATS host terminal, Macro Editor, and Advanced Macro Editor into one tool, and allows for offline development of macros. It also allows flows to be copied between macros and provides drag-and-drop support for adding new screens. By default, screen captures are automatically created for every screen navigated while recording a macro. These screen captures can be used within the Visual Macro Editor if you must later make changes to the macro.

Note:
Support for the Macro Editor and the Advanced Macro Editor is deprecated in HATS V7.5. This support is replaced by support for the Visual Macro Editor.

New supported environments

HATS V7.5 extends the supported environments in which developers can create, test, and deploy HATS applications that allow users to access host applications in a modern, transformed way. These new environments include Rational SDP V7.5, WebSphere Application Server V7.0, WebSphere Portal V6.1, Eclipse V3.4, and Lotus Expeditor V6.2.

HATS V7.5 does not support Rational SDP V7.0, WebSphere Application Server V5.1, or WebSphere Portal V5.1.

Note:
See the HATS Information Center at http://publib.boulder.ibm.com/infocenter/hatshelp/v75/index.jsp for the current list of supported hardware and software prerequisites. In the Contents under HATS prerequisites, select Detailed System Requirements.

HATS V7.5.1

Web Express Logon for standard portlets

Web Express Logon (WEL) gives you a mechanism to authenticate users and provides them with single signon capability. This support, previously available only for Web applications and IBM portlets, is now available for standard (JSR 168) portlets.

For more information see the chapters, WebSphere Portal and HATS and Security and Web Express Logon in the HATS User's and Administrator's Guide.

Simplified Web service definitions

You can now create simplified Web service definitions from Integration Objects or EJB access beans by selecting only the desired input and output properties that you want exposed as parameters for the Web service, eliminating the need to expose them all. You can also customize the input and output property names.

For more information see the section, Creating a Bottom-up Web service from Integration Objects, in the HATS Web Application Programmer's Guide.

Rich client application support for Lotus Notes

HATS rich client applications provide native client applications targeted for a user's desktop that provide an easy-to-use graphical user interface (GUI) for 3270 applications running on IBM System z platforms and 5250 applications running on IBM i operating system platforms. HATS rich client applications can be now be targeted to run in a Lotus Notes environment in addition to existing support for Eclipse Rich Client Platform (RCP) and Lotus Expeditor Client environments.

For more information see the chapter, Developing and deploying HATS rich client applications, in the HATS User's and Administrator's Guide.

Mobile device support for iPhone and iPod touch devices

You can develop HATS Web applications that provide screen transformation access to your host applications from mobile devices such as cellular phones, data collection terminals, and personal digital assistants (PDAs). This capability is now extended to support iPhone and iPod touch devices. This allows you to improve the productivity of your increasingly mobile workforce and can help you broaden your customer base and improve your level of service.

For more information about HATS support for mobile devices see the section, Developing HATS applications for mobile devices, in the HATS User's and Administrator's Guide.

Automatic disconnect and refresh for Web screen transformation applications

You can improve the performance, usability, and supported environments of HATS Web screen transformation applications through the use of new AJAX-based auto-disconnect and auto-refresh functions.

Use of these new functions, instead of the previously supported asynchronous update applet-based functions and disconnectOnClose parameter, simplifies configuration, eliminates the need for an additional connection to the HATS server from each browser, and extends support to all browsers supported by HATS.

The auto-disconnect function provides the ability to detect when the browser has been out of contact with your HATS application for a predefined period of time. When detected, disconnect processing is performed, for example running the disconnect macro, to clean up resources associated with the browser session and thereby reduce the load on the server.

The purpose of the auto-refresh function is to automatically refresh the Web page view of your HATS application if the underlying host screen changes because the host sent a new screen. This eliminates the requirement for the user to click the Refresh button to see asynchronously changed screens from the host.

For more information see the section, Automatic Disconnect and Refresh , in the HATS User's and Administrator's Guide.

Note:
Use of the asynchronous update applet is deprecated. The AJAX-based auto-disconnect and auto-refresh functions should be used instead.

New templates

Templates enable you to provide a consistent appearance for all of the pages of your HATS application. HATS V7.5.1 includes two new templates that provide examples of new navigational menus, layouts, color schemes, and graphics, which can help provide an improved "out-of-the-box" experience.

These new templates match the new WebFacing styles. They are marked with an asterisk on the Template tab of the Project Settings editor.

For more information see the section, Template examples , in the HATS User's and Administrator's Guide.

Visual Macro Editor support for non-text host screen planes

Using the Visual Macro Editor, you can extend your HATS macros to extract and provide reuse of data from non-text planes of the host screen. You can use this extra screen information to enhance the graphical user interface you provide with your HATS applications and thereby provide a more meaningful user experience. The supported non-text planes are the: Color, Field, Extended Field, DBCS, and Grid planes.

For more information see the section, Extract action , in the HATS Advanced Macro Guide.

Enhanced Calendar widget

The Calendar widget is responsible for rendering an input field with an associated launcher button, link, or image. This launcher opens a calendar date picker which your users can use to select a date. This date is then inserted into the associated input field.

An enhancement to the calendar widget lets you specify that the date picker be displayed in the current Web page instead of in a new browser window. This is helpful in cases where pop-up blockers prevent the display of the date picker in a new browser window. The visual appearance of the enhanced calendar date picker is also better integrated with HATS templates for a more consistent look.

For more information see the section, Calendar , in the HATS User's and Administrator's Guide.

Improved 3270 numeric field support

A new setting for the Field and Text input widgets allows you to specify that the user can enter only numbers 0 through 9, plus sign, minus sign, period, comma, and bidirectional values into 3270 numeric fields.

For more information see the sections, Field and Text input, in the HATS User's and Administrator's Guide.

Coexistence

HATS V6, V7.0, V7.1, and V7.5 can coexist on the same development system with HATS V7.5.1. It is also possible for HATS V7.5.1 to be installed multiple times on the same system. If you have multiple Rational SDP offerings installed on your system, HATS V7.5.1 can be installed into each of them.

Migration

If you are a HATS V4 LE, HATS V5 LE, HATS V4, V5, V6, V7.0, V7.1, or V7.5 user, you can migrate your projects to HATS V7.5.1.

If you are a Host Publisher V4.0 or V4.01 user, you can migrate whole applications, or just the Integration Objects.

For more information about migrating to HATS V7.5.1, see the

HATS User's and Administrator's Guide

Serviceability

IBM Support Assistant

The IBM Support Assistant (ISA) can help you simplify software support, reduce support costs, and improve your ability to resolve software problems in-house quickly. ISA is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. For more information see the ISA Web site at http://www.ibm.com/software/support/isa/.

HATS provides a plug-in for ISA V4.x. The HATS plug-in provides links to the HATS Information Center, home page, support site, education assistant site, and other sites. You can search these sites for information that may help you resolve a problem. For information about how to install the HATS plug-in, see the section, Use the IBM Support Assistant, in HATS Troubleshooting.

Roles and skills

A number of different people, each with different roles within your organization, can be users of HATS. Depending on the role, skills ranging from a beginning user to an advanced developer may be required. The following roles and skills are involved in HATS application development, deployment, administration, and usage:

Casual Web developer

A user of the HATS Toolkit. The developer creates and edits a HATS Web application using Rational SDP and the HATS perspective.

Skills expected:
Creating a default application may require minimal HTML, JSP, and cascading style sheet (CSS) skills. Editing transformations and templates may require minimal to advanced HTML, JSP, CSS, and JavaScript™ skills.

Advanced Web developer

A HATS Toolkit user who is already familiar with Rational SDP and advanced topics such as servlets, EJBs, Struts, JSF, and Web services. The developer creates and edits a HATS Web application using Rational SDP and the HATS perspective. The developer also creates business objects (Integration Objects) based on HATS macros, and integrates these with other back-end systems.

Skills expected:
Highly skilled in HTML, JSP, CSS, JavaScript, and Java EE application environments.

Casual rich client developer

A user of the HATS Toolkit. The developer creates and edits a HATS rich client application using Rational SDP and the HATS perspective.

Skills expected:
Creating a default application may require minimal Java skills. Editing transformations and templates requires skills using the Java Editor or Visual Editor and minimal to advanced Java skills.

Advanced rich client developer

A HATS Toolkit user who is already familiar with Rational SDP and advanced topics such as SWT widgets and Eclipse plug-ins. While creating and editing a HATS rich client application using Rational SDP and the HATS perspective, the developer might create custom components and widgets, integrate business logic, and create custom perspectives.

Skills expected:
Highly skilled in Java, SWT, and Eclipse plug-in development.

User

HATS has two types of users. The browser-based user and the rich client-based user of a HATS application. The browser-based user invokes the application, either through a direct URL request to the application or through a portal, and uses the resulting host session to work with a host application. The rich client-based user clicks an icon that will establish a host session.

Skills expected:
Web browser or rich client platform common usage is all that is required.

HATS administrator

The person who administers HATS Web applications including portlets. This may be the same person as the WebSphere Application Server administrator or the WebSphere Portal administrator. This person has the ability to monitor the number of HATS sessions and manually stop connections in error cases. Currently, this role only exists for the HATS Web application and portlet environments.

Skills expected:
Web browser common usage along with HATS problem determination skills.

WebSphere administrator

The person who administers WebSphere Application Server. The WebSphere administrator is responsible for deploying HATS applications that have been packaged as .ear files and transferred to the production system. This role exists for the HATS Web application environment.

Skills expected:
Web browser common usage along with HATS and WebSphere Application Server problem determination skills.

Rich client administrator

The person responsible for installing, provisioning, and deploying HATS rich client applications.

Skills expected:
Skills with maintaining update sites along with rich client platform and HATS problem determination skills.

WebFacing developer

The user of the IBM WebFacing Tool for IBM i feature. Using Rational SDP and the WebFacing perspective, the WebFacing developer creates and edits a WebFacing application to convert IBM i data description specification (DDS) display file source members into a Web-based user interface for 5250 programs.

Skills expected:
Creating an application requires knowledge of the location of the DDS source required by the 5250 program; customizing the Web interface may require HTML, JSP, CSS, and JavaScript skills.

Independent software vendors

Independent software developers use the HATS Toolkit to create custom applications that are resold to other customers.

Accessibility

Accessibility features help a user who has a physical disability, such as restricted mobility, limited vision, or other special needs, to use software products successfully. As a set of plug-ins of Rational SDP, HATS takes advantage of the accessibility capabilities provided by Rational SDP. These are the major accessibility capabilities in Rational SDP:

Accessibility when using HATS

Keep the following in mind when using HATS:

Notes:
  1. HATS supports accessibility for Web applications only when using Internet Explorer.
  2. HATS supports accessibility for rich client applications in both the application and transformation views.

Keyboard shortcuts

Ctrl + F9
When a region of the host screen is selected, a new dialog box opens up that displays the selected text.

Where can I find more information about accessibility?

For more information about accessibility, refer to the following Web sites:

Where can I find information about HATS?

The following HATS information is available before you install HATS:

In addition to the information available before installing HATS, the following information is available on the system after installing HATS: