Cooperative file listening configuration

Cooperative file listening requirements
Cooperative file listening requires single source-event watches and source-event files that are created by atomic operation. It supports the GPFS and NFS shared network file systems as well as POSIX-compliant local file systems.
Cooperative file listening config.yaml file and Launcher settings
You enable cooperative file listening in the config.yaml configuration file and in the /runtime/launchersettings.
Error directory configuration
When cooperative file listening is enabled and the output card specifies OnFailure=Rollback, the File adapter moves the source-event file to an error directory when a map fails. The error directory is a subdirectory of the trigger directory. You can use the default error directory, or specify the error directory as an absolute file path, a relative file path, or an alias that is defined in the Resource Registry.
Keep directory configuration
A keep directory stores source-event files after a map successfully processes them. A keep directory is always available when cooperative file listening is enabled in the config.yaml file. When cooperative file listening is not enabled, a keep directory is available if you explicitly configure its directory path in the Launcher settings. The OnSuccess setting of the input card must be Keep or KeepOnContent to save source-event files in a keep directory.

Parent topic: Cooperative file listening: Multiple watches monitor a single trigger directory