It depends on your situation. With just a few VirtualHosts it's easier to
have the client domains aliased to your interface.
Here's a nice article that was posted here a couple of months ago.
Matt Raible [EMAIL PROTECTED]
09/25/2002 08:29 PM
Please respond to Tomcat Users List
To: 'Tomcat Users List' [EMAIL PROTECTED]
cc:
Subject:Virtual Hosts: Connecting Apache 2.x to Tomcat 4.x (was
mod_jk, Windows
XP, Tomcat 4.0.5 - issues)
Sweet - I got it all working - now for a new question.
What is the recommended setup for an ISP/ASP with one box? The article
I modified my workers.properties after (http://www.ubeans.com/tomcat/)
seems to be geared for load-balancing rather than an ISP/ASP
situation. So I added the following and it seemed to achieve what I
wanted.
VirtualHost 192.168.0.3:80
ServerName localhost
JkMount /*.jsp tomcat1
JkMount /servlet/* tomcat1
/VirtualHost
# Second Virtual Host. Also accessible via HTTPS
#
VirtualHost 192.168.0.3:80
ServerName fatbastard
JkMount /*.jsp tomcat2
JkMount /servlet/* tomcat2
/VirtualHost
Where requests to http://localhost will go to tomcat 1 and
http://fatbastard will go to tomcat 2. So if I now have to configure
this on one Linux server for approx 5 (initially) different tomcat
instances.
So do you recommend setting up a bunch of customer1.mycompany.com
aliases that go to the same IP, or stuffing a bunch of NIC cards into
the one box?
Thanks for all your help - this stuff is great, and folks on this list
have made it very easy to setup.
Matt
-Original Message-
From: Robert L Sowders [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 6:25 PM
To: Tomcat Users List
Subject: Re: mod_jk, Windows XP, Tomcat 4.0.5 - issues
No, you should stay with 2.0.42. You need the dll from the
Jakarta build
web site, it has been built against 2.0.42. The one you
downloaded has
not been up-graded yet to work with 2.0.42 yet.
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2
/nightly/win32/
rls
Matt Raible [EMAIL PROTECTED]
09/25/2002 05:10 PM
Please respond to Tomcat Users List
To: 'Tomcat Users List' [EMAIL PROTECTED]
cc:
Subject:mod_jk, Windows XP, Tomcat 4.0.5 - issues
I'm trying to use one of the mod_jk.dll downloads at
http://www.acg-gmbh.de/mod_jk/ and having no luck. The errors I'm
getting is:
1. The Apache service named reported the following error:
Apache.exe: module
C:\jakarta-tomcat-connectors-4.0.4-src\jk\native\apache-2.0\mod_jk.c
is not compatible with this version of Apache (found 20020628, need
20020903). .
2. The Apache service named reported the following error:
Please contact the vendor for the correct version. .
I have the following in http.conf
# Using mod_jk.dll to redirect dynamic calls to Tomcat LoadModule
jk_module modules/mod_jk.dll
#
# Configure mod_jk
#
JkWorkersFile conf/workers.properties
JkLogFile logs/mod_jk.log
JkLogLevel info
And I've downloaded http://www.acg-gmbh.de/mod_jk/Release/mod_jk.dll.
My configuration is Windows XP SP1, Apache 2.0.42, Tomcat 4.0.5.
Looks like I need Apache 2.0.40 eh?
Thanks,
Matt
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Web Hosting with Tomcat 4 and Apache
Overview
There are a number of configuration issues and security concerns
which must be addressed when setting up Apache and Tomcat 4 for
virtual hosting of customer sites in a web hosting environment.
The major conerns are:
1. Delegating to untrusted customers maintenance of their applications
without compromising server security.
2. Configuring Apache and Tomcat for virtual hosting.
3. Surviving poorly written web applications installed by
customers. This includes fault tolerance and identifying
which customer's web application is causing problems.
4. Mimimize the amount of hand holding or config changes the
apache and tomcat system administrators have to make.
This is written based on my experiences setting up this type
of hosting environment on Sun Solaris hardware. Some of this
will be specific to Solaris, but in general should work for
almost any flavor of Unix.
Unix accounts and groups
The user tomcat was created for running tomcat, it should
be created similar to the nobody account used for running
Apache. The tomcat user is assigned to the group tomcat.
The tomcat user is a member of group user.
The group tomcat was created as the group the user tomcat
is assigned to.
The group user was created, this is the group customer
ftp accounts are assigned to. The tomcat account is a
member of this group so that both customers and tomcat
can write files
