Andrew, If you have machine specific information that needs to be in the XML configuration files, you can always reference those via JNDI in the configuration files and then create a specific context xml file for each machine. The same CAS war file then can be used on each machine, and the machine specific entries are in the application server's context xml file.
We do that with our database connections and stuff on our different tiers. -Scott On 10/26/07, Andrew R Feller <[EMAIL PROTECTED]> wrote: > > In lieu of the CAS server 3.1.1 upgrade, what CAS management practices > does everyone use for CAS fix releases? > > > > In order to make it easier to deploy a new CAS server, I took the original > CAS 3.1 server source code and modified the configuration files as needed > without machine-specific information (cas-servlet, applicationContext, > login-webflow, etc). Once done, I packaged it into a WAR file and deploy it > to the intended server. After I unpack the WAR file, I configure the > machine specific settings such as JBoss replication information. > > > > Does this model make sense? Are there any recommendations for managing > CAS deployments? > > > > Thanks, > > > > Andrew R Feller, Analyst > > Subversion Administrator > > University Information Systems > > Louisiana State University > > [EMAIL PROTECTED] > > (office) 225.578.3737 > > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
