Positioning For the Future with Alternative Development Tools

1
iSeries
Legacy Application Modernization

• Positioning For the Future with Alternative
  Development Tools!

Tim Archer, Symatrix Technology Tim.archerr_at_sirius
com.com [phone]
2
Agenda,

• Sirius Introduction
• History in iSeries Application Development
• Todays and Tomorrows Application Needs
• Defining iSeries Application Modernization
• Modernizing Justification and Considerations
• Tools for Retooling Legacy Applications
• Getting Starting and Defining Requirements
• Break
• Advanced Business Links Strategi Product
  Overview
• Questions and Wrap up

3
About Sirius www.siriuscom.com

• Founded February 1980.
• Dedicated to the sale and integration of IBM
  product.
• 350 Employees and headquartered in San Antonio
  TX.
• 28 Sales and Regional Offices throughout the US.
• Products Include,
• pSeries, xSeries, iSeries
• Software (Notes, WebSphere, PowerTech, DB2, ABL)
• Storage (SAN, NAS, ESS/FastT, Tape)
• High Availability products (HACMP, Vision, TSM,
  Veritas)
• IBM Support Services Maintenance SupportLine.
• Key Partnerships Include,
• Siebel, Lawson, JD Edwards, Lakeview

4
About Sirius www.siriuscom.com
Consulting Services, Project Management
Requirements Gathering e-Business WebSphere,
Notes/Domino, ABL - Strategi Infrastructure
Services iSeries, pSeries, xSeries, SAN/NAS
Network Architecture. Business continuance
Tivoli, Veritas, HACMP, Vision. Application
Development Lotus Notes, Websphere, iSeries
RPG, Cobol, Microsoft Visual Basic, MS
Office. Education Training Lotus, iSeries,
Custom.
5
iSeries History in Application Development
6
Application Development

• iSeries (AS/400), History of Application
  Development.
• 1980s
• RPG II, RPG III Hosted Applications.
• COBOL Hosted Applications.
• Text User Interface, Green Screen.
• Non Programmable Terminals, NPTs.
• Personal Computers with 5250 Text Emulation.
• Simple File Transfer to and from PCs.

Twinax Connections
7
Application Development

• iSeries (AS/400), History of Application
  Development.
• 1990s
• RPGIV, RPGLE/COBOL Hosted Applications.
• Development with Case Tools.
• MS Windows, GUI PCs.
• LAN/WAN Environments.
• File Transfer Integration with Desktop Products.

Ethernet/Token Ring
TCP/IP
8
Application Development

• iSeries (AS/400), History of Application
  Development.
• 1990s
• Client/Server Application Modeling.
• ODBC, RDO, ADO.
• Internet eMail.
• Web Access, Browser Based 5250 Emulation.

Ethernet/Token Ring
Email and 5250 Emulation
WWW
TCP/IP
9
Application Development

• iSeries (AS/400), History of Application
  Development.
• Late 1990s
• RPGIV, RPGLE/COBOL Hosted Applications.
• Common Gateway Interface, (CGI) to an HTML User
  Interface (UI).
• Java as an Enterprise Development Language.
• Trends Towards GUI, Web and Browser Based UI.

WWW
10
Application Development

• iSeries (AS/400), History of Application
  Development.
• 2000 up to Today
• AS/400 Renamed to iSeries, 2 CPW Performance
  Ratings, Interactive Batch
• IBM Repackages Development Tools, ADTS to WDT
• High Speed Internet Access Frame, DSL, Cable, T1
• iSeries Migration/Modernization Tools.

11
Today's and Tomorrow's Applications!
12
Tomorrow's Applications?

• Graphical User Interface, GUI,
• Browser Based Client,
• Cross-Platform Supported,
• Users More Accustomed to the Windows Environment.

13
Tomorrow's Applications?
Intelligent Databases, Access to Applications
Data from Anywhere, Wireless Access, (Cell
Phones, PDAs), Advanced Reporting/Printing, Distri
buted Content.
14
Defining iSeries Application Modernization
15
Todays Legacy Applications
16
After Modernizing?
17
Defining iSeries Application Modernization,
30,000 Feet!
eBusiness Enabled, Adapting New Business
Models, Market Positioning, Application
Partitioning Modularization, Re-Designed User
Interface, Ability to Adapt to New
Technologies, Skills to Develop and Support the
Application, Advanced Reporting
Tools, Cross-Platform Supported, On-Going
Continued Process!
18
Defining iSeries Application Modernization!
GUI User Interface, Event Driven, Browser Based
Client, Code Conversion to ILE Environment. Partit
ioned, (UI Input/Output Business Logic
Database), Database Triggers, Constraints and
Stored Procedures, Utilizes Todays Modern
Development Tools, Advanced Reporting Graphics,
PDFs, HTML, email, Adaptable to Multiple User
Interface Technologies!
19
Justification and Considerations?
20
Modernizing Considerations?

