- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Configuring appSettings
The Orchestrator configuration consists of an array of Kubernetes config maps and secrets that are loaded in a specific order, and placed in the appSettings section of config maps.
The latest configuration is loaded from the orchestrator-customconfig config map. Any newly loaded configuration overwrites all existing settings that have the same key.
To display the current custom Orchestrator configuration, use the config orchestrator get-config uipathctl command:
uipathctl config orchestrator get-config --app-settings
{
"key":"value"
}
uipathctl config orchestrator get-config --app-settings
{
"key":"value"
}
The uipathctl commands needed for configuring appSettings are:
uipathctl config orchestrator get-config --app-settings- This exports the current configuration in a key-value pair json file, ready for editing. You can read more about it here.uipathctl config orchestrator update-config --app-settings appsettings.json- This updates the configuration with your changes. You can read more about it here.
-
Export the current custom
appSettingsconfiguration to a json file using this command:uipathctl config orchestrator get-config --app-settings > appsettings.jsonuipathctl config orchestrator get-config --app-settings > appsettings.json -
Edit the exported
appsettings.jsonfile as needed. You can add, remove, or change any of its settings.Example:
{ "Triggers.DisableWhenFailedCount": "20", "Triggers.JobsCountStrategy": "NoLimit" }{ "Triggers.DisableWhenFailedCount": "20", "Triggers.JobsCountStrategy": "NoLimit" }Note:You must export the file again every time you need to make a change, since the update overwrites all settings.
-
Update the
appSettingsconfiguration using this command:uipathctl config orchestrator update-config --app-settings appsettings.json orchestrator config updateduipathctl config orchestrator update-config --app-settings appsettings.json orchestrator config updated