Bin: I don't know of any more information than what's already there on the CAS wiki, but if your list of CAS enabled applications is small, use an in-memory solution. You can configure their registration on both machines and you're really not hurting much by duplicating an ArrayList e.g. with 8-10 applications on both servers.
A database registry would be a little trickier. You'd probably have to customize the CAS code and develop something where the "keys" to your persisted registry were kept in session on both machines. Then if one went out, the other would at least have the keys. I'm not sure if CAS can do this and someone else may inteject here. I would use in-memory storage if I could. Also, remember that the data is not dynamic. You, the server administrator know what apps are CASified. This fixed number and their URL's can be held in memory very easily if you're not storing too many. And, if you're clustering, I don't suppose the initial cluster was created for CAS. So, that would mean that if you have the hardware, you probably have the memory as well. HTH David On 10/10/08, Bin Rong <[EMAIL PROTECTED]> wrote: > Hi all, > > I am a newbie to CAS, and in our production environment, we have two apahche > servers running behind a hardware load balancer, using ajp to balance > out to several tomcat instances. Sticky session is used, and only one of the > backend tomcat is used for CAS. > > Now we want to load balance/failover CAS, the options are: > > 1. Clustering CAS > 2. Have database-backed registry, so that multiple CAS can validate the > ticket vended by other CAS servers. > > Just wondering what is the best practise? > > We think the database-backed is a good one, and I've searched the web, there > is very little information in this regard, except > http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS. > Could anyone point to any source of information or any detailed howto guide? > > Any advise is appreciated. > > Bin > > _______________________________________________ > 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
