Morning Harry, Yes, I have kept up with the changes that I have made in a Subversion project. I took the CAS 3.1 source code and put it into trunk, where I do the necessary modifications. Once I reached key milestones (initial configuration, replication configuration, customization/branding, etc), I tagged trunk.
The technical services guys, who are using VMWare for server infrastructure, created a machine, which I configured with Tomcat, Java, CAS, etc without any machine-specific configurations and reverted it into a template. So whenever we need a new CAS server, we simply create it from the VMWare template and configure it for development/test or production usage. As for the CAS 3.1.1 release, I should be able to do diffs on the directories and see what files have changed, but that will definitely be tedious as I have to go through each file's diff to see what has changed to make sure my changes won't be lost. As for the major changes I have made in our CAS deployment template, there have been changes in cas-servlet, applicationContext, deployerConfigContext, login-webflow, added a new themes and views, created our JBoss replication configuration file, etc. Also, I have written some custom code to pass user's credentials to Lotus Domino servers for Domino SSO as our legacy applications are Lotus Notes. Thanks for the reply; I would enjoy figuring out if something better can be done! Andy -----Original Message----- From: [EMAIL PROTECTED] on behalf of Harry Ng Sent: Sat 10/27/2007 11:57 AM To: [email protected] Subject: Re: CAS management practices Hi Andrew, I agree with what you did. And do you keep track of the modifications made? I will keep a branch in my subversion repository which are snapshots of released versions, and put the local changes on the trunk. Whenever there is a new release, I will commit to a branch, then merge the updates to my trunk to produce a "localized upgrade". What do you think about this approach? Regards, Harry Andrew R Feller 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 > > -- View this message in context: http://www.nabble.com/CAS-management-practices-tf4698996.html#a13445138 Sent from the CAS Users mailing list archive at Nabble.com. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
