Start of changeFileNet P8 Content Search Engine, Version 5.0.+            Operating systems:  AIX, HP-UX, Linux, Solaris

Migrating existing indexes into IBM Content Search Services

IBM® Legacy Content Search Engine users who are moving to IBM Content Search Services can migrate their existing indexes to an IBM Content Search Services object store. This option is only supported for custom applications in IBM Content Search Services 5.0.

When you initiate the index migration process, a background job processes objects that are currently indexed in IBM Legacy Content Search Engine and indexes them into an IBM Content Search Services object store. Any objects that are created after the index migration process is started are indexed in both IBM Legacy Content Search Engine and IBM Content Search Services. The object store operates in this dual indexing mode until the index migration process completes and you disable IBM Legacy Content Search Engine.
Important: Disabling IBM Legacy Content Search Engine, cannot be reversed. Make sure that the index migration process has completed and searches are working correctly on IBM Content Search Services before you disable IBM Legacy Content Search Engine.

Complete the following tasks before you start the migration process:

To migrate your existing indexes to an IBM Content Search Services object store:

  1. Set the TextSearchEnabled property value of the object store to true to initiate the index migration process.
  2. Change the syntax of the content-based queries from K2 VQL to Lucene after the migration phase.
  3. Open a document on IBM Content Search Services and verify that searches are working correctly.
  4. Disable IBM Legacy Content Search Engine.


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)
End of change