We are launching an application that needs to be available to all user at exact xx:00 hours. Business requirement is to not make it accessible even a minute before and all users should be able to access at exact xx:00 hours. The application has replicas on 2 other servers. I am concerned about two points. First is that access updates are normally not visible immediately. Sometimes users face issue and get access only when they restart notes or wait for couple of mins. Will the ACL update at exact time would be helpful ? Second is, replication between servers will also take 1-2 mins. Making ACL changes available at same time on all 3 servers is challenging. Any thoughts ? Any other way to handle this, may be through code ?
Subject: Suggestion
Don’t replicate acls and from 2 pc change the no access to the db to the right access.
Subject: Use clustering and mark the replicas out of service
The easiest way I can think of to do this is to cluster the servers and then programmatically mark the database in/out of service at the necessary times. When marking it out of service, existing connections won’t be dropped, so you’d need to fold in a command to drop the database immediately after marking it out of service.
IBM Documentation http://www-01.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/admn_makingadatabaseunavailableforuseraccess_t.dita