1. What’s new in HATS 9.5 Tim Parker, HATS SME HATS Development team
Alisa Morse, Host Integration and RD&T Offering Manager

2. Agenda HATS- why and what What’s new in HATS 9.5 Examples
Demonstration
Wrap up
Q&A

3. Enterprises want to…. But…
Improve application UI to
Reduce learning curve for newer employees
Extend to new customers who rely on web application ease-of-use
Streamline application flow to improve employee productivity
Automate where appropriate - eliminate unnecessary keystrokes
Customize access for a specific set of users
Eliminate or reduce administration and maintenance of terminal emulation clients
Leverage “integration at the glass” with portal technology
Access existing applications from a common portal
Use existing applications in their new business processes
Web Services based mobile and composite applications
Integrate with new JEE, .NET, etc. applications for totally new user interfaces and/or business process automation
But…
Re-architecting, rewriting or refactoring is time consuming and risky!

4. Solution: Rational Host Access Transformation Services (HATS)
Quickly and easily transform green screen applications to Web services, Web, Mobile, Portal and rich client interfaces
Integrate host business processes and data with other web, portal, mobile, and rich client applications
Greater customer satisfaction, lower employee training costs, and fewer errors from more modern and compelling UIs
Low cost and low risk: No need to rewrite or refactor existing applications and built on open, proven platforms and technologies
Aon Integramark increased internal efficiency by as much as 85 percent because staff members save more than one minute per database query

5. HATS Deployment options
Web
Rich Client
View through your favorite browser
Zero footprint
3270 or 5250 datastream
Portal
Integration at the desktop with other Eclipse applications
Client side processing
Rich set of user interface widgets
Built on the standard, open Eclipse foundation
3270e print directly to end user’s printer
Mobile
Web Service
Integration at the glass
Cooperative portlet support
Build self-service transactions
PDA, Smart Phones, Data Collection terminals

6. Modernization at your own pace
Today
Day 1
Tomorrow

7. Modernization at your own pace
Today
Day 1
Tomorrow
Modern UI: All pages share the same theme and style, which can be based on an existing Web site.
Instant Value: HATS default rendering automatically transforms actions into clickable links and buttons. No changes required to the host application.

8. Modernization at your own pace
Today
Day 1
Tomorrow
Integration: Text can be replaced with images, input fields can be populated from data on other screens or from a database, date fields can be converted into popup calendar widgets, and more!
Modern UI: All pages share the same theme and style, which can be based on an existing Web site.
Instant Value: HATS default rendering automatically transforms actions into clickable links and buttons. No changes required to the host application.
Aggregation: data from other screens, databases, or other systems can be merged and displayed with host data.

9. Visual Macro Editor (VME)
Palette
Add new screens and actions.
Connect screens together.
Design Canvas
High-productivity macro (script) development
Web services are created from macros
Easy visualization/expression of alternate / error flows
Flows can be analyzed by developers, expert users, and business analysts
Source Editor
Integrated Terminal
Add new screens
Test macro

10. HATS Web services…
HATS generates standard SOAP or RESTful web service interfaces
Reuse with HATS enables you to extend the value of the applications and business processes that currently run your business, not replace them.
HATS does not require reengineering or rewriting
Rewriting consumes a significant amounts of time and resources, plus access to and understanding of application source code.
Rewriting inherently introduces new bugs that must be found and fixed.
Rewriting is not an option for some customers
HATS is unique
HATS is the only IBM product that web Service-enables 3270, including CICS and IMS, 5250, and VT terminal applications – great for customers with a mix of applications (one tool can be used to enable all of them).

11. What’S NEW in HATS 9.5

12. Prerequisites
IBM® Installation Manager Version 1.8.3, or later, is required.
One of the following Rational SDP packages, or later fixpacks, including the WebSphere® Application Server v7.0, v8.0, or v8.5 development tools features:
Rational Application Developer for WebSphere Software V9.5
Rational Business Developer V9.5
Rational Software Architect for WebSphere Software V9.5
Rational Developer for i V9.5

