Configuring the NFS Shares

Connections Docs can utilize a NFS, CIFS or a dedicated storage file server to share data between the different Connections Docs components. File Viewer and Conversion as well as Connections Docs and Conversion need to both access shared storage directories for documents and configuration information.

This section guides you through setting up the server-side shared storage and then providing access to this shared storage from the Connections Docs, Conversion, and File Viewer servers. In addition, it also guides you through setting up the IBM® Connections file content directory access and shares for File Viewer if needed.

Note: You configure the NFS on a NAS or Linux server. When configuring the access to the share, the UID and GID values must match the values that the WebSphere® process is using to run. For example, if the server is running as root, the UID and GID values must be 0 and 0.

Configuring the server-side NFS shares
Shared storage is required for the Connections Docs components to share configuration and document data and information. These specific procedures are required only if you are using one of the Linux servers as an NFS server.
Mounting the NFS share on a Windows server
The Connections Docs Conversion server needs access to the File Viewer and Connections Docs shared storage to be able to store the document data after converting from the native file types. Since Conversion is only supported on Windows, the shared data folders will need to be mounted as Windows shares and provide the proper access for reading and writing from these shares.
Mounting the NFS share on a Linux server
If Docs servers are running on Linux, Docs share needs to be mounted from the Docs servers. If File Viewer servers are running on Linux, they also need to mount the File Viewer.
Configuring the shared data folder as a non-root user
Connections Docs supports non-root configuration for the shared data folder.
Configuring the file content directory for File Viewer using NFS
If File Viewer is not running on IBM Connections nodes, the directory where IBM Connections stores its files must be accessible to File Viewer.

Parent topic: Configuring Connections Docs shared storage