Migrate the search index from the Connections 4.5 deployment to Connections 5.0

When you upgrade a Connections 4.5 release to Connections 5.0, the index structure is the same between the two releases and the index can be migrated, avoiding the need to rebuild the search index fully.

This approach is recommended when migrating from IBM Connections 4.5 to 5.0. If the index is not migrated as outlined in this task, then rebuilding the search index is a mandatory part of the upgrade.

While you perform the steps described in the this procedure, search functionality is not available to the users.

Each node in the Search cluster maintains its own local search index. Index migration involves copying the full search index from the 4.5 deployment to each Search node on the 5.0 deployment. Additionally, searchable content that has been extracted from files is retained on disk for reuse. This content (on the Connections shared file system) is also migrated to the Connections 5.0 deployment.

1. Stop all the nodes running the Search application.

2. Ensure the local index directory is cleared on each node.

3. Copy the search index from one of the nodes on the Connections 4.5 deployment. If one or more of the nodes on that deployment was offline for a period, copy the index from the most up-to-date node.

   The index should be copied to the local disk location specified in the WebSphere environment variable SEARCH_INDEX_DIR. The index must be copied to this location on every node in the Connections 5.0 Search cluster.

4. Copy the extracted file content from the Connections 4.5 deployment to the Connections 5.0 deployment.

   The location of this is specified in the WebSphere environment variable EXTRACTED_FILE_STORE. This location should be on the Connections shared file system so it only needs to be copied once (not locally to each node).

5. Start all the Search nodes in the cluster.

6. To ensure that all content is included in the indexing process, restore the full set of default indexing tasks.

   In scheduled tasks were configured, and you do not want to restore the default scheduled tasks, and if the indexing task names specific application names (instead of 'all_configured'), then add the people_finder application name (added in Connections 5.0) to this list. We can update the task to include 'people_finder', by deleting it and adding it back.

   • List existing indexing tasks using...
     SearchService.listIndexingTasks()

   • Remove an indexing task using...
     SearchService.deleteTask(String taskName)

   • Add an indexing task using...
     SearchService.addIndexingTask(String taskName, String schedule, String startBy, String applicationNames, Boolean optimizeFlag)