This integration point is enabled by configuring the portal search center component to include
Connections content as part of the related search results. You also need to configure a component to allow the navigation from the portal search center to the portlets so that users can view the Connections related search results.
Portal currently provides the following two search frameworks. The one you use depends on whether you value performance or ease of maintenance.
Search Service is a live search and leverages REST (along with other technologies ) to search on a target information source and fetch the matching results. Connections/Portal integration uses the "Remote Content Server Search Service Type" (referred to as RCSS type), leveraging the ATOM/REST APIs exposed by Connections. This approach would tag relevance score of connections content, in isolation, to the portal relevance score. It is a federated approach in which the search is federated between Portal and Connections instances.Search Collections
Search Collections uses a seedlist framework to crawl and index all of the Connections data locally on a Portal server. The advantage of this approach is that it removes extra network traffic to the Connections server during the search process, making information retrieval fast. One disadvantage is that the crawler needs to run frequently to synchronize local content with all the latest content on the Connections server. It can do a better relevance ranking of search results, as search results (including Portal and Connections) are served by the Portal engine only.Excluding Connections Portlets from Portal default search indexing
Exclude the Connections portlets from the default Portal search indexing.
Deploying search integration prerequisites
When you configure search integration for 220.127.116.11, manually copy some of the supporting files to your system
Deploying search integration prerequisites (Refresh)
Follow these steps to configure search integration.
Configuring search using Remote Content Server Search Service Type (RCSS)
Use the Remote Content Server Search Service Type (RCSS) to implement live search for IBM
Connections content from an IBM WebSphere
® Portal application.
Configuring a search collection
Search Collections uses a seedlist framework to crawl and index all of the IBM
Connections data locally on a WebSphere
Setting the Search Scope
Define search scopes for the content from IBM
Connections that is returned from a search in IBM WebSphere