Install workers on Linux, Windows Server and cloud

Choose the installation path

There are two supported paths: install Dova Worker Agent on an existing authorized server, or provision a cloud VM through Administrator → Cloud workers. Neither path automatically assigns every existing Session to the worker. Before starting, confirm tenant, operating system, approved capacity, outbound connectivity and responsibility for the infrastructure.

Download the currently published package through the supported catalog and verify its integrity. Package versions can differ from the Dova application version. Use the instructions bundled with the selected package and perform the initial exercise on an authorized laboratory server.

Linux prerequisites and installation

The documented prerequisites include Python 3.10 or later, a virtual environment, systemd, util-linux with flock, administrator access and outbound HTTPS to Dova and the approved package registry or mirror. The installer checks requirements; do not assume it installs a different Python or changes the operating system.

1. Extract the verified package on the laboratory server.
2. Run the prerequisite check from the package directory.
3. Complete installation only after resolving the reported requirements.

sudo sh execution-worker/install.sh --check
sudo sh execution-worker/install.sh

In Dova, use Register worker, select the intended system, enter the worker name and permitted concurrency, and generate the enrollment instructions. Run the generated command on the correct server. Supply the enrollment token through the supported hidden prompt, never through documentation, shell history or a shared screenshot.

After enrollment succeeds, enable and inspect the service:

sudo systemctl enable --now dovaetl-execution-worker
sudo systemctl status dovaetl-execution-worker

Windows Server prerequisites and installation

Use supported 64-bit Windows Server, PowerShell 5.1 or later and a machine-wide 64-bit Python 3.10+ installation accessible to the service account. A Windows Store alias or a Python installed only for the interactive user is unsuitable.

1. Extract the verified Windows package.
2. Open an elevated PowerShell in its directory.
3. Follow the bundled installer instructions and identify the actual machine-wide Python executable.
4. Generate enrollment for Windows Server and complete its hidden-prompt flow.
5. Start and inspect the installed service after successful enrollment.

Set-Service -Name DovaWorkerAgent -StartupType Automatic
Start-Service -Name DovaWorkerAgent
Get-Service -Name DovaWorkerAgent

The service uses a dedicated virtual account. Windows process limits do not make arbitrary untrusted code safe, and Windows workers remain private-only under the supported sharing contract.

Cloud installation and acceptance

Prepare Connections and Profiles, then use Provision worker as described in Cloud workers. Observe Provisioning history until you distinguish VM creation from completed agent enrollment.

Verify service state, recent heartbeat, displayed resources and tenant eligibility. Assign a synthetic Session to the worker, execute a small controlled file transformation and inspect its Monitor result. Concurrency represents slot units: a job can reserve more than one unit, so capacity is not simply a count of jobs.

If the worker is offline, inspect service, outbound connectivity and safe logs. If it is online but ineligible, inspect tenant, capabilities, policy and capacity. Enrollment does not configure database credentials or transfer input files.

Continue with Worker migration and removal before replacing or retiring infrastructure.