Alteryx Server Admin key terms

The core Windows service that runs the Alteryx Server backend, hosting the scheduler, worker execution, and queue processing. Administrators start, stop, and restart it to apply configuration changes or recover from failures.

The server node component that accepts workflow execution requests, manages the job queue, and dispatches work to available workers. In a multi-node deployment it coordinates execution across the environment.

A server node or process that actually runs workflows assigned by the controller. Workers must have the required engines and data connections available to execute the assigned jobs.

A label assigned to a worker that restricts which workflows it can run. Schedules or workflows can require a tag so execution only occurs on appropriately configured machines.

The ordered list of workflow jobs waiting to be picked up and executed by workers. Monitoring queue depth helps administrators spot bottlenecks and capacity shortages.

The Server subsystem that triggers scheduled workflow runs at configured times and intervals. It enqueues jobs for the controller and records run history for each schedule.

A saved configuration that runs a workflow or app automatically on a defined frequency, such as hourly or daily. Schedules are owned by a user and subject to permission checks.

A single execution instance of a workflow or analytic app on the Server. Each job has a status, start and end times, messages, and outputs retained according to server settings.

The web interface where users browse, run, and share workflows, apps, and insights. It also provides administrative pages for managing users, permissions, and server settings.

A curated grouping of shared Gallery content that helps users find related workflows and apps. Collections can be public or restricted and are managed through access permissions.

A rule granting a user or group a specific level of access to content, such as view, run, or edit. Permissions can be set on workflows, collections, and other Gallery objects.

A predefined set of capabilities assigned to a user account, such as Curator, Artisan, or Viewer. Roles determine what a user can do across the Gallery and administrative areas.

A named set of user accounts used to assign permissions and content access in bulk. Groups simplify administration and can be linked to directory services for automatic membership.

A directory service used to authenticate users and organize them into groups. Alteryx Server can integrate with it so users sign in with domain credentials and inherit group membership.

An authentication approach letting users access the Gallery with credentials from an identity provider instead of a separate Server password. It typically relies on SAML or similar protocols.

The process of verifying a user's identity when they access the Server, whether through built-in accounts, directory services, or an identity provider. It precedes authorization checks.

The process of deciding what an authenticated user is allowed to see or do on the Server. It is enforced through roles, permissions, and content ownership rules.

The administrative configuration area in the Gallery where server behavior is controlled, including workers, schedules, email, authentication, and security options. Changes often require a service restart.

The stored settings and configuration files that define how a Server instance operates, including node roles, ports, and data connections. These are typically edited through the admin interface or a configuration tool.

The process of moving a Server installation to a newer version, which includes backing up data, running the installer, and migrating the repository. Proper sequencing prevents data loss and downtime.

The database that stores Server metadata such as users, schedules, permissions, and workflow definitions. It is the most critical component to back up and protect.

The database engine used by Alteryx Server to hold the repository. Administrators must ensure it is healthy, backed up, and sized appropriately for the environment.

A saved copy of Server data, including the repository and configuration, used to recover from failures or prepare for upgrades. Regular tested backups are essential for continuity.

The process of recovering Server data from a backup after a failure or migration. It must be validated to confirm users, schedules, and content are intact.

A deployment design using redundant nodes so the Server keeps working if one component fails. It typically involves multiple workers, shared storage, and a resilient database setup.

A saved definition that lets workflows connect to a database or other data source without embedding credentials in the workflow. Administrators manage these centrally for consistency and security.

Stored authentication details, such as a username and password, used by the Server to access data sources or run scheduled workflows. Credentials are encrypted and controlled by administrators.

The administrative interface for creating, testing, and sharing data connections across the Server. It controls which users and workflows can use each connection.

The process of encoding stored secrets and sensitive data so they cannot be read without the proper key. Alteryx Server uses it to protect credentials and configuration values.

A record of Server activity and errors written by services and components. Administrators review logs to diagnose failed jobs, authentication problems, and service issues.

The systematic process of identifying and resolving Server problems using logs, job results, service status, and configuration checks. It often starts with confirming the service is running.

The outputs and messages saved from a completed or failed job, including logs and generated files. They help users and administrators verify execution and investigate errors.

A saved analytic process published to the Server that can be run manually or on a schedule. Its execution depends on available workers, credentials, and permissions.

An interactive workflow published to the Gallery that prompts users for input before running. Apps can be shared with specific users or groups and run on demand.

A single machine in a Server deployment that hosts one or more roles, such as controller or worker. Multi-node setups distribute load and improve resilience.

The activation code that determines which Server features and capacity are available. It must be applied during installation and updated when the license changes.

The process of setting up Alteryx Server, including prerequisites, service accounts, database configuration, and license activation. Correct setup prevents later authentication and execution failures.

The Windows account under which the Alteryx service runs. It needs appropriate permissions to access files, databases, and network resources used by workflows.