Configure a remote Search in a portal farm
To support Search in a portal farm, install and configure search for remote search service on an IBM WebSphere Application Server instance that is not part of the farm.
Configure remote search
- Install and configure the search service to work remotely.
The service is on a remote WAS instance which is not part of the portal farm. We 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 instance.
- Configure the search portlets for remote search service so that they access the remote server accordingly.
- To ensure that the Seedlist
Servlet is started:
- Log on to the WAS admin console on the remote server.
- Go to Applications > Application Types > WebSphere enterprise applications.
- Search for the Seedlist Servlet.
- Ensure that the Application Status is set to the green arrow. If it is not started, click Start.
- Save the changes and then log out of the WAS admin console.
- If you have configured a remote search service for a portal farm, configure the default location for search collections
to a directory on the remote server that has write access.
- 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 configuring the portlet for remote search, then the default portal site search collection is only available on the primary farm instance, but not on the remote server. In this case you need to re-create the portal site collection to make it available for search on all instances of the farm.
Parent: Configure search in a portal farm