RE: Using a partition as an APPSERVER with RDB

Yes, we can do all these things using SQL Cursors that's not an issue.  My
only issue is the performance and connection limitations if any.  Using this
design I can move my application on any server.  It is like a MVC approach
but on i5 using SQLRPGLE :-)




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Phil Kestenbaum
Sent: Friday, February 17, 2006 9:15 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Using a partition as an APPSERVER with RDB

Are you converting completely to SQL? How will you be handling the use
of Chains, Reade's etc...

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mohammad Tanveer
Sent: Friday, February 17, 2006 11:01 AM
To: 'Midrange Systems Technical Discussion'
Cc: 'RPG programming on the AS400 / iSeries'
Subject: Using a partition as an APPSERVER with RDB

*         We have 5 partitions on i5. 

*         Each partition has many production environments.  

*         Each environment is using the same application.  

 

Currently we are maintaining the source for each environment separately.
Don't ask why (it's been this way for years).  We don't have any problem
the
only issue we have is that when we have to make a global change (very
often)
we have to retrofit this change in 50 different environments (most of
the
time its frustrating), time consuming and requires a lot of resources.

 

What I am thinking to do is to make one Partition an Application Server
(I
am stealing this term from WEB/Java World), convert the RPGII/RPGIII
application into SQLRPGLE Application (This will help me to avoid any
kind
of level checking in case there is a slight difference in database in
individual partition). 

 

Application will run on this partition, depending upon the USER LOGIN,
application will connect to a particular partition and environment using
CONNECT database (RDB).  Programs will run on this partition and access
the
remote database. I have done the testing and its working fine.

 

What I don't know is the performance issues especially when 100s of
people
will connect to this APP server.  Is there any documentation or design
pattern I must follow so that performance won't become an issue?  Is
there
anyone doing it this way, have they encountered any problem?

 

 

Thanks in advance.