Transferring Files to and from Remote Systems

Universal Data Mover's file transfer solution, developed specifically for corporate IT infrastructures and automated data center environments, makes transferring data between various enterprise and desktop platforms reliable and easy.

These pages describe the framework in which transfers are made, and provides examples of file transfers from all supported operating systems.

Transfer Operation Components

There are three components to any Universal Data Mover transfer operation:

1. Manager
2. Primary server
3. Secondary server

The Manager can act as the primary server, depending on the type of transfer session: two-party or three-party (see Transfer Sessions).

The secondary server is always a separate and distinct component invoked via the Universal Broker.

Manager

The Universal Data Mover Manager processes commands using Universal Data Mover's scripting language. The Manager receives commands from the user through an interactive session, an external script file, or some combination of the two. Before the Manager can initiate any transfer operations, it must first establish a transfer session where it invokes the primary and secondary servers, which actually conduct the transfer operations.

Primary Server

When a transfer session is being established, the Universal Data Mover Manager invokes the primary server, which acts as the first endpoint in a transfer operation. In turn, the primary server invokes the secondary server, providing a single path of communication. The primary server also acts as a relay for the Manager, forwarding on any messages for the secondary server from the Manager. This single message pipeline reduces the number of connections needed for three-party transfers (see Three-Party Transfer Sessions).

Secondary Server

The secondary server acts as the second endpoint in a transfer operation. Data is transferred between primary and secondary servers, with either endpoint able to act as the source in a transfer operation.