Ability to Define Custom Temporary Transfer Directory for FTE Transfers in Containerized ACE Environments

In our containerized IBM App Connect Enterprise deployment, we are using the FTE Transfer node to perform Managed File Transfers (MFT) to a remote queue manager.

We’ve observed that during runtime, ACE dynamically creates a subdirectory named after the integration server container instance (e.g., <nameSpace>-<podName>_<uniqueID>) where transfer-related files are stored.

When a file transfer fails — for example, due to the remote agent being unavailable — the failed files are written into this container-specific directory path. For instance:

/home/aceuser/ace-server/config/common/FTE/integration_server/<nameSpace>-<podName>_<uniqueID>/Transfers/test/FTE Output/testfile123.txt  

Request:
We would like the ability to explicitly configure the directory used for failed or in-transit transfers to a fixed, custom path. This would help us:

• Easily locate and reprocess failed transfers
• Maintain predictable directory structures across container restarts
• Automatic Continuation of File Transfers After Container Crash/Restart
• Simplify persistent volume mappings and operational monitoring in containerized environments

Proposed Solution Ideas:

• Introduce a new configuration option (e.g., temporaryTransferDir or failedTransferDirectory) to control where these files are stored
• Support an environment variable that overrides the default runtime-generated directory
• Add configuration options to the FTE Transfer node itself for custom error or retry directories

This enhancement would improve the manageability, observability, and reusability of file transfer operations in modern, cloud-native ACE deployments.