13. Support for Latest Web Browsers
The latest browser levels are support by the HATS web runtime.
See Software prerequisites for more information.
Microsoft Internet Explorer 9.0 and future modification levels and fix packs
Microsoft Internet Explorer 10.0 and future modification levels and fix packs
Microsoft Internet Explorer 11.0 and future modification levels and fix packs
Google Chrome 40 and future modification levels and fix packs
Mozilla Firefox 38 and future modification levels and fix packs
Apple Safari 8.0 and future modification levels and fix packs
Apple Safari on iOS 8.0 and future modification levels and fix packs
Android default browser 4.1 and future modification levels and fix packs

14. Support For The Latest Runtimes
New supported HATS runtime environments include:
WebSphere Application Server V
WebSphere Application Server Liberty Core V
WebSphere Portal Server V8.5
Geronimo 3.0.1
WebLogic 12c
See Software prerequisites for more information.

15. Support For IBM Bluemix Server
With HATS V9.5, you can create, run and debug HATS applications on the IBM Bluemix Server. This enables easy integration of HATS applications into a hosted cloud environment on IBM Bluemix.
For more information visit
Run/Debug HATS application on Bluemix
Select Bluemix as the target server in HATS project creation wizard

16. TLS 1.1 and 1.2 Connectivity
HATS 9.5 includes the ability to choose the Java Secure Socket Extensions (JSSE) for secure connections. This will result in HATS trying the highest level of secure connection first, TLS 1.2, then TLS 1.1, and then TLS 1.0 connectivity.
This feature can be enabled under the Security panel of the Connection editor.
Enabling JSSE option requires Java KeyStore (.jks) file to be used as the certificate store instead of PKCS12 (.p12) file
Note: SSL v3.0 is outdated and recent developments, such as the POODLE vulnerability, have shown that SSL v3.0 is now completely insecure (especially for web sites using it).

17. Support For Dojo Asynchronous Module Definition (AMD) Format
HATS projects are now Dojo AMD compliant.
The Dojo AMD style is new standard for writing and loading modules and this dramatically improves code portability and interoperability. It allows modules to be downloaded asynchronously and concurrently, thereby decreasing page load times.
For more information visit

18. Support for the latest Struts Framework
HATS has ability to use Struts to build web pages based on Integration Objects.
WebFacing Web projects now use Struts
Note: The Struts 1.3 runtime has been removed from V9.5 IBM IDEs
Existing HATS Struts 1.3 pages will still function as-is.
Going forward you should create new pages using Struts 2.3.x.
Migration of Struts1.3 source to Struts 2.3.x in the future is recommended.

19. Add Custom Screen Recognition in HATS GUI
The Custom descriptor allows you to call custom description code.
In previous versions of HATS the only way to add a custom screen recognition class to the list of recognition criteria was to edit the XML source.
In HATS 9.5 a developer will now have the ability to insert a custom screen recognition class directly in the HATS GUI. This applies to both screen customizations and to macros through the VME.

20. Custom Screen Recognition Example
Developers often run into situations where an error can appear in any field on a screen. In this example, fields with errors are shown in red. With a simple custom recognition class we can look at all fields and find the one where the error occurred. Using this information we can store that field position in a global variable and highlight the error in the transformation to better inform the user of the location of that error.

21. Add Condition Descriptor in VME
The Condition descriptor specifies a conditional expression that the macro runtime evaluates during screen recognition, such as $intNumVisits$ == 0.
In previous versions of HATS the only way to add a condition descriptor was by using either the old HOD macro editor or by editing the source of the macro directly..
In HATS 9.5 a developer will now have the ability to insert a condition descriptor directly in a macro by using the VME.

22. Add Trace Action in Visual Macro Editor
The Trace action sends a trace message to a trace destination that you specify.
In previous versions of HATS the only way to add a Trace action to a macro was by using either the old HOD macro editor or by editing the source of the macro directly.
HATS 9.5 now has the ability to add a Trace action directly in the VME.

23. Set Recognition Limit and Pause Time for each Macro Screen in VME
The recognition limit allows you to take some sort of action if the macro runtime processes a particular macro screen too many times.
The pause time can be defined to override, for only that screen, the pausetime attribute defined in the <HAScript> element for the macro.
In previous versions of HATS the only way to set the recognition limit and pause time for an individual macro screen was by using either the old HOD macro editor or by editing the source of the macro directly.
HATS 9.5 now has the ability to set these values directly in the VME.

