Being able to offer a nice UI, browser access, and Web services access in your IBM i apps is all to the good. However, there are hidden bumps in the road to app modernization.
Written by John Ghrist
"Application modernization" has come to mean many things, from simply improving the execution of RPG code (e.g., by translation of old code to RPG ILE), to adding a graphical UI to legacy apps ("screen-scraping"), to revamping applications to function in a Service-Oriented Architecture (SOA) or Microsoft's .NET environment and adding browser access. Strategies for doing this are driven by many reasons, the most obvious of which are better appeal to users, better functioning of applications for business missions, and opportunities to re-engineer IBM i software to work in multiplatform environments.