Portal V6.1.x on application server V7: Migrating Portal search collections

The data storage format and index structure of Portal Search is not backward compatible between the different versions. To migrate, preserve search data and indexes before migration, then import into the upgraded portal after the migration.

To export and import the search collections, use the Import and Export Collections options of the Manage Search portlet.

To migrate the search collections...

1. Export the configuration data and document URLs of the search collections.

   1. Verify the portal application process has write access to the target directory.
   2. Files in the target directory are overwritten.

2. For each collection, document the following data:

   • The target file names and directory locations to which you export the collection.
   • Location, name, description, and language.
   • Setting for collection language
   • Settings for Remove common words

3. Delete the search collections from the existing portal.

   Otherwise they can be corrupted by the import step that follows later. If we are upgrading from one portal version to another, you do not need to delete the search collections, as the new collections are stored under a different directory path location.

4. Upgrade WebSphere Portal

5. Create empty search collections using the following parameters

   Location of Collection

   The location can match the old setting, but does not have to match it.

   Name of Collection

   The name can match the old setting, but does not have to match it.

   Description of Collection

   The description can match the old setting, but does not have to match it.

   Specify Collection Language

   Select this to match the old setting as documented in step 2.

   Select Summarizer

   The value is overwritten by the import process.

   Remove common words from queries (for example. in, of, on, etc.)

   Check or clear this setting to match the old setting as documented in step 2.

   You do not have to add content sources or documents, as that is completed by the import process.

6. Check that the target search collections that you created in step 5 are empty.

   Do not import collection data into a target collection that already contains sources or documents.

7. Import the search collection data into the portal.

   For the import source information, use the documented file names and directory locations to which you exported the collections before the portal upgrade.

8. When importing Web Content Manager collections:

   1. Modify the target URL for the affected content sources to use the IP address of the new portal server.
      Content source > General parameters > Collect documents linked from this URL

   2. Modify the SeedlistID in the target URL to use site area path, for example...

      SeedlistId=Migration/Site01/SiteArea01

   3. Modify the hostname of security realms for the affected content sources to use the IP address of the new portal server...
      Content source > Security tab > Edit security item button > Host Name

When you import search collection data into a collection, most of the configuration data (for example, content sources, schedulers, filters, and language settings) are also imported. If we configured such settings when creating the collection, they are overwritten by the imported settings.

Parent: Migrate search components