To configure a search collection, 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.
Ensure that these IBM Connections seedlists are available with basic authentication. Depending on your security configuration, basic authentication might be the default or can be accomplished with an additional virtual host in your HTTP server, by addressing a WebSphere node directly, or by altering Tivoli Access Manager or SiteMinder configuration to open a basic authentication protected endpoint.
Follow these steps to configure a search collection:
1. Log in to IBM WebSphere Portal Console as an Administrator.
2. Navigate to Administration -> Search Administration -> Manage Search -> Search Collections
. Click New Collection
3. Specify the location, and enter a name for the collection, IBMConnections,
and the indexing language of the collection. Click OK
4. We can find that the collection IBMConnections is created and is displayed in Search Collections
. Click on the link IBMConnections
5. In the Content Sources screen, click the button New Content Source
for this collection. In the Content source type drop down list, choose Seedlist provider
. Enter the Content Source Name as Activities
, Collect documents linked from this URL as https://connectionsww.demos.ibm.com/activities/seedlist/myserver
as shown below. This is the Seedlist URL.
Here, the Seedlist URL for a Connections service is of the form https://:port//seedlist/myserver:
6. In the Security Tab of the same screen, enter the Connections server Administrator User Name, Password as wasadmin/passw0rd and Host name. Click Create, then Save to save your content source.
7. Repeat Steps 5, 6 to add Content Sources for other services like Communities, Profiles, Wikis, Blogs, Forums, Files and Bookmarks. The table below lists all the Content Sources that needs to be created in IBMConnections.
Content Source Name
8. Once the Content Sources are added successfully, click on Start Crawler on each of the Content Source. Then, you can find that the Status changes from Running to Idle once it has indexed and collected the documents. Now, the Documents count changes from 0 to some number, if there are documents available in the service.
The figure below lists all the created content source names :
Page 1 :
Page 2 :
9. Now, Navigate to Search Center, and try to search for any word which is stored in a Connections server. Type the search word in the Text Box. Click on the search icon in the search box as shown below.
10. The search returns results as shown below. Here we can find that the search returns results from Portal and Connections. The scope "All sources" is a federated search and it searches content from all the Collections across Portal and Connections. If you want to search only from Portal content or Connections content, we can create a scope that narrows to a specific collection (WCM JCRCollection1 or IBMConnections). The scope can be created from Portal Administration portlet -> Manage Search -> Search Scopes as described in documentation. Then we can choose that specific scope while performing search instead of All Sources scope.
11. When you click on the search result, you are navigated to the respective details portlet to view the details of the selected content as shown below.