Portal, V6.1

---

 

Exporting and importing search collections

This topic describes how you export search collections from a source portal and import them into a target portal. The following are possible use cases for exporting and importing search collections:

• You have verified your search collections on a test portal, and you want to move these collections to your production portal.

• You have verified your search collections locally on a portal, and you want to move these collections to a configuration with remote search.

• You have verified your portal search configuration and search collections on a single portal, and you want to move these collections to a portal cluster environment.

• You are staging your portal to production by using the ReleaseBuilder.

To export and import your search collections, use the Import or Export Collection option of the Manage Search portlet. Use that option for both exporting and importing. For more details about these tasks and the Manage Search portlet refer to the portlet help. To export and import your search collections, proceed by the following steps:

1. On the source portal export your search collections. This 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 can overwrite files in that.

2. Document all of the following data:

   • The target file names and directory locations to which you export the collections.

   • The following configuration data of the collections:

     • The location, name, description, and language for each of the collections

     • The settings for the options Specify collection language and Remove common words from queries for each collection.

3. Create the search collections on the target portal. This task creates the empty shell for the search collection. Fill in the following data entry fields and select the following options according to the data that you documented:

   • Location of Collection:

     Fill this in with the new collection location.

   • Name of Collection:

     Fill this in with the collection name. The name can match the old setting, but does not have to match it.

   • Description of Collection:

     Fill this in with the collection description. The description can match the old setting, but does not have to match it.

   • Specify Collection Language:

     Select this to match the old setting.

   • Select Categorizer: You do not need to select this option. the value will be overwritten by the import.

   • Select Summarizer: You do not need to select this option. the value will be overwritten by the import.

   • Remove common words from queries (e. g. in, of, on, etc.):

     Check or uncheck this to match the old setting.

   You do not have to add content sources or documents; that will be completed by the import task.

4. Import the data of your search collections into the target portal. For the import source information use your documented file names and directory locations to which you exported the collections before the portal upgrade.

Notes:

1. Additionally to exporting and importing your search collections, you have to configure Portal Search on the target portal. This depends on the requirements of your target portal environment and configuration. For details about how to do this refer to the appropriate topics of the Portal Search documentation such as Planning and preparing for Portal Search and Administering Portal Search.

2. 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.

3. Import collection data only into an empty collection. Do not import collection data into a target collection that has content sources or documents already.

4. When you import search collection data into a collection, most of the collection configuration data are also imported. For example, this includes the content sources, schedulers, filters, and language settings. If you configured such settings when creating the new collection, they are overwritten by the imported settings.

5. To migrate from one portal version to a higher version, you need to delete the search collections between the export and the re-import. Follow the steps described under Migrating Web search collections.

6. When you import a portal site collection from a V5.1 portal to a V6 portal, the collection configuration data are imported, but not the documents. Therefore, to enable users to search the portal site collection on the target portal, you can either import the portal site collection and then start a crawl, or recreate the portal site collection. For details about how to do this refer to Creating or resetting the portal site collection. This restriction does not apply if you migrate your portal site search collections between V6 portals.

7. When you import a collection, a background process fetches, crawls, and indexes all documents which are listed by URL in the previously exported file. Therefore be aware of the Memory required for crawls and the Time required for crawls and imports and availability of documents.

 

Parent topic

Set up search collections

 

Related concepts

Planning and preparing for Portal Search

 

Related tasks

Manage the content sources of a search collection
Administering Portal Search
Creating or resetting the portal site collection

 

Related reference

Creating and configuring search collections
Hints and tips for using Portal Search

 

Related information

Portal Search

---