Update Automation 360 to latest version
- Updated: 2024/01/05
Update Automation 360 to latest version
Update Automation 360 On-Premises to the latest version to get new features and enhancements that help improve and scale your automation programs.
Prerequisites
- Before each release update, ensure that you backup the database, repository, and
installation configuration files. Note: The configuration files in <Installation Directory>/config/ are overwritten after an update. Ensure you either take a backup of these files before the update, or rewrite the settings after the update.
- Ensure you are on one of the previous three releases from the latest release (on
an n−3 release, where n refers to the latest release).
For example, to update to Automation 360 v.21 release, you must be on the v.20, v.19, or v.18 release. However, to update from v.15 to Automation 360 v.21 release, you must first update to v.18 release and then update to Automation 360 v.21 release. In the second scenario, ensure you perform backup of v.15 data before you update to v.18, and then backup v.18 data before you update to v.21.
- You must perform the following steps before you update the Automation 360 version:
- Ensure you reconfigure the settings for log4j2.xml files after the installation because when you update, the previous settings set at log level in log4j2 change back to default.
- Configure the SSL settings (certificates) every time you update.
- When you update from an Automation 360 release
earlier than an n−3 release to the latest release, you might see an Elasticsearch Open Distro error message. Before
updating, delete the multiple application_log indices from Elasticsearch, which will free up disk space for the
update.
For details on the Elasticsearch indices limit, see Cluster-level shard allocation and routing settings.
- Before you update from Automation 360 On-Premises v.22 to the latest release, see A360 | Upgrading to A360.23, A360.24, A360.25 from A360.22 (A-People login required)
- When you update to Automation 360 v.25 from an
earlier release, an error might occur when the database server includes the
instance name. In such a scenario, remove the instance name in the database
server and continue with the installation.
For information on removing the instance name from the database server, see Error parsing the SQL instance name while upgrading to Automation 360 v.25 (A-People login required).
- Before you update to Automation 360 v.28 On-Premises from any of the earlier versions, review the following article: Automation 360 On-Premise Edition | A360.28 – Upgrade Considerations (A-People login required). This article is applicable only to On-Premises customers who started using Automation 360 from v.15 or previous versions. To successfully update to Automation 360 v.28, you must perform the pre-update steps in the KB article.