tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alec Swan <>
Subject Re: Virtual host deployment
Date Tue, 14 Sep 2010 21:52:50 GMT
Hi Chris,

Thank you for the defaultHost recommendation.

The deployment scenario I would like to support requires deploying the same
WAR file on the development server first and then on the production server.
Development and production servers use different database credentials, so I
cannot package them in the WAR file itself. So, the database credentials
should be stored somewhere in the server configuration.

What is the recommended way to support  this scenario? Is there any other
place besides conf/context.xml where I can store server-specific DB



On Tue, Sep 14, 2010 at 3:18 PM, Christopher Schultz <> wrote:

> Hash: SHA1
> Alec,
> On 9/14/2010 5:04 PM, Alec Swan wrote:
> > I have a WAR file which I distribute to multiple servers with multiple
> > virtual hosts. On each server I have a database, which is accessed by all
> > virtual host apps on this server.
> I'm interested: is the WAR actually identical, including all settings
> for all virtual hosts? If so, you can save yourself a lot of memory and
> database connections by deploying a single copy to a single <Host> and
> either setting that host as the "defaultHost" for the <Service> or using
> <Aliases> within the <Host>.
> > Is it the right approach to put database access credentials in
> > $TOMCAT/conf/context.xml
> No. You shouldn't really modify conf/context.xml unless you have a
> really really good reason to do so.
> > which will then be loaded by each virtual host app
> > or should I put them somewhere else?
> Put the <Resource> for your database connection pool into your webapp's
> META-INF/context.xml file.
> - -chris
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla -
> iEYEARECAAYFAkyP5psACgkQ9CaO5/Lv0PAjswCeJnaG3E5zW3thH5e+l6e9seES
> b2IAn3qmhJbwiUtPfsX7tIGQiotuvTm/
> =eqpa
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message