× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks to all,
   
  They and we are on track.
  Our first Webfacing Application is already running under TomCat.
  Yes... Far better performance....
   
  Kind regards,
  Eduard Sluis. 

Bill Reed <breed@xxxxxxxxxxxxxxxxxxxx> wrote:
  To run Webfacing you need either (a) WAS on the iSeries, (b) Tomcat on
the iSeries, or (c) Tomcat on another box (ie, standard pc server).

We found that although our iSeries has wonderful performance for
everything else, it was very slow for the few Webfacing users we had.
Apparently our box teetered near the minimum memory requirement. So we
set up Tomcat on an old PC off the shelf, changed the address in the
users' links, moved Webfacing's output ".war" file (unmodified) to it,
and wonderful performance resulted.

A helpful resource (provided by an IBM friend) was Craig Pelkie's
article: 
http://www.the400group.com/aej/july04.jsp
(I don't remember if this is a site you need to subscribe to.)

Bill Reed
Rock of Ages Corp.



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Eduard Sluis
Sent: Friday, March 10, 2006 11:30 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] WAS necessary for running WebFacing?

Dear All,

On of our clients is reluctant to start using WAS just to be able to
run WebFacing.
They have heard it is also possible to use TomCat for this.
Is this correct and where to get info?

Kind regards,
Eduard Sluis.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.