|
midrange.com
I just got out of Phil Coulthard's RPG to J2EE roadmap session here at the
Websphere Technical Exchange, and he advocates much the same thing (just
using all IBM stuff).
Mike E.
"Joe Pluta"
<joepluta@xxxxxxxxxx To: "Java Programming on and
around the iSeries / AS400"
ers.com> <java400-l@xxxxxxxxxxxx>
Sent by: cc:
java400-l-bounces@xx Subject: RE: RPG to Java
Conversion
drange.com
07/22/2003 05:25 PM
Please respond to
Java Programming on
and around the
iSeries / AS400
> From: Ken Kennedy
>
> My company is going through a transition. Myself and a few others have
> shown them (upper management) what Java is capable of doing, and they
> like it. We are an ISV, and all of our source is CL or RPG. We are not
> looking to move away from the iSeries platform, and we are not looking
> to replace major business logic already mature and working. We are
> wanting to replace the presentation layer with Java/HTML. We have about
> 35 RPG developers, and 4 Java developers.
>
> My boss wants to review several plans on how we are going to transition
> RPG developers to Java. Again, we are not wanting to transition all 35
> to Java. Do any of you know of any literature (white papers, documents,
> web sites, etc...) available that outlines this type of transition? Any
> success stories? Any literature would be appreciated.
Since I sell a product that does exactly this (replace the user interface
of
legacy systems with Java/JSP), I am intrigued as to how you plan to
implement your design. My book on the subject, E-Deployment: The Fastest
Path to the Web, is still available, and gives an excellent review of the
steps required to peel off the 5250 interface and replace it with
JavaServer
Pages. I cal this the server/client architecture, as opposed to
client/server.
If that's indeed what you are trying to do, then you don't need a lot of
Java folks. Java development is really broken down into two levels: class
creators and class consumers. Class creators are the folks who write the
hard bits, the plumbing, if you will. The class consumers then simply call
APIs.
In your environment, you'd need someone to write the interface between the
RPG and the web server, and then you'd need some JSP experts to help you
design the user interface. In the perfect world, your RPG programmers
would
never need to know anything about Java, at least in the beginning, because
they would continue to maintain your applications using traditional green
screen techniques. A second step would then modify these programs to use
APIs to talk to the web server.
Eventually, you would encapsulate your business logic in true servers that
could be invoked directly by servlets in a client/server architecture (at
which point you would then have a staff consisting of servlet designers who
know Java and business logic designers who know RPG, along with JSP
designers who do the UI portion), but in the meantime the server/client
model would get you to market almost immediately.
Joe
_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
