IBM WebSphere Host Access Transformation Services, V7.0
At a Glance
IBM WebSphere Host Access Transformation Services (HATS) V7:
- Eclipse Rich Client Platform
- Simplified combination of multiple screens of tabular data
- Conversion of HATS table component data to a spreadsheet file
- Integration of Host Simulator tool with HATS toolkit to allow easier "offline" HATS development
- HATS and WebFacing application runtime interoperability
Eclipse Rich Client Platform support
HATS gives you the ability to transform access to your existing host applications using rich client GUI applications that run in Eclipse Rich Client Platform (Eclipse RCP) or Lotus Expeditor Client environments. The Eclipse RCP is a subset of plug-ins provided by the Eclipse platform, which is best known as an open source tooling platform. The introduction of Eclipse RCP enables you to use the core functionality provided by Eclipse to build native client applications targeted for a user's desktop. Lotus Expeditor Client provides a rich client runtime environment and integrated middleware components for extending many enterprise applications to server-managed laptop and desktop systems.
A rich client environment offers capabilities not available in a traditional Web environment, including:
- Improved response time
- A richer set of user interface (UI) widgets which provide for a more native application appearance, for example, native tab folder control, editable combo boxes, toolbars, menu bars, and tables
- No dependency on WebSphere Application Server or WebSphere Portal
- Client side processing (distributed, not centralized on a single server)
- Printing 3270E print jobs directly to a user's local printer
Simplified combination of multiple screens of tabular data
A new screen combination wizard and editor are provided to make it easier to combine data from multiple host screens that can be navigated using a repeatable system of navigation. The wizard and editor provide a method of defining the screen recognition criteria for the beginning and ending screens, how to navigate from screen to screen, the screen region containing the data to gather, and the component and widget to use to recognize and render the gathered data.
Conversion of HATS table component data to a spreadsheet file
HATS has the ability for host data to be converted to a format that is easily consumed by a spreadsheet program. At runtime, the Table widget will generate a temporary .csv file or .xls of the table and provide a button or link as part of its output. When an end user clicks the button, the (already generated) file would be retrieved and opened appropriately on the end user's machine.
Integration of Host Simulator tool with HATS toolkit to allow easier "offline" HATS development
The HATS Toolkit includes a host simulation capability. With this capability, you can record host simulation trace files that can be saved and then used instead of a live host connection. Following are ways you can use host simulation files instead of using a live host connection.
- Create screen captures, screen events, and screen transformations using the host terminal function.
- Create and test macros using the host terminal function.
- Test HATS applications using the Rational SDP local test environment.
- Deploy HATS applications to a runtime environment to use as demonstrations.
In addition, the host simulation capability can be used in troubleshooting by allowing you to record a host simulation file in the runtime environment that you can use, along with other traces and logs, to document a failing scenario.
HATS and WebFacing application runtime interoperability
HATS interoperability with WebFacing applications provides the ability to perform data description specification (DDS) map transformation, as well as 5250 data stream transformation, within the same Web application. This function is particularly useful for those who have built a DDS source-based transformation application, using the WebFacing tool, that needs to interact with a host application that has been transformed using the HATS tool. This function is also useful for HATS users who want to take advantage of transformation, based on DDS maps, provided by the WebFacing tool. With this support, a HATS application and a WebFacing application can be linked together to interoperate as a single enterprise application and use a single connection to a WebFacing server.
Note: The use of this function requires either WebSphere Development Studio Client (WDSC) or WebSphere Development Studio Client Advanced Edition (WDSC AE) and a license for WebFacing Deployment Tool for WebSphere Development Studio with HATS Technology (WDHT).
Rendering patterns for transformations
When you create a new transformation for a host screen, you select a rendering pattern to use for the transformation. In addition to the Blank and Prepopulated (now named Prepopulated using Default Rendering) patterns, HATS now provides two new patterns, Default Rendering and Prepopulated using Fields, from which you can select.
The Default Rendering pattern creates a new transformation that displays with default rendering at runtime. With this pattern you can use default rendering with a non-default rendering set, or use default rendering and add individual components using the Insert Host Components wizard. An Options button is provided to select the rendering set to use. If you select the Use the default rendering set check box, the default rendering set that is current at runtime is applied. If you clear the check box, you can select a specific rendering set to always use.
The Prepopulated using Fields pattern creates a new transformation prefilled with labels and input fields that can be customized using the Edit Host Component wizard.
A Preview button is provided to display the transformation using the selected pattern.
Improved testing modes
The Run on Server (for Web projects) and Run (for rich client projects) testing modes can be used to modify and test the runtime settings, defined in the runtime.properties file, that are deployed to the production environment. The Debug on Server (for Web projects) and Debug (for rich client projects) testing modes can be used to modify and test runtime settings without modifying the settings, defined in the runtime.properties file, that are deployed to the production environment.
New and improved host components and widgets
Host components are HATS objects that are responsible for recognizing elements of the host screen. Widgets are HATS objects that are responsible for rendering recognized host components in a GUI for a host screen. Following are new host components and widgets plus some of the new settings for existing components and widgets provided in HATS Version 7.0. Highlights include a new Table component, new List, Subfile, Combo (RCP only), and Toolbar (RCP-only) widgets, and a new option on the Table widget that allows the user to retrieve table data in spreadsheet file format.
Project Themes
A new project theme wizard provides a simple method of setting, and later changing, a theme for the overall appearance and behavior of a HATS application. Using the wizard you can select whether you want the application to appear more like an emulator, more like a modern application, or a custom setting somewhere in between. There are many options in the HATS project settings that change the appearance and behavior of the application. For example, options like Show OIA, Enable auto advance, and Enable overwrite mode can be used to enable a HATS application to behave more like an emulator. The new wizard provides a convenient method of setting the options in one place that together can be treated as a theme.
Action required for WebSphere Application Server users: The passage of the Energy Policy Act of 2005 alters the Daylight Saving Time (DST) start and stop dates by four weeks. Extended Daylight Saving Time will begin in March of 2007. As a result of this change, APARs, maintenance, or actions will be required for the WebSphere Application Server and operating systems. Information about the Energy Policy Act can be found on the US Department of Energy Web site. Please visit the following IBM Web site for details:
URGENT! Actions Required: Changes to Daylight Saving Time will affect IBM WebSphere Application Server and its associated Operating Systems
For information concerning the Western Australia Daylight Saving Time impact on WebSphere Application Server as of 3 December 2006, please follow this link.
Learn more about the WebSphere software platform
To learn more about how the IBM WebSphere software platform can help you succeed in e-business, contact your IBM representative, IBM Business Partner or visit http://www.ibm.com/websphere.
