+

Search Tips   |   Advanced Search

Portal, V6.1
Operating systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows

 

Configure Search in a cluster on HP-UX

To support Portal Search in a clustered environment install and configure search for remote search service on an IBM WebSphere Application Server node that is not part of the IBM WebSphere Portal cluster. To enable
search in a cluster for content created using the Authoring portlet provided with WCM , configure each machine in the cluster to access a shared. Created a shared directory called jcr/search on a machine in the network and ensure that each node in the cluster has network access to the. Note for Search users: To support Search in a clustered environment, install and configure search for a remote search service on an WAS node that is not part of the WebSphere Portal cluster. This is needed only if you use the Search Engine to access web content sources.

If you are creating content in a clustered environment using the Authoring portlet provided with WCM , additional configuration steps are required to enable content created by these content features to be searchable in a cluster.

Perform the following steps on each machine in the cluster to configure Search in a clustered environment:

  1. Edit the icm.properties file, in WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm.

  2. Change the value of the jcr.textsearch.indexdirectory property to the shared directory. For example...

    jcr.textsearch.indexdirectory=\\\\your_server\\your_share\\jcr\\search You can specify the shared directory value in one of the following formats:

    Option Description
    Universal Naming Convention (UNC) format \\\\your_server\\your_share\\jcr\\search

    Example: \\\\hostname.example.com\\share\\jcr\\search

    Mounted resource format (with forward slashes): /your_share/jcr/search

    For example: /mnt/jcr/search

    This format requires that you mount the shared directory to the local machine

    For example...

    through a mapped network drive or a mounted directory). When using the mounted resource format, always use forward slashes instead of back slashes, regardless of the native operating system path format.

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

 

Parent topic

Configure search in a cluster