Directory information properties
The Gateway Server uses its local hard disk drive or other designated storage locations for the source and destination of the transmissions it processes.
To ensure that the inbound X9.37 file with images is only written once, and to ensure the best performance, the intermediatePath, processedPath, and eodCompletePath directories need to be on the same drive as the sourcePath directory. As the file is moved between the directories, it is renamed if the paths are on the same drive. Otherwise, the file must be rewritten to each drive.
| Keyword | Values or example | Description |
|---|---|---|
| sourcePath | /opt/ibm/ftm/runtime-processing/inbound/source | Directory to monitor for incoming X9.37-2003 transmissions. To balance workloads between several instances of Gateway Server, point this source path to a shared directory location. Each Gateway Server
instance with an idle transmission processing thread pulls work from this shared source path. The Gateway Server instances use a file locking scheme to arbitrate ownership of incoming transmissions. Most persistent volume directories need at least read and write permissions for the file owner and the group. In a non-production environment, some paths on the shared persistent volume, such as the Gateway Server source path folder, might need to have read and write permissions for all others, too. |
| intermediatePath | /opt/ibm/ftm/runtime-processing/inbound/processing | Directory where transmissions are stored while they are being processed. |
| ftpRelativePath | Not | This path is the directory from which the transmission file is pulled by FTP (intermediatePath by default) and is relative to the home directory of the user ID that is doing the FTP. If the path is not specified, the absolute path as specified in the intermediatePath is used. This path must not contain blanks. |
| processedPath | /opt/ibm/ftm/runtime-processing/inbound/processed | Directory where transmissions are stored after they are processed. |
| eodCompletePath | /opt/ibm/ftm/runtime-processing/inbound/eod-complete | Directory where transmissions are stored after end-of-day processing is run. |
| errorPath | /opt/ibm/ftm/runtime-processing/inbound/error | Directory where transmissions are copied when errors are detected. This error path can be a directory location that is shared between several instances of Gateway Server. It might be simpler when you are using a source directory location that is shared between those instances of Gateway Server. |
File owner might appear to be different outside and inside the container
Files can be created on the persistent volumes for configuration, during normal processing, and for other reasons. The files that are created outside the containers, on a mounted shared volume for example, have the user identifier (UID) of the external user that created them. The files that are created inside the containers have the user identifier (UID) given to the container user. Certain containers might have more than one user and UID that creates files. When you list the files in a directory on a persistent volume, the file owner that is shown in the list depends on whether you ran the command from outside or inside the container.
For example, say that UID 1001 maps to ftmuser inside the containers and to myuserid on the operating system that you are using outside of the containers. When you list the files from outside the container, all files with UID 1001 are shown as being owned by myuserid even if some were created inside the container by ftmuser. Conversely, when you list the files from inside the container, it looks like all files with UID 1001 are owned by ftmuser even if some were created outside the container by myuserid.