The user may specify path to the directory which the listener shall observe. The listener doesn't read the directory content recursivelly. The directory must exist.
In cluster environment the directory must exist on each cluster node where the listener may run. If the listener can run concurrently on more nodes, the directory must be shared among all these nodes and the directory must exist on all these nodes.
It's recommended to use placeholders to unify configuration on all nodes.
These are recommended placeholders:
CloverETL Server config property ${sandboxes.home}
and JVM system property ${java.io.tmpdir}.
It's possible to use any JVM system property or Environment variable.
The user may specify URL to the directory which the listener shall observe. Currently these protocols are supported: FTP, S3, SFTP and SMB. Different protocols may use different authentication methods: none, username+password and keystore. The listener doesn't read the directory content recursivelly. The directory must exist.
Currently the subset of the protocols allowed by file-operations is supported:
FTP - File Transfer Protocol (no authentication or username+password authentication) URL example:
ftp://host:23/observed/path/
SFTP (SSH/FTP) - SSH File Transfer Protocol (username+private key authentication) URL example:
sftp://host:23/observed/path/
It's recommended to use placeholders to unify path configuration on all nodes.
These are recommended placeholders: CloverETL Server config property ${sandboxes.home}, JVM system property ${user.home}.
It's possible to use any JVM system property or Environment variable.
S3 - Amazon S3 Storage (AWSAccessKeyId+Signature authentication) URL example:
s3://s3.amazonaws.com/bucketname/path/
Please specify the AWSAccessKeyId as username and Signature as password.
SMB - Microsoft SMB Protocol (username+password authentication) URL example:
smb://host/path/