The intention of the Command Task is to run binary executables on the execution system. An executable is implicitly transferred from its original location into the Uspace before getting executed (if not specified via a Software Resource).
ATTENTION: In general, running a script in the Command Task is unsupported and insecure. It may fail for several reasons:
If the script does not contain a request for a shell, some script commands may be invalid in the standard execution shell on the remote system (currently the Bourne shell).
Scripts generated on client Windows systems will not run on the Unix execution systems. As any other "executable" the script is transferred to the Uspace before getting executed. Because the client assumes a binary executable, the Windows' end-of-line characters in the script are not handled appropriate in the transfer.
There are two approaches to specify an executable in the Command Task which are explained in the following. All other settings in the sub-panels Options, File Imports, and File Exports can be applied accordingly to the Script Task
If not specified via a Software Resource, the executable is defined in the Command field which can be edited after selecting the Command radio button. It may be entered either directly or by local/remote browsing of the file systems. Without browsing the location of the executable has to be specified by a proper selection in the Location combo box.
Executables of general interest on the execution system may be specified as a Software Resource in the NJS server configuration. These Software Resources can be selected directly in the Location combo box after selecting the Software Resource radio button.