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
