Executes one or more shell commands defined by <command string>. For the list of available commands, refer to the command shell documentation. This argument is usually used together with --headless to run RCE in batch mode. Multiple commands can be chained within <command string> by separating them with " ; " (note the spaces); each command is completed before the next is started.

You can use the "stop" command at the end of the command sequence to shut down RCE after the other commands have been executed. However, any error during execution of these commands will cancel the sequence, and prevent the "stop" command from being executed. To ensure shut down at the end of the command sequence, use the --batch option instead of "--exec".

As an example, rce --headless --exec "wf run example.wf ; stop" will execute the "example.wf" workflow in headless mode and then shut down RCE. However, if the workflow fails to start, RCE will keep running, as the "stop" command is never executed. To attempt execution of the workflow file, but then always shut down regardless of the outcome, use rce --batch "wf run example.wf" instead.

Standard JVM arguments. This argument needs to be listed before any arguments intended to be passed to the JVM (i.e. arguments prefixed with -D), otherwise they will not be passed correctly. Also note that the JVM will receive these arguments appended to the ones specified in the rce.ini file (the file itself will not be modified).

Example: "rce.exe -vmargs -D<some-arg>=<some-value>"

Sets the local node id, overriding any stored value. This is mostly used for automated testing.

Sets the block size to use when uploading data to a remote node. This is useful for very slow connections (less than about 10 kb/s) to avoid timeouts. The default value is 262144 (256 kb).

Example: "-Dcommunication.uploadBlockSize=131072" - sets the upload block size to 128kb (half the normal size)