I agree with Bill. Unless you have extensive experience with managing databases or you have a need for long-term durable ticket storage (i.e. remember-me support), you're better served with something like Memcache or Ehcache.
On Wed, May 15, 2013 at 2:15 PM, William G. Thompson, Jr. <[email protected]>wrote: > On Wed, May 15, 2013 at 11:24 AM, Rakesh <[email protected]> wrote: > > Hi, > > > > I am new to CAS and I am trying to set up CAS 3.5.2 for HA. I have > CAS deployed on 2 tomcat servers behind a load balancer and Tomcat servers > are not clustered. I have CAS set up to use JPA TicketRegistry. > > Highly recommend you avoid the JPA TicketRegsitry. > see: > http://jasig.275507.n4.nabble.com/JpaTicketRegistry-A-Sinking-Ship-td4256973.html > > > > > > I wanted to know if this is enough for CAS HA? or do I need set up > tomcat session replication for HA? Also can anyone shed some light on this > following configuration in cas-servelet.xml > > Tomcat session replication is not needed if you are using sticky > sessions at the load balancer. > > > > <flow:executor id="flowExecutor" registryref=" flowRegistry" > repository-type="client"> > > What is this configuration used for? Do I need this? > > > http://static.springsource.org/spring-webflow/docs/1.0.5/reference/flow-executor.html > > Best, > Bill > > > > > Thanks, > > Rakesh > > -- > > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
