Universal Data Mover

Universal Data Mover (UDM) is managed file transfer component of Universal Agent that manages data in a secure and automated manner, allowing data to be transferred between any platforms in your environment and initiated from any platform.

These pages provide operating system-specific detailed technical information for Universal Data Mover:

Usage
Configuration Options
Command line syntax
Command references
Component Definition options
Universal Access Control List entries

The extensive integration capabilities of Universal Data Mover allow data to be pre- and post-processed.

Universal Data Mover exceeds current security and auditing requirements, including SOX, GLBA, and HIPAA. It supports the most modern security standards and methodology, including SSL/TLS encryption, X.509 certificates, and proxy certificates.

If there is a connection failure, Universal Data Mover ensures that all interrupted transfers resume without manual intervention. It integrates with your existing workload management solution to issue alerts if connections are not re-established after an acceptable time interval.

Components

Every Universal Data Mover transfer operation is comprised of three components: manager, primary server, and secondary server. The manager receives commands from the user through an interactive session and/or an external script file. It then establishes a transfer session, invoking the primary and secondary servers, which actually conduct the transfer operations. Data is transferred between the servers, with either able to act as the source in a transfer operation.

See Universal Data Mover Transfer Components.

Transfer Sessions

A transfer session can either be two-party or three-party:

In a two-party transfer session, the manager also serves as the primary server. Transfer operations occur between the manager/primary server and the secondary server.
In a three-party transfer session, the manager acts only as a control point for transfer operations, sending commands to the primary and secondary servers to be executed. Transfer operations take place between the two machines under which the primary and secondary servers are running.

See Universal Data Mover Transfer Sessions.

Universal Data Mover Transfer Components

There are three components to any UDM transfer operation:

Manager
Primary server
Secondary server

Manager

The UDM Manager processes commands using the UDM scripting language. The UDM Manager receives the commands from the user through an interactive session, an external script file, or some combination of the two. Before the UDM 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.

The manager may act as the primary server, depending on the type of transfer session: two-party or three-party (see Universal Data Mover Transfer Sessions). The secondary server is always a separate and distinct component invoked via the Universal Broker.

Primary Server

When a transfer session is being established, the UDM 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 UDM Manager, forwarding on any messages for the secondary server from the UDM 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.

Universal Data Mover Transfer Sessions

As discussed in Universal Data Mover Transfer Components, transfer operations take place within the context of a transfer session. A transfer operation is initiated once the UDM Manager has established a transfer session with the primary and secondary transfer servers. All subsequent transfer operations take place between the primary and secondary transfer servers.

UDM transfer sessions can be either two-party or three-party.

Logical Names

When a transfer session is established, the user gives each server (primary and secondary) a unique logical name. Commands addressed to a particular server reference this logical name.

Two-Party Transfer Sessions

For a two-party transfer session, the UDM Manager also acts as the primary transfer server, running in the directory - and under the user ID - under which the UDM Manager was launched. This means that the machine on which UDM Manager resides is the first endpoint of the transfer.

With a two-party transfer session, the secondary server is invoked by the UDM Manager / primary server via the Universal Broker. The second endpoint of the transfer session will be on the machine in which the secondary server was spawned. Transfer operations occur between the manager / primary server and the secondary server. (See the following figure.)

Three-Party Transfer Sessions

For a three-party transfer session, the UDM Manager acts solely as a control point for transfer operations, sending commands to the primary and secondary servers to be executed. Both the primary and secondary servers are spawned via the Universal Broker, and transfer operations take place between the two machines under which these servers are running. (See the following figure.)

Detailed Information

The following pages provide detailed information for Universal Data Mover:

Universal Data Mover Examples

See Transferring Files to and from Remote Systems - Examples for examples of how to implement Universal Data Mover.

See Universal Data Mover - Remote Execution for examples of how to implement remote execution via Universal Data Mover.

Browser not supported