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.
Before you begin
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 as described in Recreating
the Search index after migrating from a Connections 4.0 deployment.Note: While
you perform the steps described in the this procedure, Search functionality
is not available to your users.
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 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. Procedure
- Stop all the nodes that are running the Search application.
- Ensure 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 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.
- 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.
Note: This
location should be on the Connections shared file system so it only
needs to be copied once (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: In case you have configured 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 using the SearchService.listIndexingTasks()
command, refer to Listing scheduled tasks.
- Removing an indexing task using the SearchService.deleteTask(String
taskName) command, refer to Deleting scheduled tasks.
- Adding an indexing task using the SearchService.addIndexingTask(String
taskName, String schedule, String startBy, String applicationNames,
Boolean optimizeFlag) command, refer to Adding scheduled tasks.