IBM FileNet P8, Version 5.2.1            

Configuring the NetApp Snaplock fixed content device

Before you can create a Content Platform Engine object to represent a NetApp Snaplock fixed content device, you must configure the device, and the device must be accessible to the Content Platform Engine network.

Procedure

To configure a connection on the NetApp Snaplock device:

  1. Use the NetApp administration utility to create a SnapLock compliant volume. Adjust the default settings as needed.
    Important: The default settings for the directory size and the maximum number of files are not sufficient for handling a large amount of content.
  2. Make the SnapLock device accessible to the Content Platform Engine network. Specifically, create a Network File System (NFS) share (or mount), a Common Internet File System (CIFS) share, or a Logical Unit Number (LUN) in an iSCSI or Fibre Channel network. The share, mount, or LUN that you create is referred to as the base directory.
  3. Grant full access to the base directory to Content Platform Engine. Content Platform Engine can now use file system protocols to read, write, and delete files that reside in the base directory.
  4. Create a NetApp user for the NetApp API. You can create the NetApp user when you configure the SnapLock fixed content device. The NetApp user must have the following NetApp capabilities: api-*,login-http-admin. For detailed instructions on creating a local NetApp API user for Content Platform Engine, see Configuring SnapLock with FileNet® P8 Content Engine 4.x on UNIX with non-root users.
  5. Ensure that HTTP access is enabled on the NetApp system. On systems that are shipped with Data ONTAP 8.1 7-Mode, HTTP access is disabled by default. To enable HTTP access, run the following commands from the NetApp command line:
    options httpd.enable on
    options httpd.admin.enable on


Last updated: October 2015
p8pcc116.htm

© Copyright IBM Corporation 2015.