Re: Recommendations on development language/environment forwebpresentation layer -- WEB400

If you want to stick with RPG IV then Relational Web is the way to gofor an iSeries based app. Simple, scalable and pretty "native" in itsimplement ion (no esoterics). Check out http://www.relational-data.com/

If you want to go with non-RPG tools then it will be a free for all. Wehave Java minded and even .NET minded folks on the list.

Joe Pluta will go for JSP's. I'll vote for FreeMarker/Webwork. You gowith what you know.

Not sure I have ever seen a truly unbiased comparison of all the toolsthat could possibly run on the iSeries.


Pete

Dave Odom wrote:

To me, they are more of an end-user reporting tool, not an application
development tool.   Am I missing something?

Thanks,

Dave

cozzi@xxxxxxxxx 8/3/2005 14:19:52 >>>

Do you have ASC's SEQUEL product? It has web interfaces for input and
output.  Check out www.asc-iseries.com for details.


-Bob Cozzi

www.RPGxTools.com


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On
Behalf Of Dave Odom
Sent: Wednesday, August 03, 2005 4:11 PM

To: web400@xxxxxxxxxxxxSubject: [WEB400] Recommendations on development language/environment

for
webpresentation layer

Fellow iSeries developers,

What are your best recommendations for development language,
environment, tools, etc., to create a web presentation layer and
application layer over iSeries tables that make up an iSeries Data
Warehouse/Data Mart/Operational Data Store.   As an aside, the
database
will be DB2 tables created via DDL and access from the presentation
layer/application layer will be via SQL and stored procedures
fostering

static SQL on the iSeries as much as possible.

Since I'll do a prototype and then the production application, I'd
like
a toolset that allows for easy development of the first and flow into
the second.   I'd like the language/development environment NOT to be
esoteric and out of the skills mainstream.  I'd like the
language/development environment to facilitate ease of development,
maintenance and rapid development.    I'd like the
language/development
environment to have a track record and probability of being around in
the future.

Having said all the "wants", I'll entertain alternative suggestions.

Thanks in advance,

Dave Odom
Arizona