The update installation setup is available for ARIS 10 servers that have been installed by a setup program. So each ARIS server is installed on one machine (single-node installation). If you currently run ARIS in version 10.0.11 or lower, you must update to version 10.0.21 first and then update to ARIS in the current version. The direct update to the current version is blocked in server setup, the agent setup, and via ACC update command.
From ARIS version 10.0.12 or higher, you can directly update to the current version.
Check whether the intermediate ElasticSearch 8 migration to service release 21 is finished
Check the extended state of the ElasticSearch runnables using the ACC list command. There must not be an extended state red displayed anymore.
You can now continue with the update from ARIS service release 21 to ARIS in the current version.
ARIS Risk and Compliance
The update setup also updates ARIS Risk and Compliance installations with customizing. If the customizing contains unsupported changes or additional files, the warning Update/patch setup not supported and a list containing the affected files are output in the log file. To ensure that all customized files are available, the customizing must be enhanced again. For detailed information, refer to ARCM – Installation Guide > Installation of a customer-specific version (Customizing). The ARIS Risk and Compliance server update procedure is described in the ARIS Risk and Compliance Installation Guide.
On Linux systems you must first update ARIS Cloud Controller (ACC) and the ARIS agent. Then perform an update setup.
The default tenant will be updated and migrated automatically. All other tenant's system databases must be updated manually, All other tenant's system databases must be updated manually to get the most current script and method update.
To update customized installations, for example, multi-node systems, when an ARIS installations spans across several computers, please contact your local Software AG sales organization.
When you update or uninstall ARIS by an ARIS setup, the current installation will automatically be backed up. This process takes additional time and requires additional disk space while the setup is running. Make sure that the size of the free disk space is at least 15 GB larger than the folder size of the working directories <ARIS installation path>\server\bin\work (Windows®) or /home/ARIS10/cloudagent/work (Linux). The update will fail if there is insufficient free disk space. If the update process fails, all ARIS components will be rolled back automatically.
If you use an external database management system backup these systems before running an update setup. In case of a failed update you will be able to restore the external database systems, too.
Before updating backup all tenant's data (see: ARIS Cloud Controller Command-Line Tool.pdf) and read the ARIS Release Notes.pdf for last-minute information which couldn't be included in this document anymore. Documents can also be installed locally (see Technical Help: ARIS client Installation Guide). You can open or download documents and the Technical Help from the Documentation Web site. Documentation is also contained in the ARIS installation package that is available in the ARIS Download Center.
Prerequisites
You have downloaded the ARIS installation package to have access to the required files. To download the package, you need access to the ARIS Download Center where a login is required. You have received information on how to register and download the installation package from Software AG or your local Software AG sales organization.
Due to the current Tomcat (Ghostcat) vulnerability, block all ports except the load balancer HTTPPS port.
In the highly unlikely event of running reports during an update, the system database might fail to be updated. Make sure to lock scheduled reports before starting the update.
Use the reconfigure ACC command to change settings, such as ports.
Make sure that no file in the installation directory is locked. Therefore, close all Command Prompts pointing into the ARIS installation folder. If the prerequisites are not met and files are not writable, the setup fails because files cannot be updated. In this case, your installation cannot be automatically restored and ARIS may no longer run. To restore your installation, you must take further action.
Make sure to exit ACC before running the update setup.
If the ARIS help link does not work anymore (404 error) after the update of a custom configuration, the help URL is broken. You can easily fix it by modifying the useraction_default.xml file (<ARIS installation directory>\server\bin\work\work_copernicus_<s, m or l>\base\webapps\ROOT\WEB-INF\config\<customization>\instances\UserAction\).
In the broken URL the /connect/ entry is missing, for example:
/static/help/{locale}/handling/ca/index.htm#52910.htm
Add /connect/. The URL must look like in this example:
/static/help/{locale}/handling/connect/ca/index.htm#52910.htm.