When Communities or another IBM
® Connections application experiences a database failure that involves restoring to a backup without replaying the transaction log to the point of failure, you can follow a number of steps to ensure a consistent data state for communities and their associated remote applications.
The Communities application provides the option of adding extended functionality by adding widgets. Some of the available widgets are internal to the Communities application, for example, the Bookmarks, Members, and Feeds widgets. Other widget types are applications that are external to Communities - these are the Activities, Blog, Files, Forums, Ideation Blog, Media Gallery, and Wiki widgets.
Communities is tightly integrated with the external widget data. However, when you perform backups of your databases, you might back up Communities database data on a different schedule than the other applications' database data. If a disaster occurs, for example, if the Activities database fails and you need to restore from a backup of the Activities database that is two days old, after the Activities database restore, the Communities database is now more up-to-date than the Activities database. Any changes that were made to the Activities widgets in Communities in the past two days are lost and the two database are no longer synchronized.
Use the information in the following topics to help you to restore the Communities and external widget data to a synchronized state following a database disaster.
Parent topic: Administering widgets and remote applications
Backing up and restoring data
1. Restoring communities with remote applications
Ensure data consistency following the recovery of an IBM
Connections application or the Communities database.
2. Comparing remote application data with the Communities database
Use the exportSyncedResourceInfo commands to return a report of all the communities that an application has interacted with. The information in these reports can help you to synchronize remote application data with the Communities database after a system crash that includes data loss.
3. Generating a synchronization report
Use the CommunitiesRemoteAppService.generateSyncReports command to generate HTML reports that help to identify data inconsistencies between communities and their remote applications.
4. Assigning orphaned remote applications to a community
Use the CommunitiesRemoteAppService.assignRemoteApp command to assign remote applications that have been orphaned following a database failure to a new community or reinsert the widget into an existing community.
5. Deleting orphaned data
Delete orphaned data from remote applications following a system crash or database failure.