automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Saving the connection strings
- Step 2: Creating your organizations in 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: 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
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS installation guide
Last updated May 30, 2025
Step 2: Creating your organizations in Automation Suite
You must manually create your organizations in Automation Suite. The organization name must comply with the following Regex
format:
'^(?!.*$)[a-zA-Z][A-Za-z0-9]+$'.
The organization name must start with an uppercase or lowercase letter and must contain at least one character after the initial letter. Then, the name can include any combination of alphanumeric characters or underscores. Note, however, that the organization name must not end with an underscore.
For example, valid organization names include
Username, user_name1, or User123. Make sure to avoid invalid formats such as _username (does not start with a letter), username_(ends with an underscore), user name (contains a space), or user@name (contains an invalid character).
Note:
You do not have to manually create the tenant as the migration tool automatically performs this operation for you. The organization and tenant names do not have to be identical. While the organization name is customizable, the Automation Suite tenant name is the same as the standalone Orchestrator tenant name.
