Cluster restart
To synchronize the various WebSEAL servers, first select a master server. For example, default-webseald-master.ibm.com houses the generic configuration. Any configuration changes that we want made available to all servers must first be manually changed for the master server that includes the configuration files and junction definitions. We must only modify the configuration information on the master. If we modify the configuration on a slave, you risk losing information during the next restart of the server when the slave synchronizes its configuration information with the master.
When we configure a WebSEAL cluster in the environment, we can issue a cluster restart server task command from the master server to apply any configuration changes and restart the updated servers. We can use the -ripple option to specify whether to restart the clustered WebSEAL servers in parallel or in sequence. There is also a -status option that used to monitor the progress of a cluster restart. See server task cluster restart.
Steps
- Run the cluster restart server task command on the master server to initiate the restart.
- The master issues a server restart command on each of the slaves in the cluster. This is either done in parallel or in sequence depending on whether the -ripple option was used in the cluster restart command.
- The slave retrieves the timestamp that indicates when the master configuration information was last modified.
- If the configuration data stored locally on the slave is not up to date, then the slave synchronizes with the master configuration data.
- If the slave configuration data was updated in step 4, then the slave server restarts. If the local configuration database on the slave did not need updating, then the slave does not restart.
- The slave notifies the master that its operation is complete.
- Once all slaves are updated and restarted where required, the master server restarts.
Parent topic: Automating synchronization