Configure a remote Search in a portal farm
To support Search in a portal farm, install and configure a remote search service. Install and configure it on an IBM WebSphere Application Server instance that is not part of the farm.
- Install the remote search service.
The service is on a remote WAS instance that is not part of the portal farm. We can provide the remote search service either as an EJB or as a web service with SOAP. Deploy the appropriate EJB or SOAP EAR file on the remote WAS instance.
- Configure the search portlets for remote search service so they access the remote server.
- Verify the Seedlist Servlet is started:
- Log on to the WAS console on the remote server, and go to...
Applications | Application Types | WebSphere enterprise applications
- Search for the Seedlist Servlet.
- Verify the Application Status is set to the arrow. If it is not started, click Start.
- Save the changes and then log out of the WAS console.
What to do next
- We must 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 the first time when an administrator selects the Manage Search portlet. If this occurred before configuring the remote search portlet, the default portal site search collection is only available on the primary farm instance. However, it is not available on the remote server. In this case, we must re-create the portal site collection to make it available for search on all instances of the farm.