Running server-side scripts

You can create scheduled tasks to run:

system-level scripts—for example, Windows batch, Perl, VBScript, and AppleScript
FileMaker scripts in databases hosted by FileMaker Server
script sequences that combine a FileMaker script with an optional pre-processing system-level script and an optional post-processing system-level script

System-level scripts

Script files must be placed in the Scripts folder on the primary machine in your FileMaker Server deployment. To schedule a system-level script to run, create a scheduled script and specify the type System Script. Next, select the script file you want to run.

System-level scripts can perform operating system level tasks on the primary machine.

FileMaker scripts

To schedule a FileMaker script to run, create a scheduled script and specify the type FileMaker Script. Next, select the database that contains the script you want to run, then the script.

FileMaker scripts can do simple or complex tasks. For example, you can write a FileMaker script to remove duplicate records or to validate the format of phone numbers. You can schedule these scripts to run during off hours, perhaps before a daily backup.

Scripts can incorporate conditional decisions (if-else statements) and perform repetitive tasks (loop statements). Use the Script Workspace in FileMaker Pro to build scripts by selecting from a list of supported FileMaker Pro commands, called script steps, and specifying options (if necessary).

To find out if a FileMaker script step is supported from a FileMaker Server schedule, choose Server for Show Compatibility in the Script Workspace. See the script step reference in FileMaker Pro Help.

Script sequences

To create a script sequence, create a scheduled script and specify the type Script Sequence. Next, select the database that contains the FileMaker script you want to run, then the script. Next, select an optional pre-processing system-level script, an optional post-processing system-level script, or both.