Configuring a remote search service

Configure a remote search service for Portal Search.

1. Log in to your portal as an administrator.
2. Click Administration > Search Administration > Manage Search > Search Services.
3. Click New Search Service.
4. Depending on whether you are using EJB or Web service via SOAP, type Remote PSE service EJB or Remote PSE service SOAP for the service name.
5. For the Search service implementation select Portal Search Service Type.
6. Depending on whether you are using EJB or Web service via SOAP, select the following steps and proceed as appropriate:
   • For EJB: To configure for remote search service via EJB, make the following modifications:
     1. Edit the search service parameter PSE_Type and change its value to ejb.
     2. Modify the parameter IIOP_URL. Set its value to iiop://your_ejb_search_server.your.example_domain.com:port, where your_ejb_search_server.your.example_domain.com is the name of the remote search server and port is the port number that you obtained in the step to determine the port for EJB under Preparing for remote search service. For example, this can be iiop://ejb_server.your_company.com:2809.
     3. Modify the parameter EJB. Set it to the following value: ejb/com/ibm/hrl/portlets/WsPse/WebScannerLiteEJBHome. This is the default JNDI name. If you have modified the EJB parameter to a JNDI name of your own choice, use that name instead.
   • For SOAP: To configure for remote search service as a Web service via SOAP, make the following modifications:
     1. Edit the search service parameter PSE_TYPE and change its value to soap.
     2. Modify the parameter SOAP_URL. Set its value to http://your_soap_search_server.your.example_domain.com:port/WebScannerSOAP/servlet/rpcrouter where your_soap_search_server.your.example_domain.com is the name of the remote search server and port is the port number that you obtained in the step to determine the port for SOAP under Preparing for remote search service. For example, this can be http://soap_server.your_company.com:10000/WebScannerSOAP/servlet/rpcrouter.

     SOAP support for remote search services has been deprecated with WebSphere® Portal Version 8.0.

7. Modify the parameter DefaultCollectionsDirectory to the portal search service. Use it to determine the default directory where your search collections are created on the server that hosts the remote search service. This parameter does not have a default value.
8. Add the parameter CONFIG_FOLDER_PATH to the portal search service. Use it to determine where the configuration data for search collections is stored on the server that hosts the remote search service. The default is wp_profile_root/CollectionsConfig.
9. Click OK to save the new search service. The Manage Search portlet now lists the new search service in the list of search services. A green check in the status column indicates that the new search service is working correctly. If the search service is not working properly, it has a red cross, and a message is displayed. Click the View details link of the message for more information about the problem and how to resolve it.
10. Restart all servers in your configuration for your changes to take effect.