Configure Portal Search in a cluster on Solaris

To support Portal Search in a clustered environment, install search for remote search service on an IBM WAS node that is not part of the WebSphere Portal cluster.

To install the search service remotely, perform the following tasks:

  1. Configure the search service to work remotely, that is, on a remote WAS node which is not part of the portal cluster. You can provide the remote search service either as an EJB or as a Web service via SOAP. Deploy the appropriate EJB or SOAP EAR file on the remote WAS node.

    For details about how to do this, refer to the WAS documentation.

  2. Configure the search portlets for remote search service so that they access the remote server accordingly.


  1. If you have configured a remote search service for a portal cluster, you need to configure the default location for search collections to a directory on the remote server that has write access.

  2. The portal site default search collection is created only once at the first time when an administrator selects the search administration portlet Manage Search. If this occurred before you configure the portlet for remote search, then the default portal site search collection is only available on the primary node of the cluster, but not on the remote server. In this case recreate the portal site collection to make it available for search on all nodes of the cluster.

Parent topic:

Configure search in a cluster on Solaris

Related concepts

Plan and preparing for Portal Search
Use remote search service

Related tasks

Configure Portal Search for remote search service
Configure the Search and Browse portlet for remote search service
Configure the default location for search collections
Creating or resetting the portal site collection
Configure the primary node to communicate with the deployment manager on Solaris
Configure a remote search service