Installation and Configuration
Installation is driven by the Alteryx Installer (or silent command-line install), and the critical decisions are the service account, the installation directory, and the role configuration (Controller, Worker, or both). The service account must be a domain or local account with Log on as a service, read/write to the Alteryx data directories, and-if workflows touch network resources-the appropriate network permissions. The System Settings dialog (run as the service account context) configures the Controller host, worker threads, MongoDB connection, SSL, and the Gallery URL.
Configuration concepts to know: the RuntimeSettings.xml and related config files that persist node settings; the distinction between the Controller connection string and the MongoDB connection string; enabling SSL/TLS for the Gallery and API; setting the base URL so links and API callbacks resolve correctly; and configuring SMTP for notifications. After changing service account or Controller settings, the AlteryxService must be restarted, and Workers must be able to reach the Controller on the required ports.
Traps: changing the service account without updating directory permissions (workflows then fail with access errors); pointing a Worker at the wrong Controller; forgetting that the Gallery base URL must match the externally reachable address or emailed links break; and assuming the installer validates connectivity for you.
Worked example: A Worker shows as offline. Check (1) AlteryxService is running, (2) the Worker's Controller hostname resolves, (3) the firewall allows the Controller ports, and (4) the service account can authenticate to the Controller. Fix the earliest failing link first.
Rule of thumb: configure and test the service account and network path before installing roles, because most post-install failures are permission or connectivity issues, not product bugs.