Update all runnables on all nodes

To update all runnables on all nodes, run this ACC command:

on all nodes updateall

or

on all nodes force updateall

The force updateall command prevents confirmation for each node.

This command creates a backup of all working folders before any change is made. The backups are stored in the folder <ARIS Installation path>\server\bin\.backup.

These backups allow to reset to the previous ARIS version. This prevents a possible impairment of the system. If an update fails, a mixture of runnables from the previous version and the most recent version would result. Such an ARIS installation will most likely not work. Note that reset to the previous ARIS version is not required for the ARIS agent because the ARIS agent can use runnables of former ARIS versions.

The backup of the working folders takes some time and consumes a significant amount of disk space.

Warning

Make sure to backup application data before starting the update setup because the backups created automatically during the update process cannot be used as a backup of your application data.

You can turn the backup option off. If you do so, a rollback to the previous ARIS version is no longer possible. If you attempt an update without backing up your data, you run the risk of system outages and/or data loss, for which Software AG assumes no responsibility.

The updateall command first checks whether enough disk space is available. If the required amount is not available, a message is displayed, such as:

On node localhost 20,93 GB of usable space is available for back up, downloaded artifacts, working directory, plugins and unpacked runnables, but 72,67 GB must be available.

In this case, make sure that the requires amount of free disk space is available.

If the updateall ACC command was successful, the output looks like the following example of a three-node installation. Of course, versions, node names, runnable instance IDs, etc. can vary depending on the environment:

ACC+ >on all nodes updateall

WARNING! The updateall command will update ALL currently not running instances on all nodes. Are you sure? (Y/N)

y

Runnable zoo0 on node n1 will be updated to version 10.0.24.0

Runnable cloudsearch_m on node n1 will be updated to version 10.0.24.0

Runnable umcadmin_m on node n1 will be updated to version 10.0.24.0

Runnable abs_m on node n1 will be updated to version 10.0.24.0

Runnable apg_m on node n1 will be updated to version 10.0.24.0

Runnable copernicus_m on node n1 will be updated to version 10.0.24.0

Runnable zoo0 on node n2 will be updated to version 10.0.24.0

Runnable elastic_m on node n2 will be updated to version 10.0.24.0

Runnable couchdb_m on node n2 will be updated to version 10.0.24.0

Runnable adsadmin_m on node n2 will be updated to version 10.0.24.0

Runnable umcadmin_m on node n2 will be updated to version 10.0.24.0

Runnable octopus_m on node n2 will be updated to version 10.0.24.0

Runnable simulation_m on node n2 will be updated to version 10.0.24.0

Runnable loadbalancer_m on node n2 will be updated to version 10.0.24.0

Runnable zoo0 on node n3 will be updated to version 10.0.24.0

Runnable postgresECP_m on node n3 will be updated to version 10.0.24.0

Runnable cloudsearch_m on node n3 will be updated to version 10.0.24.0

Runnable couchdb_m on node n3 will be updated to version 10.0.24.0

Runnable adsadmin_m on node n3 will be updated to version 10.0.24.0

Runnable abs_m on node n3 will be updated to version 10.0.24.0

Runnable copernicus_m on node n3 will be updated to version 10.0.24.0

Runnable ecp_m on node n3 will be updated to version 10.0.24.0

Runnable loadbalancer_m on node n3 will be updated to version 10.0.24.0

Successfully updated runnable zoo0 on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable elastic_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable couchdb_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable adsadmin_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable umcadmin_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable octopus_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable simulation_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable loadbalancer_m on node n2 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable zoo0 on node n1 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable cloudsearch_m on node n1 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable umcadmin_m on node n1 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable abs_m on node n1 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable apg_m on node n1 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable copernicus_m on node n1 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable zoo0 on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable postgresECP_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable cloudsearch_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable couchdb_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable adsadmin_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable abs_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable copernicus_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable ecp_m on node n3 from version 10.0.0.2 to version 10.0.24.0

Successfully updated runnable loadbalancer_m on node n3 from version 10.0.0.2 to version 10.0.24.0

23 of 23 runnables updated.