URL attributes may be defined using the URL File Dialog.
Unless explicitly stated otherwise, URL attributes of File Operation components accept multiple URLs separated with a semicolon (';').
To ensure graph portability, forward slashes must be used when defining the path in URLs (even on Microsoft Windows).
Most protocols support wildcards:
? (question mark) matches
one arbitrary character;
* (asterisk) matches any number
of arbitrary characters. Note that wildcard support and their syntax is
Below are some examples of possible URL for File Operations:
One specified file.
Two specified files.
All files satisfying the mask.
All files in the specified directory.
.txt files in directories that satisfy
path/filename.txt file on a remote
server connected via an FTP protocol using username and password.
If the initial working directory differs from the server root directory, please use absolute FTP paths, see below.
/path/filename.txt file on a remote
server - the initial slash must be escaped as
The path is absolute with respect to the server root directory.
Denotes all files satisfying the mask on a remote server connected via an FTP protocol using username and password.
filename.txt file on a remote server
connected via an SFTP protocol using username and password.
Denotes all files
filename.txt in directories
satisfying the mask on a remote server connected via SFTP protocol
using username and password.
filename.txt file on a remote
server connected via an HTTP protocol.
filename.txt file on a remote
server connected via an HTTPS protocol.
path/filename.txt object located in
Amazon S3 web storage service in a bucket
The connection is established using the specified access key ID and
secret access key.
filename.txt file on Hadoop HDFS.
CONNECTION_ID" stands for the ID of a Hadoop
connection defined in a graph.
Denotes a file located in a Windows share (Microsoft SMB/CIFS protocol).
The URL path may contain wildcards (both * and ? are supported). The
server part may be a DNS name, an IP address or
a NetBIOS name. The Userinfo part of the URL (
is not mandatory and any URL reserved character it contains should be
escaped using the %-encoding similarly to the semicolon
%3B in the example (the semicolon
is escaped because it collides with the default Clover file URL separator).
The SMB version 1 protocol is implemented in the JCIFS library which may be configured using Java system properties. See Setting Client Properties in JCIFS documentation for a list of all configurable properties.
The SMB version 2 and 3 protocol is implemented in the SMBJ library which depends on the Bouncy Castle library.
A sandbox resource, whether it is a shared, local or partitioned sandbox, is specified in a graph under the fileURL attributes as a so called sandbox URL like this:
where "data" is a code for sandbox and "path/to/file/file.dat" is the path to the resource from the sandbox root. A graph does not have to run on the node which has local access to the resource.