Raghuveer wrote:
I need to delpoy on OC4J and runs with LDAP SQL server.
LDAP,LOG 4J,DATABASE datsource configration properties changes based on
environment like TEST,DEVELOPMENT,PRODUCTION


Ant can help with
 -the logistics of copying files from place to place
 -starting and stopping servers

if you have different boxes, the convention is to have property files for each one

so

 ant deploy -Dserver=test

triggers a

<propertyfile file="hosts/secure/${server}.properties" />

that drive the build. You should keep secrets in property files that are not checked in to the SCM repository.

Cargo can start and stop app servers.

If you are trying to configure the app+db+logging dynamically from machine to machine you need to come up with a configuration management solution, such as

1. create different WAR/EAR files for each target, copying in different properties and xml files
     -scales badly and you have a disaster when the wrong jar gets deployed
2. have your app dynamically read in properties files based on its hostname
     -breaks when staging and production have the same name
3. use something like SmartFrog (http://www.smartfrog.org) to do it
-I work on this project, I'm biased. Its very powerful, but does need a big change in how you think
4. use the LDAP server to store the configurations
-This is nice; good central management of settings. But with setting in LDAP, they are not locked down in SCM no more.
       and you have the bootstrap problem: how do you bond to ldap.
5. use the database for all of them
     -simpler than ldap, still has a bootstrap problem.


Steve

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to