™ Delayed Synchronizer propagates community membership changes to Lotus Quickr
places if the Lotus Quickr
server is down when changes in community membership are made.
You can edit configuration property settings to control the delayed synchronization task, and use administrative commands to mark the communities containing links to Lotus Quickr
Wikis or Teamspaces for full membership synchronization. Marking a community in this way forces a full membership and visibility (public or private access) synchronization to the Lotus Quickr
Teamspace or Lotus Quickr
Wiki server the next time that the synchronization task runs.
Configuring delayed synchronizationParent topic: IBM Connections Connector for Lotus Quickr
When you install the IBM Lotus Quickr
connector, the delayed synchronization task is automatically configured with default settings. If you want to change those settings to values that better suit your deployment, you need to edit the <QuickrDelayedSync> settings in the communities-quickr-config.xml
Marking a community for synchronization
The IBM Lotus Quickr
Delayed Synchronizer should automatically propagate changes after a Lotus Quickr
server outage; however, in unusual circumstances, such as restoring a Lotus Quickr
place from backup, you might want to force a full synchronization to occur. You can mark an IBM
Connections community that contains links to a Lotus Quickr
Wiki or Teamspace so that the synchronizer performs a full synchronization between the membership of the place and the membership of its associated community when the synchronization task next runs.