Defining and exposing collections
Users can search the collections that are defined in the archive mapping and search configuration files. These files are part of the archived-data access configuration in the Content Collector configuration store.
About this task
The archive mapping file defines the collections that exist in the Content Collector configuration store. The search configuration file defines what collection sets are displayed on the Email Search page of the IBM® Content Collector web client. These configuration files are also required for viewing or restoring documents.
The archive mapping file and the search configuration file are stored in the Content Collector configuration store. Both files are created during the initial configuration of IBM Content Collector and initially contain default definitions for one collection set with the respective collections and item types or document classes.
For new installations, these settings are automatically imported into the configuration store. However, this import operation happens only once for each type of archived data access. For upgrade installations or when you set up additional repositories, the configuration is not automatically adapted. Instead, additional configuration files are written to the directory installDir\Configuration\initialConfig\data\search\output\cm or installDir\Configuration\initialConfig\data\search\output\p8, depending on your repository. You must then manually merge the contents of the additional configuration files with the existing definitions.
If the default collection set is sufficient for your company, no further configuration is required. However, you can define further collections and collection sets. You can also add item types or document classes to a collection as long as the new definition includes the same attributes and references as one of the existing ones.
If your repository is IBM Content Manager and you want to include legacy item types into the search scope, you must define a new collection by using the templates provided with the product.
Content Collector 4.0.1 fix pack 13 (4.0.1.13): If your repository is IBM Content Manager and you want to use the federated search support, you must define the collection of NSE in the Db2TS template provided with the fix pack.
You can adapt the archive mapping file either by using the graphical user interface of the Configuration Manager or by editing the file. The search configuration file must be adapted manually in any case.