• Leveraging Maintaining Traditional iSeries
  Skill Sets,
• Retention of Current iSeries Staff,
• Protecting Current Application Investment,
• Minimizing Business Impact with Change,
• Positioning to Leverage Future Application
  Technologies and Skills,
• Minimize Technical Re-Training,
• Minimize Required Maintenance,
• Minimize Financial Investment,
• Invest Over Time to Modernize Applications.

21
Modernizing Justification?
Management Directive, eBusiness
Enabled, IT-Initiated Plan to use New Development
Tools such as Java, Reduction of Maintenance
Overhead through Application Partitioning and
Modularization, Adaptable to New
Technologies, Achieve Platform Independence, Deliv
ering a New Class of Applications, (Workflow,
Business Intelligence, Groupware), Staff
Retention and Ability to Hire.
22
Modernizing Options?

• Rewrite Applications from Scratch?
• Cost to Rewrite Applications?
• Time to Rewrite, Test, Implement?
• New Hardware Requirements?

23
Modernizing Options?

• Replace with Commercial Software Product?
• Package Fit to Current Business Needs?
• Modify/Customize For Fit?
• Annual Fees and Dependency on Software Vendor?
• Re-Training of User Staff and Impact to Business?
• New Hardware Requirements?
• Migration/Conversion of Current Data?

24
Modernizing Options?

• Retool/Migrate Existing Applications?
• Cost to Retool Applications?
• Time to Retool Applications?
• New Hardware Requirements?

25
Modernizing Options?

• Do Nothing?
• Risk Finding/Maintaining Technical/Support
  Skills?
• Training of New Users on Legacy Applications?
• Functionality/Productivity Loss?
• Rising Costs to Replace/Retool Applications?
• Risk Competitive Position in Market?

26
Tools for Retooling/Migrating Legacy Applications?
27
Modernizing Techniques
5250 Client Print Emulation, Browser
Based Applet Based Legacy Screen Re-Facing,
Compile Time Facing Run-Time Facing Code
Conversion to RPG/COBOL ILE, Database
Modernization, Trigger Programs Constraints
28
Modernizing Techniques, Continued
Legacy Application Partitioning, Database -
Business Logic - User Interface. Scratch User
Interface Backend Legacy Application. Advanced
Reporting, Imbedded Graphics Electronic
Delivery/Delivery Format Page Segmentation 4th GL
Code Generators/Frameworks, Rapid Development
Wizards Partitioned and Modularized Re-Write From
Scratch, JSPs, EJBs, HTML, Java, C
29
Products to Retool/Migrate Legacy Applications
5250 Emulation/Print Services, IBMs Access for
Web Advanced Business Links 5250 Applet I/Nets
Webulator 5250 Re-Facing, IBMs Websphere,
WebFacing Seagulls Jwalk NetManages
On-Web Advanced Business Links GUI Style Many
More
30
Products to Retool/Migrate Legacy Applications,
Continued
Advanced Printing, IBM Infoprint
Designer/Server Advanced Business Links
PUSH BCDs Catapult Application Partitioning,
IBMs Host Publisher Linoma Softs Envoy
Genesis Legacy Web FreeStyle-400 Advanced
Business Links HSM
31
Products to Retool/Migrate Legacy Applications,
Continued
4th GLs/Frameworks LANSA IBMs Websphere
Commerce Suite IBMs Portal Server New
Development, IBMs Websphere Studio
Developer New OO Development Languages, Java,
C
32
Products to Retool/Migrate Legacy Applications,
Continued
Other, RPG II/III Conversion to RPG
IV/ILE Prodatas CvtRPGIV Wireless, ABLs Pocket
Strategi Others
33
Getting Started and Defining Requirements
34
Review Stages of Modernization
Browser Client, 5250 Emulation and Print
Services, Application UI Re-Facing, Advanced
Reporting, Application Partitioning, Redesigned
User Interface with Legacy Backend Business
Logic. Database Modernization, Migration from
Interactive to Batch, Re-Write Backend Business
Logic.
35
Getting Started
Understand your Future Business Model, Corporate
Objectives? Market Position? Appraise your
Current Application Structure, Database Native
Relational? Existing RPG/CBL Code, ILE Enabled
Structured? Catalog Applications and Viability of
Modernization? Prioritize Applications to
Modernize? Selection of Modernization
Tools, Evaluate Available Tools? Evaluate Skill
Set Requirements? Develop a Proof of
Concept? Select and Purchase Tools?
36
Getting Started Continued
Migration Planning Staff Training, Migration
Methodology Planning, Plan for Sufficient
Resources, Plan for Sufficient Time, Train/Hire
Staff. Stage Modernization, Browser Based 5250
Print Services, Application Re-Facing, Modernize
Reporting Print Delivery, Modernize Database
Triggers Constraints, Application
Partitioning, New Development Frameworks.
37
Take 5,
Continue with,
Modernizing Applications with