Alteryx Server Admin flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Controller node

Server host that runs the Gallery web app, API, and scheduler service, dispatching jobs to Workers and coordinating metadata with MongoDB.

Worker node

Server host that runs AlteryxEngine to execute workflows, receiving jobs from the Controller and reporting results back to MongoDB.

MongoDB role

Persistence tier storing users, schedules, permissions, and workflow metadata; it does not store the workflow package files themselves.

RuntimeSettings.xml

Configuration file defining a node's Controller/Worker role, MongoDB connection string, and queue settings; edits require an AlteryxService restart.

Install order

For distributed deployments: MongoDB first, then Controller, then Workers, then configure the Gallery to connect to MongoDB.

Version parity requirement

Controller and all Workers must run the same Alteryx version and matching tools/macros, or jobs fail to execute correctly.

Pre-upgrade backup

Back up MongoDB and the Server data directory before upgrading, because schema migrations are not trivially reversible.

Worker maintenance mode

State that stops a Worker from accepting new jobs so it can be safely upgraded or serviced without interrupting runs.

SAML 2.0 SSO

Authentication mode using an Identity Provider; requires IdP metadata, assertion consumer URL, and username/email attribute mappings.

Curator role

Highest built-in Gallery role with administrative rights over users, settings, data connections, and content across districts.

API key permissions

An API key inherits the owning user's permissions, so its effective access equals that user's role and asset rights.

Windows Integrated Authentication

Authentication mode using NTLM/Kerberos so users sign in with domain credentials; requires Gallery and IIS configuration.

Queue assignment

Mapping of a schedule to specific Workers; a schedule with no eligible Worker in its queue stays pending.

Job concurrency limit

Each Worker engine runs one job at a time, so throughput equals the number of engines available in the assigned queue.

Triggered schedule

Schedule type that starts a workflow in response to an event such as file arrival or an API call, rather than a fixed time.

Chained workflows

Sequentially linked workflows where completion of one can start the next; an upstream failure can block downstream runs.

District

Admin-defined group used to scope who can publish and view content; a user may belong to multiple districts.

Curated Collection

Admin-curated grouping of assets presented to a chosen audience of users or districts for easier discovery.

Asset subscription

A user following an asset to receive update/run notifications; it does not by itself grant permission to run the asset.

Collaborator permission

Asset-level permission allowing a user to edit a published workflow or app, distinct from viewer (run/view) rights.

AlteryxService log

Primary service log for Controller and Worker roles; used to diagnose job dispatch, startup, and connectivity problems.

Designer-vs-Server failure

Workflow succeeds locally but fails on Server, usually due to a local file path or a connection not published to the Gallery.

Gallery 500/502 errors

Web-tier failures pointing to IIS, application pool, or MongoDB connectivity issues rather than workflow logic.

Run history record

Stored run status (Success/Error/Canceled) with links to engine logs, used for root-cause analysis of job failures.

Backup scope

The three things to protect: MongoDB metadata, the Server data/asset directory, and configuration files like RuntimeSettings.xml.

mongodump

MongoDB utility producing a consistent logical backup of metadata; restored with mongorestore for recovery.

MongoDB replica set

Cluster of MongoDB nodes providing high availability for the metadata tier; a standalone mongod is a single point of failure.

Restore verification

Post-restore step: restart AlteryxService, confirm worker registration, and validate that metadata matches the restored assets.

Data connection

Curator-created Gallery object storing encrypted credentials so workflow authors can use a source without seeing secrets.

Run-as credentials

Execution identity used by the engine for data access, separate from the user's Gallery login; determines runtime permissions.

Connect permission

Right required on a data connection for a user to use it; without it the workflow fails at runtime.

Credential encryption key

Key tied to the deployment that encrypts stored connection credentials; moving MongoDB without it breaks decryption.