----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
This whole thing escapes me.
I'm a RedHat user. I chose RedHat partially for the ease of having solid
RPMs(yes, they're usually RH-specific, but then again the acronym is for
Redhat Package Management...).
1. Install RH 6.2 and choose Apache as a package
2. Download ApacheJServ-1.1.2-1.i386.rpm from
http://java.apache.org/jserv/dist/ApacheJServ-1.1.2-1.i386.rpm
3. Run rpm -ivh ApacheJServ-1.1.2-1.i386.rpm
4. /etc/rc.d/init.d/httpd restart
You've now got JServ installed and running. This shouldn't have taken you
even 45 minutes.
The configuration files are no different from any other servlet engine, with
the aforementioned exception of the load balacing parameters, which don't
exist in any of the other servlet engines I've used. I have to admit,
though, that the JServ comments in the configuration file are much
friendlier and explanatory than any of the other 7+ servlet engines I've
tried.
Thanks,
John Stotler
Eutectics Corporation
http://www.SocratEase.com
-----Original Message-----
From: Ben Ricker [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 18, 2000 4:15 PM
To: Java Apache Users
Subject: Re: Jserv vs. iPlanet
----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
[EMAIL PROTECTED] wrote:
> [Menchaca, Joaquin] Actually, this has nothing to do with "GUI"
vs
> "CLI" type of arguement. This is just a cost effectiveness issue. The
more
> cumbersome it is to configure something, the more time is invested. Even
> though JSERV is freeware, the time that takes those not familar with the
> system is far greater than packages like JRUN and iPlanet. The the total
> costs of the commercial package + cost of paying an engineer to
> configure/administer the system, makes JSERV more expensive than JRUN or
> iPlanet.
However, it seems unlikely that there would be a $1400 per CPU cost for
configuring Jserv due to manhours. I knew hardly anything about Unix or
Apache or Jserv and it tool me about 25 hours to set it up, mostly due
to trial an error and the hard learned lesson of using the FAQ and this
list. Now, I can setup a full Apache/Jserv setup from source in less
than 2 hours. MOst of that time is getting the servlets in the right
place and form to run. Add to this the $3000 a year for mission critical
support, and this blows your argument out of the water. We have run
Apache/Jserv for 3 months straight with NO downtime whatsoever.
Someone earlier pointed out the Achilles Heel of iPlanet: bad load
balancing. Since it ties the VM to the web server, one cannot load
balance to the JVMs. If the machine goes down with a memory leak or
socket death, there goes the whole kit and caboodle. No web serving, no
Java. Nothing.
Ben Ricker
Web Administrator
US-Rx, Inc.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