24. Recognition Limit Example
Developers will sometimes find a need to write a macro that loops through screens until it finds a specific criterion to match to stop the looping process. In most cases this behavior will work correctly; however, there are times where an unexpected situation can occur on a screen and cause the macro to continuously loop and get stuck. This causes an infinite loop and can affect both the host and application server. Setting a recognition limit can prevent this out of control behavior and end the macro gracefully.

25. Add Indicator When uselogic Attribute is Enabled for Screen Recognition
The uselogic attribute of the <description> element allows you to define more complex logical relations among multiple descriptors than are available with the default combining method.
In previous versions of HATS the only way to know this feature was turned on was to view the source and look for the uselogic attribute.
In HATS 9.5 there is now an indicator to alert a developer that this advanced attribute has been enabled.

26. uselogic Attribute Example
Developers will find some situations where they want to reuse a screen customization to handle multiple screens but the criteria defined are slightly different in some ways. The uselogic feature allows a developer to use Boolean logic to handle these more complex scenarios. In this example, a single customization can be made to handle 4 or more valid screens based on a combination of criteria being true or false at one time. Using a combination of logic such as and, or, and not (!), we can build complex expressions to match several different screens.

27. Field Location in Screen Capture
In previous versions of HATS the only way to find the exact location of a field was to use the host terminal and place the cursor at the location to get the row and column values. In HATS 9.5 a developer will now have the ability to get this information directly from a HATS screen capture file.
In this example the selected field location starts at row 6, column 17
and ends at row 6, column 49.

28. Withdrawn Capabilities In This Version
Capability
Rationale
Client Recommendation
Java Visual Editor (JVE) (used to create and edit HATS Rich Client transformations)
The JVE has been removed from V9.5 IBM IDEs.
Use one of the available Open Source Software alternatives.
IBM Portlet API portlets
The IBM Portlet API has been removed from WebSphere Portal V8.5.
Use JSR168/286 standard portlets for HATS projects. Migrate WebFacing portlet projects to HATS.

29. JVE Removal - Client Recommendations for RCP
RCP templates or transformation can be created or edited in previous versions of HATS and deployed in new IDE's.
HATS component code has to be added manually to RCP templates and transformations.
Open source tools, such as WindowBuilder, can be used as an alternative.

30. HATS Examples

31. Basic Transformation with Modern Template
Benefit: Modern look and feel- menus, highlighting, fading, rounded corners
Easily customizable and quick deployment

32. Increase Productivity by Combining Screens
The Screen Combination transformation provides a way to combine multiple host screens of contiguous tabular data into one web page.

33. Create Cleaner and More User Friendly Layouts
Turn cluttered host screens into a clean, readable layout.
Text replacement can turn cryptic codes into clear, understandable information.

34. Display Data By Integrating Modern Web Features
Turn a customer address on a host screen into a dynamic map.

35. HATS 9.5 Demo

36. HATS Summary Rich Client Browser Portal Mobile Web Services
Integration at the desktop with other Eclipse-based applications
Client side processing
Rich set of user interface widgets
Supports Lotus Expeditor deployment
Zero footprint
Pure HTML
Access through your favorite browser, including Internet Explorer and Firefox.
Extend to new users for drive new revenue or achieve cost reduction with internet self-help
Integration at the glass
Inter-portlet communication
JSR 168 and 286 compliant
Access host applications from mobile devices
Windows Mobile, iPhone, iPod Touch, iPad
Build reusable transactions
Expose host business processes as standard Web Services
Provide controlled access to vital host applications and host data.
Quick ROI : Host applications can be quickly deployed with a new user interface
Low cost : No need to rewrite application
Practical and low risk : Leverage established terminal applications and open, proven platforms and technologies
Increase productivity and reduce training costs and data entry errors
Improving work flow from multiple applications
Provides integration of host business processes and data with other Web, portal, and rich client applications

37. Resources
HATS Product page:
HATS Trial:
HATS Data sheet:
HATS 9.5 documentation:
HATS Hot Spot:
HATS live demos:

38. QUESTIONS?