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.

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)

The "--local" option only lists components provided by the local node.

The "--as-table" option formats the output as a table that is especially suited for automated parsing.

The <component id> needs to be defined as listed by the "components list" command, e.g. "rce/Parametric Study", "common/MyIntegratedTool", or "cpacs/MyCpacsTool". This id must be enclosed in double quotes if it contains spaces.

Sends an email to the specified recipient.

Short form of "net info".

-g name of the group in which the workflow will be shown in the Palette on the client instance

-k (keep execution data): if set, the workflow execution data will not be deleted after the workflow is run

-t (temporary/transient): if set, the workflow is automatically unpublished when the RCE instance is shut down

-p: adds a placeholder file for the given workflow; see the "wf run" command's documentation for details. This operation verifies that the workflow contains the required standard elements before publishing.

Note that a snapshot of the workflow file (and optionally, the given placeholder file) is taken before publishing; subsequent changes of the workflow file do NOT affect the published workflow.

Available operations: avgcpu+ram <time span> <time limit> - fetches the average CPU load over the given time span and the current free RAM.

Operation parameters: time span - the maximum time span (in seconds) to aggregate load data over time limit - the maximum time (in milliseconds) to wait for each node's load data response.

Executes the given workflow file and waits until it has completed. Workflow file paths containing spaces must be enclosed in double quotes ("...").

The "--delete" option defines the deletion behavior after workflow completion. Deleting a workflow deletes all of its files in the data management and releases certain resources that may or may not be used after it has finished, for example data to be visualized in component's runtime views. The default of this setting is "onfinished": The workflow is deleted if it terminates in state "Finished" (which means normal completion without errors), otherwise it is left unchanged for inspection.

The "--dispose" option defines the deletion behavior from the workflow list. Disposing a workflow does not delete its data from the data management. The default of this setting is "onfinished".

The "--compact-output" option reduces this command's output as much as possible, which is intended to simplify scripted calls of this command. The first line printed will either be the workflow's assigned id if the start was successful, or a text starting with "Error " if the workflow could not be started. If (and only if) the start was successful, a second line will be printed once the workflow has terminated. The pattern of this second line is "<workflow id>: <final state>".

The "-p" option can be used to define a placeholder value file (see below).

The "--pr" option defines how often the workflow is started in parallel. The "--sr" options defines how often the workflow is started in serial. E.g. "--pr 5 --sr 3" starts the workflow three times with five in parallel. If "*" is used with the "--basedir" option or multiple workflow filenames are passed, "--pr" and "--sr" are applied for each of the workflows.

For the "--delete", "dispose" and "-p" options refer to "wf run" above.

The "--basedir <directory>" parameter specifies the directory containing the workflow files. File paths containing spaces must be enclosed in double quotes ("...").

The second parameter defines the workflow's filenames. Using "*" as workflow file runs all non-backup workflows in the basedir. Workflow file paths containing spaces must be enclosed in double quotes ("...").