EGL My Transition

1
EGLMy Transition

• Jake Berberich
• Principal, Xavier Group
• Roanoke, VA

2
Background

• Started with S/32
• Construction, Medical, Retail, 3PL
• Independent Consultant last 4 years
• Retail, Manufacturing, Government, Distribution
• Like 4GL Languages
• Been searching.

3
Evaluated

• Didnt want the MS route
• Becoming a Java guy
• Generators for RPG/CGI
• PHP on the System i

4
Important from System i Perspective

• Access to legacy data
• Learning Curve
• Leverage existing skill sets
• Reuse tested tried and true code algorithms
• Platform Loyalty

5
Chose EGL

• Stars and Planets Aligned
• Client Needs a Web Solution
• Had to be Custom App
• Virtually Committed to Adopting EGL

6
What I avoided

• Needing to learn Java
• Other syntax intensive language
• HTML coding
• Migrating away from System i

7
Positioned to

• Leverage Existing Technology Investment
• Modernize Incrementally
• Pick Right Tool for Right Opportunity
• Mix Match Hybrid Technology

8
WIIFM

• Avoid a Dinosaurs' Fate
• Stay with the System i
• Deploy UI Experience 2nd to NONE

9
Learning Curve for Legacy Guy

• Eclipse Workbench
• Binding Attributes to variables/functions
• Event Driven Run Time
• Result Sets vs. RPG Full Procedural Files
• Problem Determination
• Interpretation of WAS Server Console
• Run time HTTP errors

10
Rich System i Tool Box

• Call your RPG and CLP routines
• QCMDEXC
• Data Area
• Logon authentication example
• Data Queue access have not used
• Technique for accessing file members

11
Development Attributes

• Content Assist (like F4)
• Annotate errors as you type
• Validate variable definition and end tags
• Quick compile even for complex functions
• Compile/Run Cycle Immediate Gratification

12
Built into the Tooling

• Paging Functions (Antidotal Story)
• Category Groups
• Row Select Tool Bar or Combo Box
• In place edit of row content

13
Modus operandi

• Right time for the right tool
• Combined access of data SQL and RPG
• SQL function to populate sub-file arrays
• MVC
• RPG for record level access CRUD
• Perform heavy data edits or manipulation with RPG

14
What I Like

• Not that one couldnt.
• Rich property attributes allow for run-time
  rendering
• Populating combo boxes from iSeries table values
• Radio buttons, check boxes, etc.

15
Rendering
16
Suggestions Strategic

• Take the on-line class
• Then supplement with self study
• Audit classes when possible
• Attend the periodic Best Practices Presentations
• RSS feed the Café
• RBD and JSF PowerPoint's update always have new
  how-to(s)
• Know your strengths
• Co-opt enabled colleague to do the UI

17
Suggestions Tactical

• Use Tomcat for development
• Build Snippet Compendium
• Content Assist Softens Syntax Minutia
• Modify Page Designer Template where appropriate
• Carry Over Techniques Incremental Testing of
  logic

18
Ever Increasing Resources

• EGL Café
• Examples for virtually every presentation view
  one would find in business
• More frequent articles by industry pundits

19
What the users dont know how to do, becomes
what the product cant do.Courtesy Jon Sayles,
IBM EGL Presentation
20
Closing Thoughts

• Context of Business Application
• Virtually any UI experience
• For me, no gaps in EGL language capability
• EGL Choice no second thoughts

21
Xavier GroupJake Berberich

• Jake.Berberich_at_cox.net