Because all runnables were updated at this stage, the remote repository is no longer needed, and it can be shut down. However, if you want to configure another instance of a runnable later, you must keep the remote repository. Otherwise, configuring a new runnable will fail, because the ARIS agent first checks the remote repository for the most recent runnable version, and uses its local repository only if the file in the remote repository is of the same version. If you want to be able to configure additional runnables, you can now switch the ARIS agents to again only use the runnables already contained in their local repository. To do so, enter this ACC command:
on all nodes set local.repository.only=true
Note that you can only configure additional instances of those runnables that are already in the local repository of the related ARIS agent in the respective version.
For example, if you have configured, an abs runnable on a node n1, after applying the setting above, you can configure an additional abs runnable on the same node (or configure it again if you had de-configured it). However, you cannot configure an additional abs runnable that runs on node n2, for example, if no instance of the abs runnable exists on this node.
If the server you are using is running and the disk space is not a critical factor so that you can leave the remote repository in place, you are recommended to leave the local.repository.only parameter set to false. In this case, you can configure additional instances of any runnable on any node. Only if you must shut down the remote repository due to limited disk space after the update has completed, use the setting mentioned above.