Re: WebSphere express minimum requirements

> Those who are using much less than 300 CPW,
> can you share your experience?

I ran (if that's the word you can use to describe it) WAS 3.5.4 on a
similar machine.  I had to bump every timeout everywhere to extreme
values in order for it to start at all.  When it ran, it was painfully
slow.  I know you are talking about a newer, Express version, and
perhaps that will help.  My end-user response times on an unloaded
iSeries were something on the order of 30 seconds for a simple .jsp
page and just under a minute for a simple (no database access)
servlet.  It was not stable at all.  If the iSeries gets a workload
going, the internal WAS timeouts begin to cascade and the whole thing
came down.  Sometimes it would freeze, sometimes it would take up 100%
of the CPU, (speculating) doing some error recovery loop.  Sometimes
it would be nice to me and issue a message, but generally it was some
gibberish in the logs that only the WAS developers understood.  At the
end of the day, IBM basically said that they weren't going to support
such a configuration, because it didn't meet their minimum
requirements.  I have to say that I can't really blame them, but it's
a pity that a 30 CPW machine can handle a complex ERP with a hundred
users in the subsecond response time realm, but not be able to run WAS
worth spit.

I hope this experience is of some help.
  --buck