Before you begin
You need to export synchronized resource information by following the steps in the topic, Comparing remote application data with the Communities database
To use wsadmin commands, you must use the IBM
® Application Server wsadmin client. See Starting the wsadmin client
About this task
The CommunitiesRemoteAppService.generateSyncReports command generates two HTML reports that can help you to identify data inconsistencies between communities and their remote applications, communityDifferences.html
. The communityDifferences.html
report lists the differences in the information recorded in different application databases. For example, the Communities database might record that the privacy level of a community is set to public, but the Blogs application might record the community type as restricted. The orphanedRemoteApplications.html
file lists the remote applications for which there is either no associated community or whose associated community is missing the orphaned datas widget.
reports might indicate that there are differences for community moderation fields. In IBM Connections 4.0, these differences have no impact on the operation of Wikis and do not require immediate attention. It is recommended, however, that these differences are addressed since they might be meaningful in a future release.
To generate a synchronization report, complete the following steps.
Parent topic: Recovering from a database failure
Previous topic: Comparing remote application data with the Communities database
Next topic: Assigning orphaned remote applications to a community
Starting the wsadmin client
Comparing remote application data with the Communities database
Assigning orphaned remote applications to a community
- Verify that you completed Comparing remote application data with the Communities database and then continue to the next step.
- Run the following command to generate the report:
CommunitiesRemoteAppService.generateSyncReports(String syncedResourceInfoFilepath, String outputDirPath)
- syncedResourceInfoFilepath is the full path and file name of the output XML file that was generated using the exportSyncedResource command. (For more information about this command, see Comparing remote application data with the Communities database.) Use forward slashes as the path separator. For example, c:/temp-dir/activitiesOutput.xml on Microsoft® Windows® or /opt/temp-dir/blogsOutput.xml on Linux® or AIX®.
- outputDirPath is the full path to the subdirectory where you want to create the two output files that are generated from this command. You must use forward slashes; not backslashes as the path separator. For example, c:/temp-dir on Microsoft Windows or /opt/temp-dir on Linux or AIX.
Using the sample command previously shown, the two output files, Activities_communityDifferences.html
, are created in the c:/temp-dir
- Repeat step 3 for each remote application where you want to restore data.
Note: Potentially, you might need to run the command seven times, once for each remote application (Activities, Blogs, Files, Forums, Ideation Blogs, Status Updates, and Wikis) that is integrated with Communities.