+

Search Tips   |   Advanced Search

Generating a synchronization report


Overview

To generate reports that identify data inconsistencies between communities and remote applications, run...

The command generates two HTML reports...

The Wikis_communityDifferences.html reports might indicate there are differences for community moderation fields. In Connections 4.0, these differences have no impact on the operation of Wikis and do not require immediate attention. Recommended, however, these differences are addressed since they might be meaningful in a future release.


Generate a synchronization report

  1. Export synchronized resource information using exportSyncedResource.

  2. Generate the report:

      CommunitiesRemoteAppService.generateSyncReports(String syncedResourceInfoFilepath, String /path/to/rpt/output/dir)

    syncedResourceInfoFilepath is path and file name of the output XML file generated using exportSyncedResource in the first step.

    For example:

      CommunitiesRemoteAppService.generateSyncReports("/tmp/activitiesOutput.xml", "/tmp")

    In this example, the two output files...

    • Activities_communityDifferences.html
    • Activities_orphanedRemoteApplications.html

    ...are created under /tmp

  3. Repeat step 3 for each remote application to restore data.

    Potentially, we might need to run the command seven times, once for each remote application (Activities, Blogs, Files, Forums, Ideation Blogs, Status Updates, and Wikis) integrated with Communities.

  4. Check the application_orphanedRemoteApplications.html files. To keep the data identified in those files, follow the steps in the topic Assigning orphaned data to a new community. To delete the data, follow the steps in the topic Delete orphaned data.

  5. Check the application_communityDifferences.html files. Contact the community owners for all the communities listed in the file. To ensure the applications are synchronized, community owners can toggle the community privacy settings after any required data scrubbing is completed. Community owners can temporarily modify the community settings.

    For example, they can set a community's access to restricted, save it, change the access back to public, and then save it again to alert all remote applications the community's content should be publicly visible.

    For Community Trash, some of the Communities listed in the application_communityDifferences.html file with "visibility" differences could be caused by a Community that is deleted and is now placed in Trash. Communities in the Trash are changed to have "private" as the visibility type. If so, synchronize the Community and the external widget by restoring the Community from the Trash temporarily. This action restores the Community's original visibility. We can then delete the Community again. Both Communities and the external widget now have the same visibility and both are now in Trash.


Parent topic:
Recover from a database failure