- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Orchestrator User Guide
Prerequisites
To use Automation Suite robots in a Production environment, you need a dedicated node for Automation Suite robots. You can create this node in a new Automation Suite installation, or add it as a new node to an existing Automation Suite installation.
For evaluation installations, you do not need a dedicated node for Automation Suite robots. In this case, you can install Automation Suite robots on the shared server node used for this environment.
If you want to include Automation Suite robots in your Automation Suite installation, you must meet the hardware requirements.
- To determine overall Automation Suite requirements, including Automation Suite robots and other services, use the requirements calculator.
-
To view the hardware requirements for only the dedicated node used for Automation Suite robots, see Additional Automation Suite Robots requirements.
Note: If you want to enable package caching, which can improve performance, a minimum of 10GB are required in addition to the requirements mentioned above. For details on enabling package caching, see Managing products.
For Automation Suite robots to be available in your installation, you must either include the Automation Suite Robots service at installation time, or enable the product at a later time.
Follow the Automation Suite installation instructions and, as part of this process, make sure that you enable the Automation Suite Robots service to have this feature available in your environment.
If you did not enable the Automation Suite Robots service during Automation Suite installation, or if you chose to disable this feature at one point, you can enable it after installation as described in Enabling or disabling Automation Suite Robots.
At least one Production (Unattended) or Testing runtime must be available for the tenant to create the machine template.
One such license allows for one job to run at one time on Automation Suite robots. More licenses allow you to run multiple jobs at the same time on the same robot.
