Configuring JCR search in a cluster on Linux

To enable search in a cluster for content stored in the JCR database, you must configure each server in the cluster to access a directory. JCR-based content includes content created with Web Content Manager or Personalization.

Before you begin

Set up the remote search service on the primary node of the cluster; refer to Configuring a remote search service for information.

About this task

Complete the following steps on each server in the cluster to configure Search in a clustered environment:

Procedure

  1. Edit the icm.properties file, located in the wp_profile_root/PortalServer/jcr/lib/com/ibm/icm directory.
  2. Change the value of the jcr.textsearch.indexdirectory property to point to the index directory. For example, jcr.textsearch.indexdirectory=/opt/IBM/WebSphere/wp_profile/PortalServer/jcr/searchIndexes.
  3. Based on the configuration of your remote search service, change the jcr.textsearch.PSE.type property to either EJB or SOAP; then choose the appropriate additional steps:
    Table 1. The steps depending on the value for the jcr.textsearch.PSE.type property.
    Value Additional steps
    EJB Complete the following steps if you have an EJB service:
    1. Change the jcr.textsearch.EJB.IIOP.URL property to the URL of the naming service used to access the WebScanner EJB; for example iiop://localhost:2811.
    2. change the jcr.textsearch.EJB.EJBName property to the name of the WebScanner EJB; for example ejb/com/ibm/hrl/portlets/WsPse/WebScannerLiteEJBHome.
    SOAP If you have a SOAP service, change the jcr.textsearch.SOAP.url property to the SOAP URL of the WebScanner for the search service.
  4. Change the jcr.textsearch.enabled value in the icm.properties file to true.
  5. Required: Complete the following steps to delete the default search collections from the Manage Search portlet:
    1. Log on to WebSphere® Portal as an administrator.
    2. Click Administration > Search Administration > Manage Search.
    3. Click Search Collections.
    4. Click the Delete Collection icon for the Portal Content search collection.
    5. Click OK.
    6. Restart the WebSphere_Portal server.
    7. Go to the Manage Search portlet and confirm that the Portal Content search collection was deleted.
    8. Manually create a JCR Collection called JCRCollection1; refer to Setting up JCR Search Collection for information.