Installing Connect:Direct for UNIX

Before you install Connect:Direct® for UNIX, complete the worksheets to identify all information required to perform the installation.

Connect:Direct for UNIX may be installed on a local disk or a shared disk file system, also known as a clustered file system. Examples of clustered file systems are IBM’s GPFS, Veritas Cluster File System, and Red Hat Global File System.

If Connect:Direct for UNIX is installed on a distributed file system, the distributed file system protocol must be NFSv4, and NFS root squash must be disabled. For example, a NAS device accessed via NFS v4.1 with root squash disabled is supported. (This restriction does not apply if Connect:Direct for UNIX is installed on a local file system and is accessing user files on an NFS file system. For more information about this situation, refer to NFS Restrictions while landing files with download directory set in the userfile.cfg

The only supported distributed file system protocol is NFSv4. For example, a NAS device accessed via NFS v4.1 is supported.
Note: When Connect:Direct for UNIX is installed on NFSv4, performance in high load scenarios may be reduced, significantly for NFSv4.0, as compared to the installation on a local or shared disk file system.
For example, in a development lab environment, a TCQ load test takes up to 3 times as long to run when Connect:Direct is installed on NFSv4.1 or NFSv4.2 than when it is installed on a local file system. When Connect:Direct is installed on NFSv4.0, the load test takes up to 30 times as long to run than when Connect:Direct is installed on a local file system- installing Connect:Direct on NFSv4.0 has limited applicability as a production solution.

Connect:Direct for UNIX requires that you install a server and at least one client location. You can install Connect:Direct for UNIX in different configurations:

  • Install the server on a local system and the clients on remote systems
  • Install the server and at least one client on a local system and the remaining clients on remote systems
  • Install using a Silent Installation. See IBM Connect:Direct for Unix silent installation in the Mass Deployment documentation library.