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.


Before you begin

To use wsadmin commands, use the IBM WAS wsadmin client. See Starting the wsadmin client for details.


About this task

Communities can integrate with the Activities, Blogs, Files, Forums, and Wikis applications as remote applications. As part of recovering from an incomplete database restore operation, you can run the CommunitiesRemoteAppService commands for each remote application that is listed in the orphanedRemoteApplications report because it is missing its containing community or only its widget in a containing community. Alternatively, you can delete any orphaned data from the remote applications. For more information about deleted orphaned data, see Delete orphaned data.


Procedure

To resolve inconsistencies between remote applications and communities...

  1. From the dmgr host:

  2. To access the Blogs configuration file, use the following command:

      execfile("blogsAdmin.py")

  3. To access the Files configuration file, use the following command:

      execfile("filesAdmin.py")

  4. To access the Forums configuration file, use the following command:

      execfile("forumsAdmin.py")

  5. To access the Wikis configuration file, use the following command:

      execfile("wikisAdmin.py")

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

      <application_name>Service.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".

      Note: In clusters, when you 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, you 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 you are correcting, choose from the following commands:

      • Activities:

          ActivityService.exportSyncedResourceInfo(filePath,eventType)

      • For example:

          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:

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

      • Forums:

          ForumsService.exportSyncedResourceInfo(filePath, eventType)

      • For example:

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

      • Wikis:

          WikisLibraryService.exportSyncedResourceInfo(filePath, eventType)

      • For example:

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

      Note: If the Communities database fails, all remote applications are affected and you need to 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. For more information, see Generating a synchronization report.


Parent topic

Recovering from a database failure
Previous topic: Restore communities with remote applications
Next topic: Generating a synchronization report


Related tasks


Delete orphaned data
Generating a synchronization report
Restore Activities data
Backing up Activities data

Related reference
Activities administrative commands
Wikis administrative commands
Files administrative commands


   

 

});