User Guide > Objects > Alphabetical Listing > FileTransfer - Execution

File Transfer - Execution

Object-Type Specific Features

Exchanging data between different system platforms requires the character sets to be converted. This is automatically done using CodeTable objects. The transfer can be structured, thereby enabling the exchange of files with packed and binary fields in heterogeneous system environments. All network transfers are encoded by default.

For each file transfer, a separate connection is established between the agents. agents for the operating systems OS/400, Windows, Unix, z/OS,and NSK handle file transfers through extra threads. As soon as a file transfer has ended, the corresponding connection is automatically closed. If there are still open and unused connections, they are closed after the period of time that is defined in the key FT_CONNECTION_TIMEOUT (variable:UC_HOSTCHAR_DEFAULT).

The old file transfer protocol is used if one or both of the affected agents use Automation Engine version 8.00A or earlier. In this case, only one connection is established between the agents for all file transfers. The system checks if a connection has already been established between the two agents before a file transfer starts. If so, this connection is used and no attempt is made to establish a separate connection. After the file transfer has ended, the system ensures that a connection that is still used is not closed.

No error message is supplied if empty files are transferred (Windows and UNIX).

Note that problems can occur in file transfers when the Windows agent starts from a UNC path because you mapped files (StatusStore) cannot be used (the agent can crash, for example). Automic recommends starting the agent either from a local directory or specifying an absolute local directory in the agent variable UC_EX_PATH_TEMP in the agent's INI file.

File transfer optimization: You can specify parameters for the size of the TCP/IP buffer in some agents. The administrator can do so in the relevant INI file's [TCP/IP] section.

Transferring Files

Each file transfer is started by establishing a connection between the source and destination Execution. The file can be transferred as soon as a connection can be established. There are two methods of transferring files:

With a temporary file:

The file that should be transferred obtains a specific name in the destination system. This name is composed of the letter "T" and a 7-digit alphabetic string (such as TAAFLEFM). The string is based on the file transfer's RunID which ensures that the file name is unique. Also refer to the documentation about script functionsRUNNR2ALPHA and ALPHA2RUNNR.
In the new FT protocol, a separator and a file ID are appended in addition to the string. Doing so makes a distinction possible because all files are handled via the file transfer task's RunID.

The file obtains the name specified in the FileTransfer object after a successful transfer.

The temporary file is created in the file transfer's destination directory.
Without a temporary file:

The file that should be transferred obtains the name that is specified in the FileTransfer object in the beginning.

The method that should be used depends on the specifications that the administrator has made in the destination agent's INI-file parameter ft_temp_file=.

A temporary file is not created if an existing file is extended or overwritten. Contents are directly inserted in the relevant files.

The huge advantage of temporary files lies in the simplified handling of further processing because the files only obtain their specified names after they have successfully been transferred.

If an error occurs, the temporary file is deleted in the destination system. Files that could not completely be transferred are not removed on UNIX and Windows computers. Therefore, the agent does not have to newly start the file transfer if thefile transfer is restarted.

Temporary Files On the Source Agent's File Structure

Each time an source agent does a file transfer, it produces two temporary files; a status store file with .sts extension and a file transfer report with a .ftx extension. The location of these files is determined by the UC_EX_PATH_JOBREPORT variable set in the [VARIABLES] section of the agent's .ini configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. file. The agent uses these files to reconstruct the file transfer if the agent is restarted or if a transfer fails. When the file transfer completes successfully, the files are automatically deleted. If the file transfer fails to make a restart, the files remain on the file system. The number of days the status files remain is determined by the value of the FT_RESTARTINFO_LIFETIME key in the UC_HOSTCHAR_DEFAULT variable.

Agent Groups

An agent group can either be used as the source or as the target. This results in two possible ways of usage:

File transfers from a single host to many target hosts.
File transfers from many hosts to a single target host.

Pay particular attention to the latter one as the files must not have the same name. Otherwise, the file transfer overwrites the files or it cannot transfer the file if it is being deployed by parallel processes at that point in time. Insert the following variable in the target file name: &<FT_SRC_HOST>. The file transfer replaces this variable with the name of the file's original host.

For example:

C:\temp\&<FT_SRC_HOST>_test*.txt

Note that agent groups cannot be selected in file transfers as a source and a target at the same time!

Compression

Files can also be transferred in compressed form. You can activate this option in the FileTransfer tab.

If you select the compression type "Default value" in the file transfer, the system uses the value that the administrator has defined in the variable UC_HOSTCHAR_DEFAULT, setting FT_COMPRESS. The files are transferred in compressed mode if the two agents have different settings.

Example:

WIN01 = No compression
UNIX01 = Active compression

The files are transferred in compressed form.

The agent uses the LZP+Huffman procedure for the compression.

When using compression, make sure that effort (time required for compression) and benefit (gain of time because of reduced transfer time) are balanced against each other. An important component for your decision is the available bandwidth of your network connection. You cannot increase performance with fast networks (100 Mbit)because the compression process is more time-consuming than the gain achieved by reducing the network time. With an available bandwidth of 10MBit or less, compression will definitely result in a performance increase.

End Status

Transferring a particular file:

A file transfer obtains the status ENDED_NOT_OK if the relevant file is not available.

Use case: A file transfer is to transfer a particular file which should then further be processed.

Transferring files using wildcard characters:

A file transfer obtains the status ENDED_EMPTY if no file is available which complies with the filter specifications. It obtains the status ENDED_OK if at least one matching file is found.

Use case: A file transfer is to transfer several files whose naming convention follows a particular pattern . The focus is on file names and not on the number of files.

UNIX and MPE

The administrator can use the parameter login_check=yes to specify in the INI files of the UNIX and MPE agents that the Login object's passwordA secret combination of characters for a Automation Engine user. is checked. For reasons of security Automic recommends using this setting. Login_check=no only checks the user nameName of the Automation Engine user..

VMS

In VMS, each text file requires a delimiter to be appended. The administrator can define in the INI-file parameter FileEndDelimiter= whether the VMS agent should append one.