Use remote search service
You can configure the search portlets for local operation, or you can configure them for remote search service. Depending on your configuration, remote search service might have performance benefits by offloading and balancing system load.
You can provide the remote search service either as an EJB or as a Web service via SOAP. With EJB you can have security enabled. With SOAP this is not possible.
When you want to index and search portal sites, search results are filtered according to the user security credentials. This filtering occurs independently of whether security is enabled on the remote search server or not. However, if security is not enabled, an unauthorized user can connect to the remote server and obtain unfiltered search results. To prevent this, use EJB and enable security on the remote server. For details about enabling security on the remote search server, refer to Prepare security for remote search service in a single-signon domain.
- Prepare for remote search service
Get an overview of how you prepare the portal system for remote search service. You can provide remote search service by either using EJB or SOAP.
- Prepare security for remote search service in a single-signon domain
View the steps to set up portal security for remote search service on a single-signon installation.
- Set the search user ID
If you work with EJB on a secure server, set the search user ID.
- Configure Portal Search for remote search service
View steps to configure Portal search for remote search service.
- Configure the Search and Browse portlet for local or remote search
You can configure the Search and Browse portlet for local or remote search.
Parent topic:
Plan and preparing for Portal Search