FileNet P8 Content Search Engine, Version 5.0.+            Operating systems:  AIX, HP-UX, Linux, Solaris, Windows

Collections directory requirements for IBM Legacy Content Search Engine

The task of creating a collections directory includes setting up security permissions to allow read and write access.

Important: Contrary to information outlined in the Autonomy-supplied documentation set, remote collections are not supported for use with IBM® Legacy Content Search Engine. Collections must be written locally to the Autonomy K2 server. Using a remote-mounted disk that is accessed using the network (NFS, PCNFS, or CIFS) causes stability problems under load and corrupt your collections. Any existing configurations that contain non-local collections directories must be reconfigured.

To create a collections directory:

  1. Create a directory in which to store collections (VerityIndexArea.RootDirectoryPath). This directory must be located on a disk that is local to the Verity server. Set permissions to allow access to the k2_os_user.

    This path must be local to the index server that is assigned to write collections.

  2. Create a temp directory (VerityIndexArea.TempDirectoryPath) which is used by the K2 Index Server and Content Engine Server during operations.

    Content Engine and the Autonomy K2 servers, the K2 Administration Server and Content Engine must be on the same machine or on a network mounted file system.

  3. Provide read/write access to the collections directory for Autonomy K2 by entering the full path to the location and record the temp collections path.
    Option Description
    Windows
    1. Open the following K2 configuration file in a text editor (default path shown): verity_install_path\k2\common\verity.cfg
    2. Modify the next available alias settings by adding the collections path, where new collections are written. For example, change alias6, mapping6, and dirmode6 to the following settings:
      alias6=path1
      mapping6=C:\Collections_Directory
      dirmode6=wr
    UNIX
    1. Open the following K2 configuration file in a text editor (default path shown): verity_install_path/k2/common/verity.cfg

    2. Modify the next available alias settings by adding the collections path. For example, change alias6, mapping6, and dirmode6 to the following settings:
      alias6=path1
      mapping6=/Collections_Directory_Path
      dirmode6=wr

      The Collections_Directory_Path must be a local path and not a mount point.

  4. Set file store access. Each file store that is full text indexed must be accessible by the Autonomy K2 server that performs the full text indexing. Permissions on the file store must be set the same as the permissions on the collections directories. Having the same permissions allows both the Content Engine Operating System User and the Verity Operating System User to access them. The names of the file store directories must also be the same on each server that access the directories.

    Although we are mapping remote collections, which are not supported, indexing is not run on these indexes. The mapping is used to close the collections.



Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)