External Script

Note The External Script transformation does not function with repository encryption.

The External Script transformation step enables adding the execution of external script as part of a route. To add an External Script transformation step to a Route Package Template take the following steps:

  1. Determine whether or not to proceed with route execution on step failure.
  2. Select the external script path.
  3. Determine whether or not to log the external script's standard output to the server log.
Note Step 2 is mandatory. All other steps are optional.

The following topics provide configuration details for the External Script transformation step:

Related topics:

Proceed with route execution on step failure

If Proceed with route execution on step failure is checked, the route execution continues even if the step execution fails.

Script Settings

The script settings consist of the selecting the external script path.

External script path

The external script path is an absolute path to external script.

Example script expressions:

  • For *nix environment:

    /usr/bin/env bash -c ${FILEDRIVEHOME}/bin/agents/example.sh

  • For Windows environment:

    cmd /c ${FILEDRIVEHOME}\bin\agents\example.bat

Logging Settings

The logging settings consists of determining whether or not the external script's standard output is logged to the server log.

Log script's standard output to Server log

If Log script's standard output to Server log is selected, the external script's standard output is logged to the server log.

Related Links