Manipulating the resume tokens for HCL Connections services

Use administrative commands to manipulate the resume tokens in the Search index.

Before you begin

To use administrative commands, you must use the wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin client.
  1. You must have an index in place because the commands manipulate the resume tokens in a valid index.
  2. Do not run this command against a foreground index.

About this task

Use the Search application to update the resume tokens for components in an index. When this index is then used as the foreground index, crawling of the components resumes from the time and date that is specified in the updated resume tokens.


To manipulate resume tokens, complete the following steps.
Use the following command to run one-off indexing tasks.
SearchService.updateResumeTokens(String components, String date, String indexLocation)
Updates the resume tokens in the index.
Note: You can run this command on background indexes only.
This command takes the following arguments:
The applications whose resume tokens are to be manipulated. The following values are valid:
  • activities
  • all_configured
  • blogs
  • calendar
  • communities
  • dogear
  • ecm_files
  • files
  • forums
  • people_finder
  • profiles
  • status_updates
  • wikis

Use all_configured instead of listing all indexable services when you want to manipulate the resume tokens.

The date the resume tokens are changed to; date is in the format MM-dd-yyyy HH:mm:ss:SSSZ.

For example: 08-01-2013 14:00:00:000-0000

The location that contains the index that has its resume tokens updated.

For example: /opt/IBM/Connections/data/search/index_backup

If the command works correctly and the resume tokens are updated, the value "1" is returned on the command line. If the resume tokens are not updated the value "0" is returned on the command line.


SearchService.updateResumeTokens("all_configured","08-01-2013 14:00:00:000-0000", 
activities,blogs,communities,forums,files,dogear","08-01-2013 14:00:00:000-0000", 

What to do next

Restore the updated index to all nodes in the cluster. For more information, see Restoring the Search index.