Hi.
I have seen your HOWTO and have some questions. My situation is a bit more complex.
Let's say I would like to achieve a general situation:
HOST1
--------
Tomcat {
VirtualHost www.vhost1.com {
Context "Addres book" {
deployed under it's own directory
with path "/addr_book"
}
}
}
HOST2
--------
Apache {
VirtualHost www.vhost1.com {
WebAppDeploy {
I would like to deploy that Tomcat's Context here
}
}
}
Well, needless to say, I'm having problems with this setup. Rught now HOST1 = HOST2,
but even situation where it isn't so, breaks. I'm getting warp errors on Tomcat's side
saying that www.vhost1.com name is not unique.
So, my question is: does WARP work with virtual hosts on Tomcat?
All (successful) examples I've seen use <Host name="localhost" ...>. could that be my
problem?
What I would like to achieve are two things:
GOAL 1
---------
I would like to have a *real* virtual hosting server, where I will create a user
account, create dirs inside it:
./bin
./data
./sql
./public_html
./cgi-bin
./webapps
Then create (if needed) PostgreSQL database for that user and virtual hosts both in
Tomcat and Apache, based in "public_html" and "webapps" respectively.
That way, a user will have the whole virtual environment and it will be "packable" -
if I decide to move the user to anotehr server, all I have to do is transfer the
entire home and establish new virtual hosts in DNS, Apache and Tomcat (on the new
server machine).
GOAL 2
---------
Another thing I wanted is to be able to separate DB, Tomcat and Apache. I have several
machines I can populate with these and they are not identical. The way I see it, DB
should be on a machine with good disks and a lot of RAM (I got AlphaServer 4100 :-)),
Tomcat on a fast CPU+mem (any decent Linux, Solaris or an unused Alpha will do) and
Apache should have good disks and network (again any Linux will do).
Can this be done?
Since listening on ports above 1024 doesn't require root priviledges, I could adopt
your solution, but then the owner of virtual host would be responsible for starting up
Tomcat and that is not something that looks good to me. Again, even that can be
automatized.
From your point of view, is it better to run all virtual hosts of Tomcat withing one
JVM (one process, myriads of threads) or to have one JVM per virtual hosts (n
processes, each one with it's complement of threads)?
Nix.
