Configure a search collection

Search Collections use a seedlist framework to crawl, and index all of the Connections data locally on a WebSphere Portal Server .

To configure a search collection, we specify one content source for each Connections seed list. Each Connections service (for example, Profiles, Communities, or Blogs) exposes its own seed list so there is one content source per Connections service.

Important: Ensure these IBM Connections seedlists are available with basic authentication. Depending on the security configuration, basic authentication might be the default or can be accomplished with an additional virtual host in the HTTP server, by addressing a WebSphere node directly, or by altering Tivoli Access Manager or SiteMinder configuration to open a basic authentication protected endpoint.

1. Click the Administration link in the header of the portal page.

2. In the Manage Search section, click Search Collection.

3. Click New Collection.

4. Define the location of the collection on the portal file system, and name it with an easily identifiable value.

5. Click OK to create the collection and create the associated folders and files on the file system.

   The path must not point to an existing directory.

6. Click Collection to view the metadata of the collection created.

7. For each Connections service to integrate with Portal search:

   1. Click New Content Source.

   2. Select Seedlist Provider as the Content source type.

   3. Provide the name and the seedlist URL of the Connections service. A Seedlist URL has the form: https://<connection_server_name>:port/<service_name>/seedlist/myserver For example: https://connections.ibm.com:9444/activities/seedlist/myserver.

      If IBM Connections is configured to use Tivoli Access Manager and SPNEGO security, or just SPNEGO, configure the seedlist URL and host without Tivoli Access Manager, using IHS host only.

   4. Click the Security tab and enter the Connections administrator credentials so that we can access the service seedlist URL, then click the Create button.

   5. Click Create to create the corresponding Content Source to enable crawling over the specified service.

   6. Create other Connections services, for example, Activities, or Blogs, by repeating these steps.

      We can either select to run the crawler on the complete set or on individual service

Parent topic:
Configure search integration