Transfer Parameters
The following tables list the parameters used to add a new transfer.
For basic file transfers, you are required to configure the Required Transfer Information section.
| Parameter | Description |
|---|---|
| Client File Name | The full path name of the file on the client machine.
This is a suggested value that can be updated by the client when it initiates the transfer request. |
| Server File Name | The full path name of the file on the server.
The server could be Internet Server, an FTP server, an SSH server, an AS2 server, or Platform Server, depending on the server name associated with the transfer definition. |
| Directory Transfer | Defines whether this transfer definition is for a directory transfer or a single file transfer.
A transfer user can specify a directory and transfer all files and subdirectories from the directory at once. |
| Description | A brief description of the file. |
| Authorized User Id | The authorized user ID, which will be allowed to access this file. |
| Authorized Group Id | The authorized group ID, which will be allowed to access this file. |
| Server Name | The server associated with this transfer. |
| Transfer direction | The transfer direction.
If selecting Both, two transfer definitions will be generated. One is used for uploading and the other one is used for downloading. |
| Client Protocols Allowed | The protocol that is allowed for this transfer.
The default is ALL. |
| Department | The department to which this transfer belongs.
This parameter is only used with the delegated administration. |
| Virtual Alias | The mapping to the server file name specified in the transfer definition.
This alias is used when the client is FTP, SSH, or TIBCO MFT Platform Server. |
| Section | Description |
|---|---|
| Server Properties | This section defines default credentials for the server as well as default encryption (if supported). |
| Additional Transfer Properties | This section defines the Transfer Descriptions, Data Properties, Accessibility, Checkpoint Restart and Diagnostics subsections.
One of the more important parameters is Write Mode. The write mode allows you to define rules to determine if the file can be written to the server. For example, a write mode of Create will allow a transfer to complete only if the file does not exist on the server. This parameter is for upload transfers only. For a download transfer, the write mode of CreateReplace is always used. |
| Email Notification | This section allows you to send emails when a transfer definition is created, or when a file transfer is completed, either successfully or unsuccessfully. |
| Post Processing Actions | This section allows you to perform actions when a transfer is completed. |
| JMS Properties | This section defines values used when the transfer definition points to a server defined with server type of JMS.
These parameters are only used when reading from or writing to a JMS queue and are ignored for other server types. |
| z/OS Properties | This section is used only when creating a file on a z/OS system through an upload transfer request.
Unless the server defined in the Server Name parameter points to an FTP server or Platform Server running on a z/OS system, this section will be ignored. |
| UNIX Properties | This section is used only when creating a file on a UNIX system through an upload transfer request.
Unless the server defined in the Server Name parameter points to Platform Server running on UNIX, this section will be ignored. |
| HTTP Properties | This section is used only when performing a Form upload to a target HTTP server. |
| PGP Information | This section is defines the PGP information that can be associated with a transfer. |
| Client Permissions | This section is defines additional actions that can be taken by the FTP, SSH, and Desktop .NET clients.
These include: Allow Delete, Allow Rename, Allow Create Directory, Allow Remove Directory, Allow Client Transfer Mode, and Allow FTP Site Command Pass Through. |