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

Collections directory requirements

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® FileNet® P8 Content Search Engine. Collections must be written locally to the Autonomy K2 server. Using a remote-mounted disk that is accessed via the network (NFS, PCNFS, or CIFS) will cause stability problems under load and corrupt your collections. Any existing configurations that contain non-local collections directories must be re-configured.

For performance reasons, create one collections directory for each index area that you create in IBM FileNet P8 Content Engine. Each collections directory you create must be set to provide proper security access as outlined below. The path to both the collections directory and collections temp directory must be entered in the index area properties when you create the index area.

Security and communication between Autonomy K2 Content Engine, and the collections directory is handled through the user accounts and permissions provided to those accounts.

For detailed information on security, see the IBM FileNet P8 help topic Security > IBM FileNet P8 Security > Security for integrated components and third-party products > Security for Legacy Content Search Engine.

To create a collections directory:

  1. On the Autonomy K2 server, create a directory in which you will store K2 collections. Give read, write, and execute permissions to the k2_os_user.

    This path must be local to the index server that will be assigned to write collections. This is the same index server that you created when you configured Content Search Engine.

  2. Create a temp directory on the Autonomy K2 machine on which you created the collections directory. The temp directory will be used by the K2 Index Server and Content Engine Server during operations.

    This path must be visible to both the Content Engine and the Content Search Engine servers. If the K2 Master Administration Server and Content Engine are not installed on the same machine, they both must be on a network-mounted file system.

  3. Record the collections directory path in the Autonomy K2 configuration file.
    Option Description
    Windows®
    1. Open the following K2 configuration file in a text editor:

      verity_install_path\k2\common\verity.cfg

    2. Modify the next available alias settings by adding the collections path, where new collections will be written. For example, change alias6, mapping6, and dirmode6 to the following:
      alias6=path1
      mapping6=C:\Collections_Directory
      dirmode6=wr
    3. Save our edits.
    UNIX®
    1. Open the following K2 configuration file in a text editor:

      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:
      alias6=path1
      mapping6=/Collections_Directory_Path
      dirmode6=wr
      Restriction: The Collections_Directory_Path must be a local path and not a mount point.
    3. Save your edits.


Feedback

Last updated: November 2010


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