EDATEMP and NFS-Mounted Disks

Part of the WebFOCUS Reporting Server process creates pipe and fifo objects in EDATEMP for Interprocess Communication (IPC). However, pipe and fifo object types that are used for IPC, do not work well on NFS-mounted disks; so the prior recommendation was not to use NFS-mounted disks for EDATEMP. To alleviate this problem and allow NFS-mounted disk use, set the EDAIPC system variable to a local non-NFS directory location, so you can redirect pipe and fifo object to this separate non-NFS location. You can point EDATEMP to an NFS-mounted disk, but the pipe and fifo objects go to a local disk.

Normally, the EDATEMP directory defaults to a subdirectory of EDACONF. The EDATEMP variable allows EDACONF file objects, such as edaprint.log and rmdta.log and the EDATEMP directory to be redirected to the location specified by EDATEMP. EDAIPC is usually used with EDATEMP, when EDATEMP is pointed to an NFS-mounted disk. It is also possible that EDACONF itself could be on an NFS-mounted disk (the EDATEMP directory is also on an NFS-mounted disk by parentage) and EDAIPC should also be used in this instance.

For example:

export EDATEMP=/nfs/wfs

export EDAIPC=/tmp/wfs

.../edastart -start

The /tmp directory is always local, but should organizationally be identified by a subdirectory name, such as wfs. If multiple Reporting Servers are run on the same box, there should also be a subdirectory such as wfs/accounting to prevent process collisions.

Note: The pipes and fifos for tscom300 are the only exceptions to the redirection that EDAIPC invokes. Additionally, while the WebFOCUS Reporting Server can detect if NFS is in use, EDAIPC has no default and must be explicitly set to redirect the pipes and fifos.

The EDATEMP and EDAIPC variables may also be set in the EDACONF bin/edaenv.cfg file, using the normal edaenv.cfg rule, which is one variable per line in x=y format (no "export" keyword).