tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: General Architecture Question for multiple websites on a single RedHat server
Date Thu, 05 Jul 2012 01:02:19 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leonard,

On 7/2/12 4:32 PM, Simon, Leonard wrote:
> Our goals are as follows:
> 
> The operating system will be RHEL 6.X.
> 
> We want to run Apache and Tomcat on a single server running five
> websites using different ports for each.
> 
> Our goal is to manage each web server independently, i.e.,
> separate shutdown and startup scripts and hopefully  different log
> files for each web server.
> 
> We noticed the bundled Apache/Tomcat with RedHat might only give us
> a standard install. Is there a way to do an alternate path
> install?
> 
> Thanks and look forward to some ideas on how to accomplish this.

I periodically threaten to post my multi-instance Apache Ant scripts
to the list. I have recently split my build process into multiple
build scripts including a build-tomcat.xml which will manage that kind
of thing for you. It's still not a perfect separation, but it allows
you to do things like define 'projectname.property=value' in
~/.ant.properties, set <project name="name"> in build.xml, then
duplicate the whole thing over and over again.

So, I have, for instance, "myproject1.tomcat-port" and
"myproject1.tomcat-shutdown-port", etc. and then (near) duplicates for
each project. Each developer on a shared dev server gets a batch of
port numbers assigned for their own uses and then sets those up
accordingly. Each webapp can also have a separate projectX.tomcat-home
and projectX.java-home property, so that simply typing 'ant
tomcat-start' in any project's directory will build an appropriate
CATALINA_BASE (ports and all) for that webapp and then launch the
webapp in that instance.

All of this requires a fair amount of infrastructure to set up (build
scripts, environment-specific server.xml, etc. files, etc.) but once
it's done it makes your life sooooo much easier.

I can share what I've got, but it will likely require you to heavily
modify it to work in your environment since it's so deeply integrated
into our complete build process.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/055sACgkQ9CaO5/Lv0PCr/QCbBAC4LQmZxoMzdtarFxBXHbb8
qjEAn3ldY08iFkVxlWrEkTLDgfxA7qql
=ev/P
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message