RE: Switching to Java on OS/400 - got a few questions.

> From: StokesP@xxxxxxxxxxxxxxxx
> 
> 
> You wouldn't in most cases. The point was really around why porting an
> intensive J2EE app to AS400 app server architectures (WebSphere for
one),
> that'll cost a fortune and still potentially have issues, compared to
> running the identical app on Linux, Solaris or even Windows app
servers at
> a fraction of the cost and full performance and reliability.

There are a LOT of assumptions there.  First, what is "an intensive J2EE
app"?  My guess is a Struts/EJB/CMP environment.  The worst possible
architecture for an iSeries, but great for a dedicated CPU.

And there's simply no way you get the same reliability on a Windows
machine (or a Linux machine, or even a Solaris machine).  


> > What were the processor speeds on the two boxes?
> > How much RAM?
> 
> 7495 x 8 / 48G
> 7495 x 4 / 48G

Model 7495 only goes to a 4-way.  Did you happen to check the CPU
speeds?  The clocks on iSeries boxes, are quite low.  The 7495 is a
1.65GHz box.  The 7495 is also an enterprise enabled machine with full
interactive capabilities.  The corresponding batch machine is only
$100,000.  Exactly what is the alternate configuration you're running
which matches the iSeries in performance for a fraction of the cost?


> > Was the iSeries dedicated to web serving, or was it doing
> > other things?
> 
> Tried in both scenarios, it came down to the IBM implementation of
java on
> the AS400 that caused issues, WebSphere app server's performance under
> load
> of running a J2EE compliant WAR basically fell to bits. No success
either
> with the IBM chaps.

Interesting.  I guess it depends on your definition of a J2EE compliant
WAR.  I have many clients running powerful J2EE applications quite
nicely on much smaller boxes.  Subsecond response time.  Complex
database interactions.  Maybe it's your application, not the box?


> Because of issues we saw, I can only advise on making sure it's what
you
> need and works, we've had a 1 year long priority 1 call that still
> couldn't
> be fixed with the recommendation to stay on alternative platforms.
Details
> of which IBM are aware of but you'll only find out if you come across
it
> yourself - I can't advise on any specifics, Sorry.

I see.  How about an APAR number?  Typically when a problem is reported
to IBM, there's an APAR number associated with it.

In any case, I'll send your name and company to somebody in the iSeries
group and try to find out who is recommending a non-iSeries solution and
why. 

Joe