Configure JCR search in a cluster

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

1. Create a directory called jcr/search on a server in the network.

2. Ensure that each node in the cluster and the deployment manager has network access to the directory.

3. Set up remote search service on the primary node of the cluster.

1. Log in to the WAS console of the deployment manager and go to...
   Resources | Resource Environment | Resource Environment Providers

2. Choose one of the following two options:
   • Select the appropriate cluster from the Scopes list.
   • Clear the Show Scope check box and select Browse Clusters to specify the portal cluster.

3. Select JCR ConfigService PortalContent > Custom properties.

4. Set the value of...
   jcr.textsearch.indexdirectory

   ...to the parent directory in the remote search server where JCRCollection1 was created. For example...

   jcr.textsearch.indexdirectory=\\\\your_server\\your_share\\jcr\\search

   If the index directory is shared or mounted on the remote search server, we can specify the shared directory value in one of the following formats:

   Format	Shared directory
   Universal Naming Convention (UNC) format	\\\\your_server\\your_share\\jcr\\search For example, \\\\hostname.example.com\\share\\jcr\\search
   Mounted resource format (with forward slashes)	/your_share/jcr/search For example, Y:/share/jcr/search This format requires that you mount the shared directory to the local server (for example, through a mapped network drive or a mounted directory). When we use the mounted resource format, always use forward slashes instead of back slashes, regardless of the operating system path format.

5. Change the jcr.textsearch.PSE.type property to EJB.

6. 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.

7. Change the jcr.textsearch.EJB.EJBName property to the name of the WebScanner EJB. For example...
   ejb/com/ibm/hrl/portlets/WsPse/WebScannerLiteEJBHome

8. Change the jcr.textsearch.enabled value to true.

9. Required: In a cluster, we must drop the JCRCollections in the default search service and then re-create them in a remote search service, otherwise you receive display errors in the search.

   To delete the JCRCollections from the Manage Search portlet:

   1. Log on to WebSphere Portal as an administrator and go to...
      Administration | Search Administration | Manage Search | Search Collections

   2. Click the Delete Collection icon for the JCRCollection1 search collection.

   3. Click OK.

   4. Restart the WebSphere Portal Server.

   5. Go to the Manage Search portlet and confirm the JCRCollection1 search collection was deleted.

   6. Manually create a JCR search collection called JCRCollection1. For more information on creating the JCR search collection, see Set up a JCR search collection in the related links.

Parent Configure search in a cluster

Related tasks:
Set up a JCR search collection
Configure a remote search service