There is one more consideration to how the app is set up and that is what the auditors say you have to do. Besides having to set up a separate partition (which started out as a physically separate box), we also had to run level 50 security which was really enjoyable to configure.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjoern Ravn Andersen
Sent: Friday, May 15, 2009 1:36 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] More on iSeries web apps and security
Mike Cunningham skrev:
Is there something I am missing? Are all of you running under the one partition model or have you split the three functions up?
I believe that the primary reason for the "use a separate box for each
function" line of thought which is common for PC-based solutions has a
very pragmatic background.
Windows and Linux did not[1] provide pools for CPU-cycles and memory -
or rather, only one.
Hence it was possible for a single process to grab all available CPU and
memory and bring the box to its knees. In the bad old days it was quite
common to have a run-away process slow the machine so much down that it
took several minutes to get Ctrl-Alt-Del show the task manager.
Fortunately this is much better today with multicore machines :)
My suggestion is to create three subsystems - one for each component -
and give them a reasonable configuration, and then tell him to do
ANYTHING he can to bring the box to its knees. Hopefully you'll just
see the resources used, climb to the max, but not impact the rest of the
machine.
I did some heavy Java benchmarking on our sole AS/400 and nobody came to
complain, as I only used 90% cpu over a couple of hours. I don't think
anybody actually noticed. On a Linuxbox people would have come looking
for me within a few minutes.
[1] They may now, but most likely in server configurations.
midrange.com
