ACC Command

Dear Jordan,

When your ARIS is in autostart mode, then you could use restart agent after stopping all runnables. That command restarts ARIS Agent (Windows service) which then looks up the autostart mode.

You can check the autostart mode via  the ACC command get autostart.mode. Gettign the response value "Off" would not start up the ARIS runnables when ARIS Agent restarts. But an "All" would restart your ARIS stack.

A few more ACC commands might useful for you, such as restart runnable loadbalancer_m. That stops a runnable and restarts it in one step. It replaces the following longer command sequence:
stop loadbalancer_m
wait for stopped loadbalancer_m
start loadbalancer_m

Another helpful ACC command is already used above wait for... which I am using quite often. It helps me to send a sequence of ACC commands which require a certain status of a runnable, e.g. either STOPPED or STARTED. The wait command waits for the runnable to reach the requested state, and only after that then next ACC command is processed.

The following example stops all runnables, waits until the last/first runnable (Zookeeper) has stopped, too, then restarts ARIS Agent, then waits for the last runnable being started which is loadbalancer_m, and then lists all runnables.
stopall
wait for stopped zoo_m
restart agent
wait for started loadbalancer_m
list

Cheers
Runè

Nice, restart agent was news to me. You can refine this procedure into a one click "Restart ARIS" link on Windows.

1. Create an ACC command list file ACC_commands.txt

# ACC command file, run with acc.bat -cf <path\filename>
stopall
# first started runnable is stopped last
wait for stopped zoo_m
# restart agent must wait for success, before next ACC command can be executed
restart agent wait
# Last starting runnable
wait for started loadbalancer_m
list

2. Create a link to acc.bat with the usual arguments and append "-cf PathTo\ACC_commands.txt"

Maybe this use case can be added to the Aris Cloud Controller reference.

Regards, Martin