Setup a shared database server for the ticket/service store and put 2 web servers behind load balancers. Or you can setup cache replication in tomcat instead of shared database. You can also install MySQL on both web servers and setup Master/Master replication if you prefer that route. That's how we do it instead of a single shared database.
Jason ----- Reply message ----- From: "Pratap K M" <[email protected]> Date: Sun, Feb 10, 2013 9:53 am Subject: [cas-user] CAS Server failover? To: <[email protected]> Dear sir, In the Single-sign-on(SSO) framework, CAS Server becomes the critical component. Its failure will result in all applications not accessible. How to overcome this? regards Pratap K M -- 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 -- CONFIDENTIALITY NOTICE: This e-mail together with any attachments is proprietary and confidential; intended for only the recipient(s) named above and may contain information that is privileged. You should not retain, copy or use this e-mail or any attachments for any purpose, or disclose all or any part of the contents to any person. Any views or opinions expressed in this e-mail are those of the author and do not represent those of the Baptist School of Health Professions. If you have received this e-mail in error, or are not the named recipient(s), you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited by the sender and to do so might constitute a violation of the Electronic Communications Privacy Act, 18 U.S.C. section 2510-2521. Please immediately notify the sender and delete this e-mail and any attachments from your computer. -- 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
