About Command Execution

Administer Operator Categories and Custom Operator Groups › Configuring Operator Categories › About Command Execution

About Command Execution

Command Execution operators let you run shell scripts or executable programs on any agent or Orchestrator. This category provides data and resource access to network devices that support the Telnet and SSH (Secure Shell) interface protocols.

The list of operators follows:

Run Program
Run Script
Run SSH Command
Run SSH Script
Run Telnet Command
Run Telnet Script

If you are running scripts, follow the Windows or UNIX operating system conventions to make them executable. In CA Process Automation, scripts return result as CA Process Automation dataset variables.

For UNIX systems, the first line of the script specifies the full path to the desired interpreter. For example:
```
#!/bin/sh
```
Specifies to execute using sh, the Bourne shell on systems such as Oracle Solaris. On Linux systems, this entry is a link to another shell, such as bash. A Script operator can execute any script for which the target host has an interpreter.

Wrap Shell commands such as cp or dir in an executable script file.
```
#!/usr/bin/perl
```
When placed at the top of a Perl script, tells the web server where to find the Perl executable.
For Windows systems, the filename extension defines the scripting interpreter. For Windows, define file associations to run the scripts automatically. The following extensions are supported:
```
*.ps1
```
A Windows PowerShell file.
```
*.exe
```
An executable file that installs and runs programs and routines.
```
*.cmd
```
A batch file that is composed of a sequence of commands; similar to a .BAT file, but run by the CMD.exe program rather than the COMMAND.com program.
```
*.vbs
```
VBScript file.
```
*.wsh
```
A Windows Script Host text file with parameters for a script such as a .vbs file; requires Microsoft WScript or Microsoft CScript to open the file.

More information:

Configure Command Execution: Default Telnet Properties