Searching across Lotus Quickr servers

Set up search services for remote IBM® Lotus® Quickr® servers, then make the services available to Portal Search so that users can search across content on all the servers.

Before you begin

Prerequisite:
  • Before setting up search between the portal server and any Lotus Quickr servers, single-signon (SSO) must be enabled and you must exchange LTPA keys between all servers involved, as described here: Preparing security for remote search service in a single-signon domain.
  • Interim fix LO25578 is required for Lotus Quickr Version 8.0 servers.
  • WebSphere Portal only supports searching across Lotus Quickr services for WebSphere Portal (J2EE). WebSphere Portal does not support searching across Lotus Quickr services for Lotus Domino.

About this task

In a collaborative environment where users are working across Lotus Quickr servers, the portal server can be configured to access these remote servers and make the content on the servers available for searching.

To enable users to search content from Lotus Quickr servers, create a new search service on the portal server that retrieves search information from the remote Lotus Quickr servers. This search service discovers search scopes on the Lotus Quickr servers, and represents them as new scope locations on the portal server. Using these new locations, it is possible to define new scopes, which will allow users to search seamlessly across local portal and remote Lotus Quickr content.

Create a new search service as follows:

Procedure

  1. Before setting up a new search service, ensure that both servers are using the correct SSL certificate.
    1. On the Lotus Quickr server, start the IBM Key Management tool, which can be invoked with the ikeyman command in the was_profile_root/bin directory.
    2. Open the DummyServerKeyFile.jks file located in the was_profile_root/etc directory. The password is WebAS.
    3. Click Extract, and then click OK. By default, the cert.arm file is extracted to the was_profile_root/bin directory.
    4. Transfer the cert.arm file to the machine where the portal is installed. If you are working in a clustered environment, copy the file to each node in the cluster.
    5. On the portal server machine, start the IBM Key Management tool.
    6. Open the cacerts file as a JKS key database file. The file is located in the AppServer_root/java/jre/lib/security directory. The password is changeit.
    7. Add the cert.arm file that you transferred from the Lotus Quickr server to the key database file cacerts. To do this, select Add, locate the file cert.arm, and click it.
    8. Click OK, and give the signer certificate a name.
    9. Restart the Lotus Quickr server and the portal server.
  2. Add a new content search service to the local portal server where the search will be initiated.
    1. From the main portal menu, click Manage Search.
    2. In the Manage Search portlet, click Search Services.
    3. Click New Search Service.
    4. Click the drop-down list under Search service implementation, then click Remote Content Server Search Service Type.
  3. Modify the new Search Service configuration by setting the following parameters, if required. Setting the RestServiceHost parameter is required. You must also define a secure port for the parameter RestServiceSecurePort (for example, 10035) during creation of the RCSS Service, and ensure that you use https for the RestServiceSecureProtocol parameter. By default, the service work with scopes, and the remote Lotus Quickr server is excluded from the All Sources scope.
    Table 1. Description of the parameters and their values
    Parameter Value Description
    RestServiceHost example: yourserver.yourcompany.com The host name of the remote Lotus Quickr server. This parameter is required.
    RestServiceSecureProtocol https Protocol required for use with secure port.
    RestServiceSecurePort example: 10035 A secure port. This parameter is required.
    RequestLocationType /scopes for discovering scopes on the remote Lotus Quickr server (default) Represents part of the URL path from the REST Search request for retrieving all available locations on the Lotus Quickr server.
    LocationParam scope if using a scope identifier (default) Represents the location parameter name for the REST Search request against the Lotus Quickr server.
    DefaultCollectionName example: DefaultRemoteContentServerCollection The name of the collection which represents the remote Lotus Quickr search service.
    IgnoreAllSourcesSearch True if the Lotus Quickr results will not be included in the All Sources scope (default)

    False if the Lotus Quickr results need to be included in the All Sources scope

    		 Defines whether the Lotus Quickr search service will participate in the All Sources scope search.
  4. Click OK.
  5. Check that a new collection was generated for the new service with the name as specified in the parameter DefaultCollectionName. This is a virtual collection that represents the remote Lotus Quickr content.

Example

To define a new search scope that includes the location from the remote Lotus Quickr server:
  1. Click Administration > Manage Search.
  2. Click Search Scopes.
  3. Click New Scope.
  4. When creating the new scope, click Select Locations. In the list of locations look for the Remote Content Server Search Service, which contains the Lotus Quickr scope, as defined by the RequestLocationType parameter that was defined in the search service.
  5. Select the scope, or select multiple locations of the scope. Click OK.
    Note: Selecting multiple locations from the same server will result in multiple calls to the remote server, which can cause performance degradation.
For more information about scopes, refer to the Managing search scopes and custom links topics.