tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madere, Colin" <>
Subject RE: Simplified Install of Apache w/ Tomcat
Date Thu, 11 Sep 2003 22:31:38 GMT
well, 2. should be "tar" and you should make sure it is GNU Tar.  Windows
you unzip it with your fav util and it should work :)

-----Original Message-----
From: Filip Hanik [] 
Sent: Thursday, September 11, 2003 6:08 PM
To: Tomcat Users List;
Subject: Re: Simplified Install of Apache w/ Tomcat

installing tomcat is quite easy.

1. Download the ZIP from the website
2. jar xvf

bada bim bada bom

It is installed. For apache, goto  the apache httpd docs


----- Original Message -----
From: "Nikolaos Giannopoulos" <>
To: "Tomcat Users List" <>
Sent: Thursday, September 11, 2003 3:13 PM
Subject: Simplified Install of Apache w/ Tomcat

We have a product that utilizes servlets that we will be making available
for download.

The problem is that we can't expect that our target customers will have
Apache + Tomcat or Tomcat (standalone) installed.

What we want to do however is to provide a set of simplified (if possible
minimal) instructions for installing Apache + Tomcat (ideally we would want
to automate this through a script if possible).  Is there a simplified
procedure for installing these two components - by simplified I mean that
building from source is probably not going to go over well with the Windows
oriented target customers unless we automate the process.

Our target platforms are Windows NT/2000/XP, RedHat 6/7, and Solaris 7/8/9.

Our (specific) product installation is quite trivial - we just want to make
sure that a burdensome installation of the web server / servlet engine
doesn't turn customers away before they even get to our product install.

Any ideas? Suggestions?

We would suggest a stand alone install of Tomcat 4.X except that (a) there
seems to be no way to have it run on port 80 as nobody (without front ending
Apache) and (b) our product tries to minimize the work done in servlets and
is designed to leverage the web server to serve the appropriate content
(whose URL it returns) - unless Tomcat 4.X becomes more solid as a stand
alone web server we have to offer this option.

Will Tomcat 5.X will make these stand aline issues moot?



To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message