About this task
The Lotus Quickr
Delayed Synchronizer reconciles inconsistencies in membership synchronization between a Lotus Quickr
place and its associated community. A community's membership might go out of synchronization from time to time, for example, if the Lotus Quickr
server is down when new members are being added to or deleted from a community. The Delayed Synchronizer looks at all the communities that have been modified in the past 14 days to check if the membership between the communities and the associated Lotus Quickr
places has fallen out of synchronization. The synchronizer then propagates any changes to the Lotus Quickr
place at a later time.
To configure delayed synchronization between Lotus Quickr
places and their associated communities, complete the following steps on the file system of the Deployment Manager:
- Navigate to the following subdirectory to locate the communities-quickr-config.xml file:
- Open the file with a text editor and navigate to the bottom of the file to locate the QuickrDelayedSync settings.
The QuickrDelayedSync task information looks similar to the following:
<comm:startDelay value="60"/> <!-- minutes -->
<comm:taskInterval value="60"/> <!-- minutes -->
- Update the settings as required. The following table displays information regarding the QuickrDelayedSync properties and the type of data that you can enter for them:
Table 1. QuickrDelayedSync properties
|QuickrDelayedSync.enabled||Enables synchronization to occur. This property takes a Boolean value: true or false.|
|QuickrDelayedSync.startDelay||The delay in minutes before the task starts. This property takes an integer value.|
|QuickrDelayedSync.taskInterval||The delay in minutes between consecutive tasks. This property takes an integer value.|
|QuickrDelayedSync.daysBackToScan||Limits the search for community changes. The default value of 14 indicates that only communities that have been modified in the past two weeks will be checked for missed propagations. This property takes an integer value.|
- Save your changes to the communities-quickr-config.xml file.
- To apply your changes, stop and restart the Communities server.
What to do next
When you have multiple WebSphere
® Application Servers running the Communities application, you must ensure that the Lotus Quickr
Delayed Synchronizer is only enabled on one server by doing the following:
Parent topic: Using the Lotus Quickr Delayed Synchronizer
- On the file system of the Deployment Manager, open the communities-quickr-config.xml file in a text editor. Edit the file so that the <comm:serverToRunOn> element contains a string in the following format:
- Save your changes and then apply them by doing the following:
- Select System administration -> Nodes, select all the nodes, and then click Full Resynchronize.
- From the main Integrated Solutions Console page, select Servers -> Clusters.
- Select the check box beside the cluster containing the nodes that have been updated, and then click Stop.
- Select the cluster and click Start.