VW
Hi, we just upgraded to Aris 10. In the documentation I cannot find how to reconfigure the business server's components to start automatically when the windows service starts. The Cloud Controller command for reconfiguring this in v9.6 does not have any effect in v10.
Anybody knows the reconfigure command parameters or where this is documented for v10?
Hi,
you are looking for the autostart.mode parameter.
This is a node setting valid for all runnables at a node.
Example for one node:
set autostart.mode = "all"
Example for all nodes:
on all nodes set autostart.mode="all"
Do not use the autostart setting for each runnable
This is the requested documentation part.
Runnable autostart
So far, the agent had only a very simple autostart feature. By setting the agent config parameter "restart.stopped.runnables.on.agent.start" to true, after being started, the agent would restart every configured runnable that it finds in STOPPED state. The runnables would be started in the order in which they were configured, and the agent would wait for the time in milliseconds set with the "wait.for.predecessor.runnables.on.agent.start" parameter for each runnable to reach STARTED state before proceeding.
In conjunction with our new workaround for the launch order dependency problem of our applications, we also rolled out a new improved autostart mechanism.
It can be controlled by a new agent configuration parameter "autostart.mode", which can have four different values:
· off : nothing is started automatically
· autostart.flag : only those runnables which have their "autostart" set to true (by invoking the new "set runnable property" command TODO link to description) are started automatically
· last.started: only those runnables that were started the last time (i.e., all runnables for which an explicit "start" command had been issued, without being followed by an explicit "stop" or "kill" command) are started automatically
· all : starts all runnable automatically
In general, autostart will become active when the agent starts up, but only if
a) autostart.mode is set to "all", "autostart.flag", or "last.started" (you might have guessed that... )
b) the agent finds ALL runnables to be either STOPPED or UNKNOWN after starting up. This prevents the agent from starting up stuff it the agent itself (but not the entire node) is manually restarted and the runnables themselves are still active.
Regards
Patrik
