Updating the cluster configuration

After regenerating the cluster_config.json file but before performing the upgrade, you can make various changes, such as updates to the database configuration, certificate configuration, and more. For details, see Performing advanced configuration.

Additionally, there are a few service-specific configurations that you must apply before upgrading. To check which changes are required for your Automation Suite cluster, see the following table:

Conditions	Actions
1. You installed Automation Suite 2023.4 or earlier in an offline environment. AND 2. You upgrade to Automation Suite 2023.10 or later.	You must manually add install_type: offline to the cluster_config.json file.
1. Orchestrator is installed on the old Automation Suite version. AND 2. You upgrade from Automation Suite 2022.10.	Set the following parameter in the cluster_config.json file to confirm that you agree with blocking classic folder executions. Without consent, the upgrade will fail. orchestrator.block_classic_executions: "true" For details, see Orchestrator-specific configuration.
1. Apps is installed on the old Automation Suite version. AND 2. You upgrade from Automation Suite 2022.10 or earlier.	Create a database for Apps with the following default name: AutomationSuite_Apps. Update the ODBC connection string for the Apps database in the cluster_config.json file. { "apps": { "sql_connection_str": "SERVER=sqlserver.mycompany.com,1433;DATABASE=AutomationSuite_Apps;DRIVER={ODBC Driver 17 for SQL Server};UID=testadmin;PWD=***;MultipleActiveResultSets=False;Encrypt=YES;TrustServerCertificate=NO;Connection Timeout=30;" } } For an example of the ODBC connection string, see Database configuration.
1. AI Center is installed on the old Automation Suite version and connects to an external Orchestrator.	Copy the Orchestrator certificates to the server node on which you plan to trigger the upgrade. For details, see Copy the Orchestrator certificate to the virtual machine. Update the cluster_config.json file with the following configuration: "aicenter": { "enabled": true, "orchestrator_url": "https://orchestrator.example.com", //Specify the Orchestrator URL for AI Center "identity_server_url": "https://orchestrator.example.com/identity", //Specify the Identiy URL for AI Center "orchestrator_cert_file_path": "/opt/UiPathAutomationSuite/UiPath_Installer/orch.cer", //Specify the path to the Orchestrator certificate "identity_cert_file_path": "/opt/UiPathAutomationSuite/UiPath_Installer/orch.cer", //Specify the path to Identity certificate file "metering_api_key": "test" //Specify the metering API key } Ensure that cluster_config.json includes the following parameter: { "sql_connection_string_template": "DOTNET connection string templates", "sql_connection_string_template_odbc": "ODBC connection string templates" }
1. Process Mining is not installed on the old Automation Suite version. AND 2. You want to enable Process Mining during the Automation Suite upgrade.	Add the sqlalchemy connection string template in the cluster_config.json file before the upgrade. For details, see Providing the new connection strings for installed products.