Commands are executed as it would be from the system command line (so Windows rules on a Windows host, and Linux rules on a Linux system). These commands are executed on the Identity Validator 2.0 server.
Executing commands on Windows:
If the command is a Windows executable, you simply call it using the full path.
Example: C:\Windows\System32\write.
If the command is a batch file, or if the command is a command processor (cmd.exe) built-in command such as dir, copy, etc., you need to use the following syntax:
cmd /c <command>
Example: cmd /c dir c:\
Executing commands on Linux or Mac:
For Linux and Mac, you enter the command exactly as you would at the command-line.
There are some issues observed with the commands. Although the Execute Connector Documentation says: the command is executed as it would be from the local system command line, that is only 90% accurate. The back end engine runs in a JVM (Java Virtual Machine), meaning, like all Java, the engine is in it’s own machine and OS (JVM truly means Java Virtual Machine). Java has limited access to the host OS. The normal shell command-line such as piping(|), redirection(>), spaces in names, and memory between command do not work.
If your command do not work:
Make sure the command works on the command line on the Identity Validator server.
Make sure the command doesn’t need a specific current directory, or you may need to write a script to perform a CD and execute the command.
Put the command results in a variable, and read it for any error message.
Put the command in a shell or batch file. Then it should behave exactly like the command line because it is loading the shell.