1. © Logicalis Group Roadmaps for System i application modernisation Mandy Shaw, Chief Technology Officer, Logicalis Computing Solutions

2. Agenda What is our objective? What are we modernising? What added value do we want? How does it all work in practice?

3. What is our objective? Lose ‘The Matrix’? Web-enable? Move towards SOA? Re-engineer our development environment for the 21 st century?

4. Losing ‘The Matrix’

5. INTERNET DMZ MZ Firewall Extranet and external Web server Firewall Internal databases and RPG- based applications Web browser – Extranet or external user Internal 5250 application user Web application server (may reside in DMZ though not best practice) Intranet Web server Web browser – Intranet user Connectors INTERNET DMZ MZ Firewall Extranet and external Web server Firewall Internal databases and RPG- based applications Web browser – Extranet or external user Other external data or transaction sources and targets Internal 5250 application user Web application server Intranet Web server Web browser – Intranet user Connectors Application now available externally! Web enablement

6. Delivery and timesheets ESB CRM system ‘Engagement’ business process Event: new engagement Helpdesk Finance Add a support contract Add an accountAdd a project Moving to SOA

7. Green screen 5250 Display file RPG or COBOL program Physical or logical file DB2 Interface Presentation and navigation Transport Application logic Interface to data store Database Web browser WDHT Struts/JSF Entity bean Session bean Connectors JDBC, MQ, etc. Web service Embedded SQL Development environment reengineering

8. What are we modernising? The presentation? The navigation? The logic? The database? The business’ view of the System i platform? Our approach to application development?

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

10. How can we get the most out of our logic? Value it Separate it from presentation Modularise, expose, write for (and reward) reuse, understand how it maps onto the business Take maximum advantage of the System i platform ILE, Java, electronic output, … Even with no source code there is loads we can do: ESB Business process HATS scripted navigation Web service

11. PTSTSOCKET HOST(PACIFIC6) PORT(1352) If successful, a completion message will be returned Connection successfully obtained to PACIFIC6 on port 1352 Otherwise, an appropriate escape message will be returned Host CAT32 name resolved but no connection was possible on port 1352 Multi-language example

12. R BARLOGO2 AFPRSC('WarringtonMap.jpg' *JFIF + 2.0 1.0 (*PATH '/shawm')) CRTPRTF FILE(SHAWM/BARLOGO) DEV(PDF) DEVTYPE(*AFPDS) USRDFNDTA('MAILTAG(mandy.shaw@notability.com)') CRTDEVPRT DEVD(PDF) DEVCLS(*LAN) TYPE(*IPDS) MODEL(0) LANATTACH(*IP) AFP(*YES) PORT(5101) FONT(011) RMTLOCNAME('127.0.0.1') USRDFNOBJ(SHAWM/MANDY *PSFCFG) STRTFMMGR STRPRTWTR PDF CALL BARLOGO CHGPSFCFG PSFCFG(SHAWM/MANDY) PDFGEN(*MAIL) PDFDEVTYPE(*IP40300) PDFPPRDWR1(*A4) PDFPPRDWR2(*A4) Electronic output

13. Taking advantage of DB2 on System i Right up there with the competition Optimise usefulness of data to business processes and reporting Maximise information quality Maximise manageability and monitoring capability Maybe we need a DBA after all … N.B. change control, impact analysis

14. What added value do we want? Reduced cost / risk Standards usage / availability of skilled resources Improved maintainability / support Reusability / use in an SOA environment

15. How does it all work in practice? Build – tooling / change control / application generators Run – infrastructure and middleware Losing ‘The Matrix’: typically WebSphere Application Server Web enablement: typically WebSphere Application Server SOA: typically WebSphere Process Server or WBI Server Express Manage – security / availability / performance, capacity planning, provisioning Cultural impact

16. Tooling WebSphere Development Studio Client Traditional System i programming environments (RSE) ‘GUI-specific’ DDS keywords Java, Web, service-oriented development Database design and documentation Change control: CVS, plugins for traditional System i tools iSeries Navigator SQL command execution Performance advice and monitoring WebFacing, HATS and WDHT

17. Part of WebSphere Development Studio Client No user enablement licence required Eliminates interactive (OLTP) workload for 5250 applications Requires DDS source for screen formats in refaced applications Creates permanent Web artifacts which can be customized further WebFacing up to now

18. No source code required – “on the fly” conversion Programmable screen flow using scripts, variables & macros Sold as HATS for iSeries with a Limited Edition in iSeries Access Requires runtime enablement licences – user or processor Does not eliminate interactive (OLTP) workload for 5250 applications Host Access Transformation Services (HATS) up to now

19. 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 WebSphere Development Studio C/C++COBOLRPGADTS WebSphere Development Studio Client Remote Systems Explorer HATS Tool Kit Web Tools for iSeries Java Tools for iSeries IBM WebFacing Tool iSeries Projects CODE and VisualAge RPG Best of both worlds: WebFacing Deployment Tool with HATS Technology (WDHT) on V5R4