Workload Management (WLM) offers flexible deployment options—On-Premises for secure, compliance-driven environments, and Cloud-based for scalable, managed operations—each with distinct architectural and system requirements to ensure optimal performance and control.

Deployment options

Deployment options include On-Premises for organizations with strict compliance needs, featuring a private data center and internal VM or physical machines, and Automation Anywhere Cloud for businesses seeking scalability, with Cloud-based or hybrid devices..

On-Premises
  • Use case: Organizations with strict compliance or security needs
  • Architecture:
    • Control Room hosted in a private data center.
    • Tasks run on an internal VM or physical machines.
    • WLM queues and task (bot) assignments are managed within a secure internal environment.
Automation Anywhere Cloud
  • Use case: Businesses seeking scalability and managed infrastructure.
  • Architecture:
    • Control Room hosted on Automation Anywhere Cloud ( Amazon Web Services (AWS) and Google Cloud Platform (GCP)).
    • Workload queues and orchestration handled in the Cloud.
    • Devices can be Cloud-based or hybrid (Cloud + On-Premises).

Deployment components

The following table lists various components for On-Premises and Cloud deployment options.
Component Deployment option
Control Room On-Premises or Cloud
Devices Virtual (On-Premises or Cloud) or physical devices
Workload queues Centralized in the Control Room
Work items Structured in the database (internal queue or external DB via API)
Monitoring Dashboard, log aggregation, or notifications

System requirements

The system requirements for deploying and operating WLM in a Control Room include the following components:
Component Requirement
Control Room Installed On-Premises or deployed on Cloud
Devices VM, physical, or Cloud-based devices with the Bot Agent installed
Network access All devices must have access to the Control Room over HTTPS (443)
Database Internal to Control Room (PostgreSQL Server or Microsoft SQL Server for queue management
Storage Persistent storage for logs, work items, and results
Load balancer (optional) For high-availability (HA) deployments
Queues Workload queues must be created in the Control Room with appropriate schema (defined fields, priorities)
Work items Uploaded via CSV, Excel, or API
Device pools Devices grouped into device pools for concurrent processing
Credential Vault Used to securely store bot credentials if needed per work item
Roles and permissions Ensure that you have appropriate access rights to queues, bots, and devices. For more details, see WLM user roles and permissions.
Bot Agent Must be compatible with Control Room version

For more information, see Bot Agentcompatibility.
Browsers Google Chrome or Microsoft Edge for accessing the Control Room.

For more information, see Browser requirements for Automation Workspace
API clients Postman or custom scripts for uploading and managing work items via Control Room APIs.

For more information, see Control Room APIs.