Home
Manage the index
Overview
The search feature uses a Lucene 2.4.0 index, supplemented by social facet information. By default, this location is mapped to an IBM Websphere Application Server variable, SEARCH_INDEX_DIR. The value of this variable is by default set to...
<CONNECTIONS_DATA_DIRECTORY>/search/index
The index is generated by retrieving all the necessary information from each IBM Lotus Connections feature on an administrator-defined schedule. Each task defines which features to crawl and whether to optimize the index at the end of the task. The following features can be indexed in Lotus Connections 2.5:
- Activities
- Blogs
- Bookmarks
- Communities
- Files
- Profiles
- Wikis
Search uses the WebSphere Application Server scheduling service for creating and updating the search index. The scheduling service allows you to reliably process workloads using parallel processing, and to schedule resource-intensive tasks during off-peak hours when there is low traffic. Using a dedicated work manager ensures that only one thread is used for indexing.
The WebSphere Application Server scheduling service is based on the Cron calendar, which uses predefined date algorithms to determine when a task should run. While the scheduling service supports the use of a Simple calendar, this is not supported for Lotus Connections 2.5.
Lotus Connections features maintain delete and access-control update information for a maximum of 30 days. If indexing is not performed on an index for 30 days, that index is considered to be out-of-date and reindexing is necessary. Delete and recreate the index to ensure data integrity.
As the information is retrieved from each feature, it is written into a temporary index. Saving the information to a temporary index allows the existing copy to be maintained in an unmodified state in the event that a failure occurs during the indexing process. After each of the Lotus Connections features listed in the task definition has been crawled, the consolidation of social information takes place and the temporary index is merged into the main index.
When indexing on a Microsoft Windows 2008 deployment, you might get the following error: java.io.IOException: Access is denied. This error is caused by an underlying Lucene issue and prevents the index from being updated. To resolve the problem, restart all the machines in the cluster.
See
- Configure scheduled tasks
- Run one-off tasks
- Delete the index
- Backup and restore
- Configure file attachment indexing settings
- SearchCellConfig commands
- SearchService commands