I'm going through our CAS configuration in preparation of updating 3.5 and trying to simplify everything as much as possible as I go. I'm currently using JpaServiceRegistryDaoImpl and running MySQL on each of our two CAS servers with a cronjob that dumps the configuration and copies it to our DR site when it changes. Is all that extra infrastructure really necessary? Since the ServiceRegistry database is only used every couple of minutes, it seems like a waste of resources to have MySQL and all of the replication overhead running all the time. If the serviceregistry configuration was stored in a flat file, I could replicate to all the CAS servers and the DR site with a simple shell script and rsync. As a bonus, I could also keep the configuration in SVN to track changes. I tried using InMemoryServiceRegistryDaoImpl and including the configuration for serviceRegistryDao in an external XML file. Unfortunately, the in-memory implementation only reads the configuration on startup, so any changes to the config file while CAS is running are ignored. Before I go down the path of making a custom ServiceRegistry that does what I want, is this a good idea? Can anyone think of issues with using a file-based setup instead of a RDBMS? The only downside I can think of is that the service management GUI would have to be read-only because any changes would be overwritten by the next file reload.
THanks, -Eric -- Eric Pierce Identity Management Architect Information Technology University of South Florida (813) 974-8868 -- [email protected] -- 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
