We currently have WAS 1.2 and 3.5 in production on OS/390 and are in
progress of installing WAS 4 on the system programmer test LPAR. WAS 4
"alternate configuration" is the same as 3.5, which is to say a relatively
modest footprint but no J2EE. Full-blown WAS 4 J2EE environment seems like
it's going to be quite a pig. (200 MB of modules to go into LPA!?!)
We installed WAS on Linux on 390 during our trial, but never really did
anything interesting with it. It seemed to be a bit difficult to
understand and a bit of a pig as well (needed at least a 128MB machine
before it would even become minimally responsive). JBoss wasn't much
different though.
Our largest OS/390 WAS application actually still runs under 1.2 and seems
to perform pretty well. But of course it all depends on the
application--you can write big ugly servlets that take forever or you can
write small fast ones.
Remember that the OS/390 WAS code base is different than the other platform
and has tight ties to OS/390 services such as WLM and RRS.
That probably doesn't help much, but it's something.
Scott Chapman
"Steven A. Adams"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.com> cc:
Sent by: Linux on Subject: Honest Perspective
390 Port
<[EMAIL PROTECTED]
IST.EDU>
03/05/03 11:02 PM
Please respond to
Linux on 390 Port
Hey All,
Here's the request: I'd really like to get some performance perspective
from those individuals that have used WAS under linux, AIX and or MVS.
We are getting ready to use WAS and would like to get a view on which
platform should yield the best performance from those that have used it.
Any input would be appreciated.
Steve
