| Panel | |
|---|---|
|
...
Managed File Transfer operations are handled as file transfer requests that are registered in the system.
A transfer request record is created either when there is a download or an upload initiated by a partner client that is connected to a local UDMG server Server or when a UDMG client Client is triggering a request on the interfaces: CLI, REST API, UAC UDMG File transfer task (see GET a file from an SFTP server). Usually, a transfer request is associated with a single file, where the filename is provided by the client and the path is determined by the transfer rule determines the path.
A wildcard transfer is a special kind of transfer that can include a wildcard in the file name parameter, it is possible to request the upload or download of multiple files towards a remote partner with this wildcard mode.
...
Source file specifications, not destination file specifications. (Under some operating systems, it is possible for * and ? to be valid characters in a file name. If they appear in a destination file, they are treated as file characters, not as wildcards.)
The file name portion of file specifications , and not as part of the directory.
Types of Wildcards
...
Example of a command line with the UDMG client Client to fetch the files matching the pattern “wince*.png” from the remote partner “rebex” (see Tutorial - Download Multiple Files with Wildcard Mode)Creating a PeSIT Partner).
| Panel |
|---|
|
...
| Panel |
|---|
|
The result is the creation of a transfer record with the wildcard pattern, which executes as followfollows:
Step 1 | Connect to the remote partner. |
|---|---|
| Step 2 | List the files that are matching with the pattern on the remote path. |
| Step 3 | Create a child transfer record for each of the files. |
...
The transfer is set to planned status and is independent |
...
of the parent request. |
...
| Step 4 | Terminate and keep the list of files and child requests in its transfer info metadata. |
|---|---|
| Step 5 | Additionally, the file size field is set to the number of matched files (and child requests). |
| Step 6 | The child requests are processed independently |
...
of the parent request and can be paused, resumed, or |
...
canceled on their own. |
In this example, the transfer with ID 160 is the parent request, with the wildcard pattern, while 161 and 162 are the children requests for the 2 matching files: 'winceclient.png' and 'winceclientSmall.png'.
...