Overview

A single process indicates that a built-in script or custom script should be run by itself, against each file or against all files retrieved during a single traditional task run. (Synchronization tasks cannot run processes.) There are two types of scripts: built-in and custom.

Built-in scripts are installed and updated along with MOVEit Automation, and their source code may not be viewed or altered. A complete list of built-in scripts available in this version is available in the Processes/Scripts - Built-In Overview, but examples of built-in script functions include PGP encryption/decryption, advanced ZIP, find-and-replace operations and invocation of command-line applications.

Custom scripts are just that: they are VBScript scripts written by you or imported from the directory of sample scripts installed with MOVEit Automation Admin. (Custom scripts are available only in the MOVEit Automation Enterprise.) The source code of any custom script may be viewed or changed at any time, as long the user who wants to view or change the code has been properly authenticated through MOVEit Automation Admin. (Custom scripts are stored encrypted in the MOVEit Automation configuration file so a hacker who gains access to the MOVEit Automation hard drive cannot alter processes.)

Built-in scripts are available automatically as soon as you install MOVEit Automation. By contrast, to use a custom script, you must load it into MOVEit Automation. A custom script is loaded into MOVEit Automation when an administrator selects a VBScript source code file (*.vbs) and associates a "friendly name" with this script. Once loaded, the original script file is no longer used and can be deleted. (If changes to the script need to be made, an administrator can retrieve a copy of the saved script using MOVEit Automation Admin, make changes and reload the script back into MOVEit Automation.)

When defining a process, you choose these options:

• Which script to use
• When to run the script. Your choices are:
  • One time, after all files have been downloaded from Sources and before any files have been uploaded to Destinations.
  • Per file, immediately before each file is uploaded. If no sources are defined for the task, "per-file" processes are run once.
• Which task parameters to use (if any), and their values. This is optional; not all tasks require task parameters.

See Configuring Tasks - Tasks Elements - Process.

A script can call any function defined by VBScript. It can also instantiate and invoke COM objects, such as the useful "Scripting.FileSystemObject" and command-line applications using the "MIRunCommand" function. In addition, there are several MOVEit Automation-specific functions that allow you integrate seamlessly with MOVEit Automation cache files and make your own task log entries.