This might not be the solution you're looking for, but you could use ant and
specifiy your different deployments as different targets. This would at
least give you a central place to build from, and because ant knows about
.war packaging and supports FTP, theoretically (because I have not done this
myself) you can do all you're looking for with build scripts.
----- Original Message -----
From: "Attila Bodis" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Thursday, May 17, 2001 10:57 AM
Subject: Deployment to multiple instances...?
> Hi,
>
> This is a newbie question, I guess... Here is the situation:
>
> I have a web application (a bunch of servlets, JSPs, and supporting
classes)
> I want to deploy to multiple Orion instances. Some of these instances are
> for QA, some are inside the firewall, and some are outside the firewall.
My
> application has external dependencies on databases and files in the
> filesystem that are not part of the application itself. Rather than
> hard-code these values, I include them as <context-param>s in
> WEB-INF/web.xml.
>
> Ideally, I'd like to be able to build my web application on my development
> machine, package it as a WAR file, and deploy it by just FTPing the WAR
into
> the appropriate directory on my various Orion instances. The problem is,
my
> configuration parameters are in WEB-INF/web.xml, which is inside the WAR
> file. These configuration parameters have to be different for my
different
> instances (e.g. different directory structure, different database
connection
> parameters, etc.). But the web.xml file inside the WAR file always
> overwrites the one already deployed, which means each time I distribute my
> WAR file to my different instances, I have to 1) wait for Orion to
> auto-unpack the archive, then 2) manually change the settings in
> WEB-INF/web.xml on each instance.
>
> Of course if I avoid putting container-specific (i.e. deployment
> environment-specific) parameters in WEB-INF/web.xml, then the same web.xml
> will work on all of my various instances. But then where do I put config
> parameters such as "log level," "log file directory," and "path to
> my-secret-files", etc., which are used by the application but are specific
> to the particular deployment environment?
>
> Does Orion provide a way to specify config parameters for an application
on
> a per-container basis?
>
> Thanks,
>
> Attila
>
