WebFacing Deployment Tool with HATS Technology

1. WebFacing Deployment Tool with HATS Technology Green screen applications on the web

2. What is WebFacing? Eliminates interactive (OLTP) workload for 5250 applications Requires DDS source for screen formats in refaced applications Creates permanent Web artefacts which can be customized further

3. What is Host Access Transformation Services (HATS)?

4. Host Access Transformation Services (HATS) • What is HATS? • Host Screens are converted to web-like GUIs on the fly, in real time • Preserves existing application flow • Easy web-to-host first step • Eliminates need to customize every screen • Low skills requirement • Rules-based, customizable • "Near" load-n-go implementation • Zero footprint on the desktop • Iterative development

5. Host Access Transformation Services (HATS) • What is HATS? • Wrap existing green screen applications with web features • Branding and re-branding • Links – training guides • Portal integration • Re-arrange application layouts • Function Keys • Primary Input Fields • Confirmation boxes • Enhance ways users work • Skip unnecessary screens • Improve workflow • Reduce training

6. Host Access Transformation Services (HATS) • What is HATS? • When to use HATS • Make an application available to the web • Reuse application or resources with a web look and feel • Where to use HATS • In place of 5250 desktop applications • Integration to new developments • Web Services to J2EE applications • Where to run HATS • WebSphere Application Server • iSeries • Linux • Windows • AIX • Solaris

7. Delivers a runtime enablement that exploits the capabilities of both HATS and WebFacing Allows refacing projects to combine the strengths of both products in a single project using WDSC Provides a system wide solution for multiple applications, with or without source code No interactive (OLTP) workload required for HATS or WebFacing with i5/OS V5R4 Alternative licensing models: User Processor Best of both worlds: WebFacing Deployment Tool with HATS Technology (WDHT) on V5R4 WebSphere Development Studio C/C++ COBOL RPG ADTS WebSphere Development Studio Client Remote Systems Explorer Web Tools for iSeries HATS Tool Kit Java Tools for iSeries IBM WebFacing Tool iSeries Projects CODE and VisualAge RPG

8. How do we want to deliver to the desktop? Add more value through GUI DDS, applets, fat clients

9. Moving to SOA Helpdesk: HATS scripted navigation Delivery and timesheets Finance Add a support contract: web service Add a project Add an account ESB ‘Engagement’ business process Event: new engagement CRM system

10. So how does it work? iSeries running 5250 application WebSphere Application Server WebFacing server WDHT J2EE application (servlets, JSPs and JavaBeans for converted display files, customised 5250 screens, macros and on-the-fly conversion) Display file or system panel Green screen application 5250 data stream Telnet client running inside WAS Telnet server Customisations Developer PC WDSCi with HATS Toolkit loaded HATS can talk to 3270, 5250 and VT applications WAS can be on any platform

11. Host Access Transformation Services /A closer look at HATS

12. Green screen through iSeries Access

13. A simple HATS rendering

14. An automatic but more Windows-like HATS rendering

15. An advanced customisation

16. Implementation Topics • A rules based transformation engine • Customised access to one or more applications • Dynamically creates a new interface for your iSeries • Improves navigation and productivity

17. A rules based transformation engine • Default rules allow applications to be transformed within hours of software being installed • Zero specific requirement for a software developer • Most screens will not need customising • No need to modify RPG and DDS, or worry about recompiling it

18. Customised access to one or more applications • Every application on your iSeries is transformed • Ability to merge data from various sources to one web page • Develop pages at your own pace

19. Dynamically creates a new interface for your iSeries • No applets or downloaded run time • On the fly transformation means green screen updates are automatically picked up and presented • Reduce support and costs: you only need a web browser, portal or mobile device • Integrate to portal for single sign on and ‘click to action’ • Handle and integrate apps on multiple iSeries systems/partitions through a single HATS interface

