File Deploy Job - General

The General panel lets you provide information that identifies a File Deploy Job. It also lets you identify the source and destination of the files copied in a File Deploy job.

Field definitions


Identifying name.


Optional descriptive text.

Save in

Folder in which to store the object.


Use the Source list to identify the files and directories you want to deploy. The files and directories you specify appear in the Source list. To specify additional files and directories, do any of the following:

  • Click Browse and use the Select Source Files dialog box to select a file or directory.
  • Click Add and use the Add Source File dialog box to provide a path to a file or directory.
  • To delete an entry from the list of files or directories being deployed, select the entry and click Delete .

Preserve source file paths

To preserve source file paths, check Preserve source file paths.
Checking this option means that each file or directory you are deploying has the same relative path on the destination machine as it has on the source machine. For example, when you are copying the file /etc/hosts, the hosts file is copied to the path /etc/hosts rather than being copied to a directory that you specify. Preserving source file paths is an easy way to synchronize file systems, especially when you are moving multiple files that need to reside in various locations.


For Destination, enter the path of the location to which you want to copy files or directories. You can type a path or click Browse to select a destination.

If you checked Preserve source file paths in the previous step, you should probably enter / for Destination. Specifying a destination other than / means that the system preserves the paths of the files and directories you are deploying and recreates those paths relative to the destination directory you specify. For example, if you are copying /etc/hosts and your destination directory is /tmp, the hosts file is copied to /tmp/etc/hosts.

Number of targets to process in parallel

Choose one of the following options:

  • Unlimited — Simultaneously runs the job on as many servers as possible. Application Server settings control the number of targets the job can access.
  • Limited — Specifies the maximum number of targets on which the job can run simultaneously. Limiting the number of targets is useful when a job might temporarily disrupt the functionality of a target server, and you want to limit that disruption to a small fraction of your managed servers.
    If you want the job processed serially at the target servers, set this value to 1. Note, however, that although this is the best approach for achieving serial processing, it does not always guarantee full serial processing at all targets; the first two or three targets might still run in parallel.

Set execution override

Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

Clear execution override

Remove an existing execution override.

Where to go from here

File Deploy Job - Targets

Was this page helpful? Yes No Submitting... Thank you