Supported Script Languages

WSH is language-independent for WSH-compliant scripting engines. Natively, the Windows platform supports Visual Basic Scripts, with file extension .vbs, and scripts written in the Java Script language, with file extension .js.

For other scripting languages, a dedicated script interpreter must be installed on the execution server. For example, if you install a Perl interpreter on an execution server, this will register a Perl scripting engine at the WSH environment for the extension .pls. Whenever a file with extension .pls is passed to the WSH tool, with the executable cscript.exe, it will invoke the appropriate interpreter because of the file extension. So the client of WSH, in this case the Silk Central Execution Server, does not need to know about the installation of the Perl interpreter.

Note: After installing a script interpreter, for example Active Perl, try to execute a script locally on the execution server by calling the WSH command line tool with a sample script before executing the script in Silk Central. To do so, open a command shell on the execution server and type cscript <somescript>, where <somescript> is the path to a script of your choice that is available on your execution server. This is exactly what Silk Central will call when executing a WSH test on an execution server. If the script is executed, then the scripting engine has been registered successfully.
The following scripting languages are WSH compatible:
Scripting Language
File Extension
.py, .pyw