Configure search using Remote Content Server Search Service Type (RCSS)

Use the Remote Content Server Search Service Type (RCSS) to implement live search for Connections content from an IBM WebSphere Portal application.

Consider these issues before you configure RCSS:

• RCSS search is not supported when the deployment is configured to use Tivoli Access Manager and SPNEGO or Computer Associates' SiteMinder and SPNEGO.

• Users who are registered in an LDAP that is common between IBM Connections and WebSphere Portal can be granted administration rights in Portal to configure RCSS using scopes API over http.

Search Service is a live search and uses REST to search on a target information source and fetch the matching results. IBM Connections and WebSphere Portal integration uses RCSS to use the ATOM/REST APIs exposed by IBM Connections. This approach correlates a relevance score for Connections content with the Portal relevance score. It is a federated approach where the search is federated between Portal and Connections instances.

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

2. In the Manage Search section, click New Search Service.

3. Name the service appropriately so that it is easily identifiable, provide this value in the Service Name field.

4. Configure the search service using the following parameters. Possible values for the parameters are provided in the Parameter Value column.

   Parameter Key	Parameter Value
   SearchRequestUrl	Use /atom/search/results in the case where only public content is returned. Use /atom/mysearch/results in the case where public as well as private content is returned.
   RestServiceUnSecureUrl	/search
   ContentType	RemoteContent
   QueryParam	includeField=wikiLabel&includeField=pageLabel&includeField=community_id&query
   IgnoreAllSourcesSearch	false
   RestServiceSecureUrl	/search
   StartParam	start
   AllSourcesParam	scope
   QueryLangParam	queryLang
   DisplayProviderId	ConnRCSS
   RequestLocaleParam	locale
   LocationParam	scope
   RequestLocationType	/atom/scopes
   RestServiceHost	connections.host.com
   RestServiceUnSecurePort	9081 Use the direct server port for the Connections server, not the IHS port.
   RestServiceSecurePort	9444 Use the direct server port for the Connections server, not the IHS port.

5. Log out and log in again before you create scopes for the RCSS service that you configured.

What to do next

The RCSS component does not use the keystore managed by WebSphere Application Server. If we try to set the RestServiceSecureProtocol property to https and the RestServiceSecurePort property to the SSL port for the Connections server when we configure the RCSS search service, we cannot to retrieve the search scopes from Connections and thus cannot complete the search configuration. You see SSL handshake errors in the WebSphere Portal SystemOut logs even though you imported the Connections SSL certificate into the WAS SSL certificate truststore. If we encounter this problem, follow the additional configuration steps that are documented in this tech note.

Parent topic:
Configure search integration