20. Improves navigation and productivity Helpdesk: HATS scripted navigation Add a support contract: web service • Total layout control • Add new workflow • Remove obsolete fields, with no loss of functionality to existing application • Automate processes for which you have only 5250 application with no source code • Macros • Skip unnecessary screens; combine screens; split screens • Enter data on behalf of the end user • Global Variables • Store end user input for use in other screens • Pass data between screens/programs and to/from external J2EE applications • Extend existing legacy proven code with Java Business Logic • Externalise your applications through web services

21. Host Access Transformation Services /HATS in action

22. Convert your entire system in about 6 minutes • Our movie shows how to use WDSCi to create a project that converts all screens on your iSeries • All screens are now available to a web GUI interface, and enables them to be accessed by a browser from anywhere you permit • As is demonstrated, you can accomplish this task in about 6 minutes

23. Host Access Transformation Services /HATS deployment and licensing

24. Web browser –Extranet or external user Other external data or transaction sources and targets Configuration with WDHT running in WAS on iSeries (also showing access via both external and Intranet web servers). MZ Web browser – Intranet user DMZ iSeries Intranet Web server Extranet and external Web server Web application server INTERNET Firewall Firewall WDHT Green screen applications Pricing either by user or by processor (taking into account iSeries tier). No subcapacity pricing yet, but special bids expected and acceptable, in which case the counted processors are those in the partition that is running the WAS instance into which WDHT is deployed. WDHT can talk to green screen apps on as many iSeries boxes / partitions as you like without further charge. WDHT can use the WAS Express that is bundled with OS/400. Internal 5250 application user

25. Configuration with WDHT running in WAS on Intel (again this could be accessed via both external and Intranet web servers, but only the Intranet one is shown here). Could be Windows or Linux (IBM tests show greater throughput on Linux). MZ Web browser – Intranet user Intel Intranet Web server Web application server WDHT Pricing either by user or by processor. WDHT can talk to green screen apps on as many iSeries boxes / partitions as you like without further charge. WAS Express comes bundled with WDHT, but this bundled WAS licence can be used for WDHT only. Alternatively, deploy into your existing WAS infrastructure on Intel (Express, Base or ND edition of either WAS 5.1 or WAS 6.0). iSeries Green screen applications Internal 5250 application user

26. iSeries pre V5R4 (HATS works with V3R7 onwards, WebFacing works with V5R1 onwards) Clarification of what it is that happens on V5R4 only Converted (WebFaced) display files (only) WebFacing server WebSphere Application Server Display file or system panel Green screen application WDHT 5250 data stream Unconverted display files (HATS) Requires interactive CPW Telnet server iSeries V5R4 Converted (WebFaced) display files, plus see below WebFacing server WebSphere Application Server Display file or system panel Green screen application WDHT 5250 data stream Unconverted display files (HATS) with new connection type No need for interactive CPW Telnet server

27. Why it’s a good idea to think about it before the end of September ‘06

28. Host Access Transformation Services /More information

29. Development and HA environments • You get HATS Toolkit and 2xuser licences for developers bundled with WDSCi • Any additional developers, assuming dev HATS server is on separate box from live one, are best catered for through additional user licences • Don’t forget to allow for high availability in a WebSphere infrastructure for WDHT, especially if you are planning to route all green screen traffic through it to avoid paying for interactive CPW • You don’t have to cluster WAS unless you have other reasons to do so, but you would be wise to provide redundancy, especially if running WAS on Intel • You would only need to license WDHT for the primary deployment, unless: • you intend to use both deployments at once, or • one is on Intel and the other on iSeries, or • DR testing uses more than the 2 WDHT connections provided with WDSC (in which case I would suggest you buy the relevant number of WDHT user licences to cover it)

30. References • Loads of good detail re WDHT here • http://www.iseries400experts.com/aiw/02-2706.jsp • IBM DeveloperWorks description of WDHT • http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=278&thread=108617&cat=9 • Workload Estimator • http://www-912.ibm.com/supporthome.nsf/document/16533356

31. Host Access Transformation Services /Question time…

32. thank you