Deleting community microblogs from the News repository
You can use an administrative command to remove orphaned community microblog data as part of the community widget lifecycle disaster recovery scenario.
Before you begin
To run administrative commands, you must use the wsadmin client. See Starting the wsadmin client for details.
About this task
Procedure
- Start the wsadmin client from the following
directory of the system on which you installed the Deployment Manager:
where app_server_root is the WebSphere® Application Server installation directory and dm_profile_root is the Deployment Manager profile directory, typically dmgr01.app_server_root\profiles\dm_profile_root\bin
You must start the client from this directory or subsequent commands that you enter do not execute correctly.
- Start the Jython script interpreter for the News repository.
- Use the following command:
- NewsMicrobloggingService.deleteMicroblogs("communityId")
Removes all microblog and associated data for a community from the News repository.
When you run this command, the status messages are removed from the Status Updates widget in the community. The messages are also removed from the Updates views in Homepage. In addition, the Status Updates widget in the community is set so that no one can add status messages; the community owner can later change this setting by editing the community, selecting the Status Updates tab, and changing the Status Updates setting.
This command takes a single parameter, which is a string that specifies the ID of the community whose microblog data you want to delete.
For example:NewsMicrobloggingService.deleteMicroblogs("e952cf0c-a86c-4e26-b1e0-f8bf40a75804")