Optimus Server Solutions

Optimus Server Solutions > Server Platforms > IBM iSeries Services > IBM Host Access Transformation ( HATS ) Demo

IBM iSeries Services: 
HATS Demo

Clip 1: Convert your entire system quickly - View Movie
Clip 2: Review Standard Screen Rendering - View Movie
Clip 3: Simple Screen Rendering Enhancements - View Movie
Clip 4: How Did We Do That - View Movie
Clip 5: More Dramatic Rendering Changes - View Movie
Clip 6: Graphical Screen Rendering  - View Movie
Clip 7: Changing Screen Navigation - View Movie
Clip 8: Using Macros and Variables - View Movie
Clip 9: Componentizing Applications - View Movie
Clip 10: Extending Applications  -View Movie
.
Clip 1: Convert your entire system quickly
This example shows how to use the IBM WebSphere Development Studio for iSeries to create a project that converts all screens of your iSeries to GUI screens, and enables them to be accessed by a browser. As is demonstrated, you can accomplish this task in about 5 minutes.
View Movie

Clip 2: Review Standard Screen Rendering
This example shows the standard rendering of the project created in step 1. Notice that all iSeries screens are now GUI, browser screens. In step 3 we will se how easy it is to change default screen renderings. We will change how the Help Text Border is displayed, add a Date Picker to all screens, and add a Library Selection List to all screens.
View Movie

Clip 3: Simple Screen Rendering Enhancements
This example shows several changes to the last demonstration. We have changed the default browser border the Optimus Solution border used on our web site. We have changed the function keys to buttons. On every screen that asks for a Library, we have changed the default rendering to now provide a controlled drop down selection list. We have also added a date picker for all date fields. And finally we changed the way standard boarders are rendered.
View Movie

Clip 4: How Did We Do That
This example shows how we accomplish our simple screen rendering enhancements. We demonstrate how we change the default boarder rendering, then show you how we changed the rendering of function keys, show you how we created the library selection list, and finally show you how we added the date picker.
View Movie

Clip 5: More Dramatic Rendering Changes
The examples so far have shows fairly simple changes. The screens still look like iSeries screens. We now demonstrate capabilities of HAST that can produce significant changes on how screens are rendered. We will use HAST to render tabular screen information graphically. This is an example of the work with disk status command before we changed the screen rendering. The next example shows the changes we made.
View Movie

Clip 6: Graphical Screen Rendering
This example shows the changes we made to the work with disk status screen. When ever a user enters that command, the resulting screen will now display graphical representations of the screen. Notice that we used a tabbed folder to represent the data in several ways. The first tab shows the data in a table, the second tab shows the data in a graph. The third tab isolates the % used statistic, and shows that graphically. The fourth tab isolated the % busy statistic. Notice that the F5 key refreshes the information, just as it does on the standard iSeries screen.
View Movie

Clip 7: Changing Screen Navigation
We will now use HATS to demonstrate how to dramatically change how applications are presented to users. This example demonstrates a classic Run Query command to create an on the fly query, that enables a user to filter the records that are listed from an iSeries table. In the next example we will use HATS to make significant changes to how a user generates the query.
View Movie

Clip 8: Using Macros and Variables
Using HATS, we added a button to the iSeries Main menu. Clicking on the button runs a HATS macro that issues the Run Query command. It pauses for the user to enter the record filter criteria, and then proceeds to run the query. The results from the query are placed in a table variable, and then presented to the user.
View Movie

Clip 9: Componentizing Applications
In the last example we demonstrated how to significantly change a user’s interaction with a Run Query command, and display the results in a nicely formatted table. The solution still requires a user to sign on to the iSeries, and click on a button. With HATS it is possible to create Integration Objects that encapsulate HATS functions. We have encapsulated the Run Query command into an Integration object. We can now provide users a URL link to the Integration Object, and allow them to run the query. Notice that the user never signs on, never sees the iSeries menus, in fact, they do not know they are accessing an iSeries. Feel free to go to the City of Marietta web site and try the application for yourself.
View Movie

Clip 10: Extending Applications
Using HATS, it is possible to extend your legacy iSeries applications to the Internet in an appropriate and secure manner. In this example we show how the City of Marietta uses HATS to extend their legacy property tax application to the public. The legacy application is a purchased RPG application for which they do not have source code. The results form the tax query were produced by traversing four iSeries application menus, and over a dozen application screens. The user simply enters search information in one of three ways. HATS executes all the required menus, and traverses the application screens. As it traverses the screens, HATS places needed information into variables. When HATS has completed with all application screens, it formats the captured data and presents it to the user.
View Movie