Compare remote application data with the Communities database

Use 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.

Start the wsadmin client.

Communities can integrate with the Activities, Blogs, Files, Forums, News, and Wikis applications as remote applications. We can run the CommunitiesRemoteAppService commands for each remote application listed in the orphanedRemoteApplications report. Alternatively, we can delete any orphaned data from the remote applications. For more information about deleted orphaned data, see Delete orphaned data.

To resolve inconsistencies between remote applications and communities.

1. Start wsadmin...
   cd app_server_root/profiles/Dmgr01/bin
   ./wsadmin.sh -lang jython

2. Use the wsadmin client to access the configuration files for the remote application to synchronize with Communities.

   • To access the Activities configuration file:
     execfile("activitiesAdmin.py")

   • To access the Blogs configuration file:
     execfile("blogsAdmin.py")

   • To access the Files configuration file:
     execfile("filesAdmin.py")

   • To access the Forums configuration file:
     execfile("forumsAdmin.py")

   • To access the News configuration file:
     execfile("newsAdmin.py")

   • To access the Wikis configuration file:
     execfile("wikisAdmin.py")

3. To generate a report of all communities that a remote application has interacted with, use the application-specific version of the following command:

   application_nameService.exportSyncedResourceInfo(file_path, event_type)

   where

   • application_name is the application that is affected by the system crash.

   • file_path is a string that specifies the absolute path to the file name. The path can only contain forward slashes. For example, "c:/temp/community_output.xml".

   • event_type is a string value that specifies the event type "community". An error is returned if this is set to anything other than "community".

   In clusters, when we run the command from the deployment manager, the path and file are created on the server running the specified application. In clusters where multiple nodes are running the specified application, we are asked to choose a server to connect to and run the command on, and then the path and file are created on that server.

   Depending on which application or applications we are correcting, choose from the following commands:

   • Activities:

     ActivityService.exportSyncedResourceInfo(filePath,eventType) For example:

     execfile("activitiesAdmin.py")
     ActivityService.exportSyncedResourceInfo("/temp-dir/activitiesOutput.xml", "community")

   • Blogs:

     BlogsAdminService.exportSyncedResourceInfo(filePath, containerType, blogType) For example, to export content for a blog:

     execfile("blogsAdmin.py")
     BlogsAdminService.exportSyncedResourceInfo("/temp-dir/blogsOutput.xml", "community")

     or

     execfile("blogsAdmin.py")
     BlogsAdminService.exportSyncedResourceInfo("/temp-dir/blogsOutput.xml", "community", "Blog")

     To export content for an Ideation Blog:

     execfile("blogsAdmin.py")
     BlogsAdminService.exportSyncedResourceInfo("/temp-dir/IdeationblogsOutput.xml", "community", "IdeationBlog")

   • Files:

     FilesLibraryService.exportSyncedResourceInfo(filePath, eventType) For example:

     execfile("filesAdmin.py")
     FilesLibraryService.exportSyncedResourceInfo("/temp-dir/filesOutput.xml", "community")

   • Forums:

     ForumsService.exportSyncedResourceInfo(filePath, eventType) For example:

     execfile("forumsAdmin.py")
     ForumsService.exportSyncedResourceInfo("/temp-dir/forumsOutput.xml", "community")

   • News:

     NewsMicrobloggingService.exportSyncedResourceInfo(filePath, eventType) For example:

     execfile("newsAdmin.py")
     NewsMicrobloggingService.exportSyncedResourceInfo("/temp-dir/newsOutput.xml", "community")

   • Wikis:

     WikisLibraryService.exportSyncedResourceInfo(filePath, eventType) For example:

     execfile("wikisAdmin.py")
     WikisLibraryService.exportSyncedResourceInfo("/temp-dir/wikisOutput.xml", "community")

   If the Communities database fails, all remote applications are affected and run each of the application-specific commands.

What to do next

The export XML files are used in the steps covered in the next topic to generate a report of how the information differs from the current state of the Communities application. See Generating a synchronization report.

Parent topic:
Recover from a database failure

Related:

Synchronize microblog data with Communities

Related:

Delete orphaned data