Enable Search functionality by building the index and copying it to each node that is running the Search application.
About this task
In IBM® Lotus® Connections 3, each node running the Search application must have the Search index stored locally on the node's file system. This configuration change is required due to limitations with Apache Lucene indexes that are accessed over network shares. Because there are multiple indexes in a clustered environment, they must all be kept in synchronization with each other. During update indexing, documents are first written to a cache table in the HOMEPAGE database and then written to each index across the nodes. When an new index needs to be built, the database cache is skipped, and the crawling and indexing process writes directly to the index directory on the node that is performing the indexing task. After indexing has been completed, the complete index must be copied to the other nodes in the cluster that are running Search. Search functionality is not available until the index is built and deployed to each node. The index is built and ready to be copied when the INDEX.READY
files are present in the index directory.
Initial index creation occurs when any scheduled indexing task fires and an index does not yet exist.
- Start one Search node in the cluster.
- Wait for the index to be built.
- Stop all the nodes that are running Search.ear.
- Copy the built index directory to the index directory on each node running the Search application.
- Start all the nodes.
Parent topic: Administering Search