Re: How are you modernising your as400 applications?

Initially we are taking the approach to reuse as much of our RPG code
and knowledge as we can and are using a third-party tool to quickly
generate applications that fall into the 'CRUD' (CReate/Update/Display)
file maintenance category and the 'show me a list of....' category. When
the existing RPG logic is extensive or the application calls for full
control of whats going on when we are using RPG CGI. For new
applications we have used a JSP frontend calling stored procedures
written in RPG. At the same time we are also starting to learn Java, and
Websphere but there is a big learning curve for traditional RPG
developers and are taking it a step at a time until we are sure we know
this new world and have the tools to manage this new environment like we
have in the traditional world.  The application generator tool we select
is currently turning out RPG CGI code but can be changed to generate
Java code when we are ready to make that switch and when the iSeries
runs Java code as effeciently as it runs RPG which I believe is not too
far away. 
 
p.s. and throw in looking at how best to make iSeries apps work in a
portal and making iSeries data availble to other web development
platforms (e.g. FrontPage, Dreamweaver) (aka web services, or stored
procedures)

>>> colinwilliams007@xxxxxxxxx 2/27/2006 3:27:12 AM >>>

Following from the long discussion re PHP/SQL/App Modernisation,

I would be interested to find out how most of us are going about the
Iseries
Application Modernisation process.

I have always been a fan of the route where you keep your existing RPG
business logic, wrap it up in APIs that you can call as a stored
procedure
via the database, and create a nice browser from end, using Java or
whatever
else you prefer, but also use some direct access from front end to DB
via
SQL. That way you dont have to use the big-bang approach, but can
modernise
as and when.

Just interested to find out what others have done or prefer, have no
personal axe to grind