Remote Execution via UDM

Remote execution refers to the ability of initiating work from one system (the local system), which executes on another system (the remote system). The type of work executed on the remote system consists of most any type of work that the remote system supports, such as commands and scripts. The Universal Command component of Universal Agent is used to execute work on the remote system.

These pages provide information on the remote execution features and functionality of the Universal Data Mover business solution.

Universal Data Mover provides access to Universal Command remote execution via the Universal Data Mover exec command. The exec command invokes the Universal Command Manager and provides parameters for passing a subset of the Universal Command Manager options.

The exec command executes system commands on remote machines if you have Universal Command (UCMD) Manager on the same system with the UDM Manager.

Remote Execution Components

Universal Data Mover Remote Execution using Universal Command consists primarily of two Universal Agent components:

1. Universal Command Manager runs on the local system. The Manager initiates the work on the remote system.
2. Universal Command Server runs on the remote systems. It executes work on behalf of a Universal Command Manager.

The Manager provides the information to the Server necessary for the Server to execute the work. This includes the command or script that defines the work, as well as the user identifier with which the work should execute. The Server authenticates the user identifier on the remote server. If the user identifier authenticates successfully, the Server executes the work with the provided user identifier.

Once the work is started, the Manager supplies input files to, and receives output files from, the remote command Server in real-time. All files with character data are translated to the appropriate code pages for the respective system. The transmitted data, optionally, can be compressed, encrypted, or authenticated.

The Manager runs as long as the remote work is running. When the remote work ends, the Manager ends. The exit code of the remote work is used as the exit code of the Manager. With standard out and standard error as well as the exit status of the remote work available from the manager, there is no need for access to or expertise on the remote operating system.