Validation - Script interpreter
- Nils Hondong
- Wette, Christian | OGiTiX
The interpreters can be stored for the individual script interpreter elements. To do this, select the appropriate interpreter from the Interpreter list box. The interpreters without a "64" in the name are the 32-bit versions. The following interpreters are available:
The CMD interpreter uses the cmd.exe of the configured IGA management server codepage.
Therefore special characters, returned values should be resolved correctly.
Note:
Special characters are read from the console output. As the code page of the server is used, this works for standard output such as echo. In the case of program output, the special characters may not be resolved. You should check this separately. If this problem occurs with program output via the CMD interpreter, please use the execute command.
The following interpreter options are available.
| Option | Description |
| /Q | Switches the command display off |
| /A | Output of internal commands to a pipe or file in ANSI format |
| /U | Output of internal commands to a pipe or file in UNICODE format |
| /E:ON | Activates command extensions |
| /E:OFF | Deactivates command extensions |
| /F:ON | Activates the addition of file and directory names |
| /F:OFF | Deactivates the addition of file and directory names |
| /V:ON | Activates delayed expansion of variables |
| /V:OFF | Deactivates delayed expansion of variables |
Configuration of the CMD interpreter
The CMD interpreter uses the 64-Bit version of the cmd.exe of the configured IGA management server codepage.
Therefore special characters, returned values should be resolved correctly.Note:
Special characters are read from the console output. As the code page of the server is used, this works for standard output such as echo. In the case of program output, the special characters may not be resolved. You should check this separately. If this problem occurs with program output via the CMD interpreter, please use the execute command.
The following interpreter options are available.
| Option | Description |
| /Q | Switches the command display off |
| /A | Output of internal commands to a pipe or file in ANSI format |
| /U | Output of internal commands to a pipe or file in UNICODE format |
| /E:ON | Activates command extensions |
| /E:OFF | Deactivates command extensions |
| /F:ON | Activates the addition of file and directory names |
| /F:OFF | Deactivates the addition of file and directory names |
| /V:ON | Activates delayed expansion of variables |
| /V:OFF | Deactivates delayed expansion of variables |
Configuration of the CMD64 Interpreters
The VBScript interpeter uses the cscript.exe of the IGA management server to run the vbscript.
The following interpreter options are available:
| Option | Description |
| //D | Enable active debugging |
| //E:engine | Use module to execute the script |
| //Job:xxx | Executes a WSF job |
| //T:nn | Timeout in seconds: Maximum time a script may run |
| //X | Executes the script in the debugger |
| //U | Use Unicode for redirected I/O operations from the console |
Configuration of the VBScript interpreter
The VBScript64 interpeter uses the 64-Bit version of the cscript.exe of the IGA management server to run the vbscript.
The following interpreter options are available:
| Option | Description |
| //D | Enable active debugging |
| //E:engine | Use module to execute the script |
| //Job:xxx | Executes a WSF job |
| //T:nn | Timeout in seconds: Maximum time a script may run |
| //X | Executes the script in the debugger |
| //U | Use Unicode for redirected I/O operations from the console |
Konfiguration des VBScript
The Powershell interpreter uses the Powershell version installed on the IGA Management Server.
You can use the interpreter option to load Powershell snap-ins and use the commands in the Powershell script.Note:
Powershell does not process script parameter.
Configuration of the Powershell interpeter
The Powershell64 interpreter uses the 64-Bit Powershell version installed on the IGA Management Server.
You can use the interpreter option to load Powershell snap-ins and use the commands in the Powershell script.Note:
Powershell does not process script parameter.
Configuration of the Powershell64 interpeter
The Perl interpreter uses the Active Perl version on the IGA Management Server. This is installed via the IGA setup.
The following interpreter options are available:
| Option | Description |
| -0[octal] | specify record separator (\0, if no argument) |
| -a | autosplit mode with -n or -p (splits $_ into @F) |
| -C[number/list] | enables the listed Unicode features |
| -c | check syntax only (runs BEGIN and CHECK blocks) |
| -d[:debugger] | run program under debugger |
| -D[number/list] | set debugging flags (argument is a bit mask or alphabets) |
| -e program | one line of program (several -e's allowed, omit programfile) |
| -E program | like -e, but enables all optional features |
| -f | don't do $sitelib/sitecustomize.pl at startup |
| -F/pattern/ | split() pattern for -a switch (//'s are optional) |
| -i[extension] | edit <> files in place (makes backup if extension supplied) |
| -Idirectory | specify @INC/#include directory (several -I's allowed) |
| -l[octal] | enable line ending processing, specifies line terminator |
| -[mM][-]module | execute "use/no module..." before executing program |
| -n | assume "while (<>) { ... }" loop around program |
| -p | assume loop like -n but print line also, like sed |
| -P | run program through C preprocessor before compilation |
| -s | enable rudimentary parsing for switches after programfile |
| -S | look for programfile using PATH environment variable |
| -t | enable tainting warnings |
| -T | enable tainting checks |
| -u | dump core after parsing program |
| -U | allow unsafe operations |
| -w | enable many useful warnings (RECOMMENDED) |
| -W | enable all warnings |
| -x[directory] | strip off text before #!perl line and perhaps cd to directory |
| -X | disable all warnings |
Configuration of the Perl interpreter
The SSH interpreter uses PUTTY PLink to establish connections to remote systems via the SSH protocol.
The SSH server on which the script is to be executed must be specified in the interpreter options.
The following interpreter options are available:
| Option | Description |
| -v | show verbose messages |
| -raw | force use of a particular protocol |
| -P port | connect to specified port |
| -X -x | enable / disable X11 forwarding |
| -A -a | enable / disable agent forwarding |
| -t -T | enable / disable pty allocation |
| -1 -2 | force use of particular protocol version |
| -4 -6 | force use of IPv4 or IPv6 |
| -C | enable compression |
| -noagent | disable use of Pageant |
| -agent | enable use of Pageant |
Configuration of the SSH interpreter
The Telnet interpreter uses PUTTY PLink to establish connections to remote systems via Telnet protocol.
The Telnet server on which the script is to be executed must be specified in the interpreter options.
The following interpreter options are available:
| Option | Description |
| -v | show verbose messages |
| -raw | force use of a particular protocol |
| -P port | connect to specified port |
Configuration of the Telnet interpreter
Configuration of script interpreter
Under Display name, you specify the name with which the job is displayed in the module.
Under Interpreter options, you can enter the server name for ssh and telnet, for example, and also specify parameters for the script.
Next to User type, select under which user account, i.e. with which rights, this job is executed. See also the Configuration chapter.
You can also specify a working directory for the script.
The actual script is displayed and edited in the text field. The content is parsed, i.e. the unimate variables contained in the script are resolved and replaced with the corresponding values. The script is then executed via the assigned management server. This means that the scripts that a company normally uses can be used here without any changes or adjustments.
Script fields