Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Migrating search collections

When you migrate or upgrade IBM^® WebSphere^® Portal Express to a later version, the data storage format and index structure of Portal Search is not backward compatible between the different versions. If you migrate your portal to a later version and want to continue using your search collections, you need to preserve them before you migrate your portal.

1. Before you migrate your portal to a later version, export your search collections. This step exports the configuration data and all document URLs of your search collections. Notes:

   1. Before you export a collection, make sure that the portal application process has write access to the target directory location. Otherwise you might get an error message, such as File not found.
   2. When you specify the target directory location for the export, be aware that the export overwrites files in that directory.
2. For each collection, document the following:

   • The target file names and directory locations to which you export the collection.
   • Location, name, description, and language.
   • Settings for the Specify collection language and Remove common words from queries options.
3. Delete the search collections from your existing portal.
4. Upgrade WebSphere Portal Express as required.
5. Create empty search collections that you can use later to hold the imported collections. Fill in the following fields and select the following options according to the information that you documented in step 2:

   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 Categorizer

   The value is overwritten by the import process.

   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 your documented file names and directory locations to which you exported the collections before the portal upgrade.

   When you import a collection, a background process fetches, crawls, and indexes all documents which are listed by URL in the previously exported file. Keep in mind that this process can require a large amount of memory and an extended amount of time.

1. 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 you configured such settings when creating the new collection, they are overwritten by the imported settings.