File Deploy Job - Advanced Options

The Advanced Options panel lets you customize a File Deploy Job using pre-commands and post-commands.

Pre- and post-commands allow you to execute commands on a target directory before a job begins or after a job ends. A pre- or post-command can consist of any number of commands that can be executed by the native operating system of a remote host.

After you define pre- and post-commands, they are saved to the file server as script files. When a job runs, it uses the nexec -e command to execute the pre- and post-commands. When you execute a pre-command, the target directory is first created (if it does not already exist) and then the pre-command is executed in the target directory. Post-commands are executed in the target directory.

You can create pre- and post-commands by entering commands in the text box or importing text from a file on any managed server.

If necessary, click Zoom to open a dialog box that gives you a larger text box to edit pre- and post-commands. When you finish editing the command, click OK.

Field definitions

Pre-command

Enter the command that you want to execute before the job begins. To import the text of the command, click Browse and navigate to the file containing that text.
If a precommand must execute successfully for the job to complete, check Must have 0 exit status. This option is not available when undoing the deployment of a BLPackage or installable software package.

Post-command

Enter the command that you want to execute after the job ends. Postcommands are executed in the target directory. To import the text of the command, click Browse and navigate to the file containing that text.

Minimum disk free

To specify a minimum amount of disk space for a destination directory, enter a value (in kb) for Minimum disk free.

Where to go from here

File Deploy Job - Default Notifications

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

Comments