Using the autostart.mode parameter, you can reconfigure runnables to start automatically when the windows service starts. This parameter is used as a node setting valid for all runnables at a node. Do not use the autostart.mode parameter for runnables. For runnables use the set runnable property command to set their autostart parameter to true. If you do not want a runnable to be started, you must deactivate it.
Procedure
To change settings for one node, enter for example:
set autostart.mode="all"
To change settings for all nodes, enter for example:
on all nodes set autostart.mode="all"
You can use the following values:
all: starts all runnable automatically.
off: no runnable is started automatically.
autostart.flag: only those runnables which have their autostart set to true (by invoking the set runnable property command) are started automatically.
last.started: only those runnables that were started the last time are started automatically. These are all runnables for which an explicit start command had been issued, without being followed by an explicit stop or kill command.
Runnables are started automatically when ARIS agent starts up, but only if the autostart.mode is set to all, autostart.flag, or last.started or if ARIS agent finds all runnables to be either in state STOPPED or UNKNOWN after starting up. This prevents ARIS agent from starting up runnables if ARIS agent itself but not the entire node is manually restarted and the runnables themselves are still active.