Use the CommunitiesRemoteAppService.generateSyncReports command to generate HTML reports that help to identify data inconsistencies between communities and their remote applications.
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 a community's privacy level 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 data's widget.
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
Comparing remote application data with the Communities database
Assigning orphaned remote applications to a community
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
is the WebSphere
Application Server installation directory and <dm_profile_root>
is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly. For more information, see Starting the wsadmin client
- Start the Communities Jython script interpreter using the following command:
If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
- 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 need to 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 above, the two output files, 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 six times, once for each remote application (Activities, Blogs, Files, Forums, Ideation Blogs, and Wikis) that is integrated with Communities.