When the index of IBM Connections seems to be corrupt, and you have a clustered WebSphere configuration, it’s very easy to rebuild the index without any downtime of the services.
First you have to determine the index location.
In this case it was: D:\IBM\Connections\data\local\search\index because it was a Microsoft Windows server.
Create the temp folders for your background index.
D:\Background\backgroundCrawl
D:\Background\backgroundFileExtraction
D:\Background\backgroundIndex
Start wsadmin on the Dmgr01 and start the searchAdmin.
Open CMD.
D:
cd D:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
wsadmin.bat -lang jython
execfile(“searchAdmin.py”)
Start the BackGround indexer for all features.
SearchService.startBackgroundIndex(“D:\\Background\\backgroundCrawl”, “D:\\Background\\backgroundFileExtraction”, “D:\\Background\\backgroundIndex”, “all_configured”)
Disable all Index Tasks.
SearchService.disableTask(“15min-search-indexing-task”)
SearchService.disableTask(“nightly-optimize-task”)
SearchService.disableTask(“20min-file-retrieval-task”)
SearchService.disableTask(“nightly-sand-task”)
Stop the JVM where Search is running on from Node1.
Rename old index or move to secure location.
ren D:\IBM\Connections\data\local\search\index D:\IBM\Connections\data\local\search\index-old
Copy new index to correct location
md D:\IBM\Connections\data\local\search\index
mv D:\Background\* D:\IBM\Connections\data\local\search\index\*
Start JVM from Node1 and repeat this process from “Stop the JVM where Search is running on from Node1” but now for Node2
Please be aware to copy the data over your network for Node2
Enable all Index Tasks.
SearchService.enableTask(“15min-search-indexing-task”)
SearchService.enableTask(“nightly-optimize-task”)
SearchService.enableTask(“20min-file-retrieval-task”)
SearchService.enableTask(“nightly-sand-task”)
Clear traces from previous index.
SearchService.notifyRestore(“true”)
Reindex PeopleFinder
SearchService.addRunOncePeopleFinderSaNDIndexingTask()
Visits: 332