When you upgrade an IBM® Connections 4.5 or 5.0 to
IBM Connections 5.5, the index structure is the same in both
releases and the index can be migrated. This means you do not need to rebuild the search index.
Before you begin
Use this approach when you migrate from IBM
Connections 4.5 or 5.0 to 5.5. If the index is not migrated as outlined in this task, then
rebuilding the search index is a mandatory part of the upgrade as described in Recreating the Search index after
migrating to IBM Connections 5.5.Note: While you
perform the steps described in this procedure, the Search app is not available to your
users.
Note: You can migrate 5.0 indexes to 5.5 with the known restriction that existing forum
attachments do not have their content indexed unless they are updated by the user. New forum
attachment content is indexed.
You can migrate 4.5 indexes to 5.5 with the known restriction that
existing activity attachments and forum attachments do not have their content indexed unless they
are updated by the user. New activity and forum attachment content are indexed.
Older content
is not re-indexed unless it is changed; changing content triggers sending it through the indexing
mechanism again to update the index. If
About this task
Each node in the Search cluster maintains its own local search index. Index migration
involves copying the full search index from the 4.5 or 5.0 deployment to each Search node on the 5.5
deployment. Additionally, searchable content that is extracted from files is retained on disk for
reuse. This content (on the Connections shared file system) is also migrated to the Connections 5.5
deployment.
Procedure
- Stop all the nodes that are running the Search application.
-
Ensure that the local index directory is cleared on each node as described in Deleting
the index.
-
Copy the search index from one of the nodes on the Connections 4.5 or 5.0 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 must 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.5 Search cluster.
-
Copy the extracted file content from the Connections 4.5 or 5.0 deployment to the Connections
5.5 deployment. The location of this file is specified in the WebSphere environment variable EXTRACTED_FILE_STORE.
Note: This location must be on the Connections shared file system so it needs to be copied once only
(not locally to each node).
- Start all the Search nodes in the cluster.
- To ensure that all content is included in the indexing
process, restore the full set of default indexing tasks. Refer to Restoring the default scheduled tasks for
Search for instructions on running the SearchService.resetAllTasks() command.
Note: If you configure custom scheduled tasks and do not want to restore the default scheduled tasks, and if your indexing task names specific application names (instead of 'all_configured'), then you must add the people_finder application name (added in IBM Connections 5.0) to this list. You can update the task to include 'people_finder', by deleting it and adding it back.
For more information about:
- Listing existing indexing tasks by using the
SearchService.listIndexingTasks() command, refer to Listing scheduled
tasks.
- Removing an indexing task by using the SearchService.deleteTask(String
taskName) command, refer to Deleting
scheduled tasks.
- Adding an indexing task by using the SearchService.addIndexingTask(String taskName,
String schedule, String startBy, String applicationNames, Boolean optimizeFlag) command,
refer to Adding scheduled tasks.