Running Scripts - How the Server and Agent Resolve Script Names

The server component processes requests for both UNIX and Windows agents. When associating and running scripts with triggered and scheduled actions, the server resolves the names of those scripts based on the following:

1. the OS under which an agent is running

2. how the script name is specified on the Specify Script window (this window appears when you select Run Script from an Alert page on a job definition window)

Agent and Operating System

The operating system under which an agent runs determines the scripts that can be run by that agent:

• UNIX. An agent running under a UNIX operating system will not run or receive (from the server) scripts that have an extension. UNIX agents only accept and run script files that do not contain an extension within their name. The first line in a script file determines what UNIX interpreter is needed to run the script.
• Windows. An agent running under a Windows operating system will only run or receive (from the server) scripts that have an extension. The extension of a script file determines what interpreter is needed to run the script.

Specifying a Script Name

Use the Specify Script window when associating a script with a triggered or scheduled action. The Specify Script window appears when you select Run Script from an Alert page on a job definition window. Enter the name of a script on the Script Name field to associate that script with the action you want to perform. The name of the script you enter might or might not contain an extension (including an extension is optional). Depending on the agent that receives the script, the following occurs after a triggered or scheduled action that contains a script is run:

• UNIX agent. If the specified script name contains an extension, the agent ignores the extension and searches for a file of the same name (without an extension). For example, if you enter backup.vbs in the Script Name field, a UNIX agent will search for a file with the name backup . If the script exists, Unix will read the first line of the script and use the appropriate interpreter to run the script. If the file does not exist, the triggered or scheduled action will not run the script.
• Windows agent. If the specified script name contains an extension, the agent will search for a file of the same name/extension. For example, if you enter backup.vbs in the Script Name field, a Windows agent will search for a file with the name backup.vbs . If the script does exist, the Windows agent will determine what interpreter is needed to run the script based on its extension. If the file does not exist, the triggered or scheduled action will not run the script.

If the specified script name does not contain an extension, a Windows agent will look for the file name in the following order (based on its extension): .com, .exe,.bat,.cmd,.vbs,.vbe,.js,.jse

Aperi Storage Manager's process for resolving script names enables you to run scripts with the same name across multiple operating systems. To run a script on both a UNIX and Windows operating systems, you must have two versions of that file on either the server or the agent. For example, if you want to run a provisioning script against a UNIX and Windows agent, you must have two versions of that file (bat and provision ) stored in the \scripts directory on either the server or agent.