TSA Study This
Port: vizql & sessions
9403 and each gets its own after
Port: PostgreSQL
8060, 8061
Port: TSM
8850
vCPUs
1 vCPU = 0.5 CPU
Port: Gateway
80, 443
Port: License Service range
27000-27009
Recommended production hardware
64 gb RAM 8 core 500GB - 1 TB
Port: reserved by default for dynamic mapping of Tableau processes
8000-9000
SAML
Allows web domains to exchange user authentication and authorize data SSO
Name all licensed processes
Application Server Backgrounder VizQL Data Server Data Engine Prep Conductor
Default Single Node Topology
Application Server x1 Ask Data x1 Backgrounder x2 Cache Server x2 Cluster Controller x1 Data Engine x1 Data Server x2 Elastic Server x1 File Store x1 Gateway x1 Messaging Service Repository x1 Search and Browse x1 VizQL x2 Licensing x1 Cluster Controller x1 Coordination Service x1
Flows: Refresh an Extract
Backgrounder queries background_jobs table in Repository every 10 seconds for schedules set Repository returns info on schedules needing to be run to Backgrounder Available backgrounder picks up the refresh extract task and sets progress to 0 (in progress) Backgrounder verifies connection and uses embedded credentials to connect to underlying data source Data Engine creates local.hyper database Data connections are used to query underlying data source for data to refresh extract The external data source returns data to the Backgrounder Backgrounder requests the Data Engine to insert tuples into local DB inside TableauTemp folder Data Engine uploads local Hyper file in Data Engine folder and rewrites relative path File Store sends relative path to Repository then starts replication Repository updates XML and the extracts table Task is updated to priority 100 in background jobs table (completed)
Installation path
C:\Program Files\Tableau\Tableau Server\ Packages AND C: \ProgramData\Tableau\Tableau Server
Core v License
Core: License every core that has a licensed process (flexible user count) User: License every user that has TS access
Extract v live connection
Extract: stored on TS as TDE / .hyper file LIve: queries the database
Role: License Type: Max capabilities:
License Type: Explorer
Role: Server Administrator 2 License Type: Max Capabilities:
License Type: Explorer Max capabilities: Tableau Server only; not applicable to Tableau Online unrestricted access to the configuration settings for the Tableau Server browser environment, all sites on the server, users and groups, and all content assets, such as projects, flows, data sources (including connection information), and workbooks can't connect to external data from the browser to create a new data source. They can author or publish workbooks and data sources from Tableau Desktop. (they function as an Explorer (can publish) site role with regards to publishing).
Role: Unlicensed License Type: Max capabilities:
License Type: Unlicensed Max capabilities: Unlicensed users can't sign in to Tableau Server or Tableau Online. Users are assigned the Unlicensed role in the following circumstances: You import users from a CSV file and their license level is set to unlicensed. The number of available licenses is reached at the time you add or import users. You remove a user who owns content on the site. The user will still own the content but not be able to do anything with it.
Role: Viewer License Type: Max capabilities:
License Type: Viewer Max capabilities: Can see published views others have created and use most interaction features. Can subscribe to views and download as images or summary data. Can't connect to data, create, edit, or publish content, or set data alerts.
Role: Server Administrator 1 License type: Max capabilities:
License type: Creator Max capabilities: Available on Tableau Server only; not applicable to Tableau Online highest license activated on the server between Creator and Explorer. It allows unrestricted access to the configuration settings for the Tableau Server browser environment, all sites on the server, users and groups, and all content assets, such as flows, projects, data sources (including connection information), and workbooks. Connect to Tableau published data sources or external data, from the browser, Tableau Desktop, or Tableau Prep; create and publish new data sources; author and publish workbooks.
Role: Creator License type: Max capabilities:
License type: Creator Max capabilities: This site role offers non-administrators the maximum level of content access. Connect to Tableau or external data in the browser, build and publish flows, data sources and workbooks, have access to Dashboard Starters, and use interaction features on published views. Can also connect to data from Tableau Prep or Tableau Desktop, publish (upload/save) and download flows, workbooks and data sources.
Role: Site Admin Creator License type: Max capabilities:
License type: Creator Max capabilities: highest level of access for Tableau Online Unrestricted access to content like server admin but at the site level. Connect to Tableau or external data in the browser, Tableau Desktop, or Tableau Prep; create new data sources; build and publish content. On Tableau Server, server administrators can determine whether or not to allow site administrators to manage users and assign site roles and site membership. By default, on Tableau Server, and always on Tableau Online, site administrators are allowed these capabilities.
Role: Explorer License Type: Max capabilities
License type: Explorer Max capabilities: Can browse and interact with published views. Can subscribe to content, create data driven alerts, connect to Tableau published data sources and open workbooks in the web authoring environment for ad-hoc queries, but they can't save their work.
Role: Explorer (can publish) License Type: Max capabilities: (differ vs creator)
License type: Explorer Max capabilities: Can publish workbooks from the web using existing data sources, browse and interact with published views, use all interaction features, and can save new standalone data sources from data connections embedded in workbooks. In the web editing environment, can edit and save existing workbooks. Cannot save new standalone data sources from data connections embedded in workbooks, and cannot connect to external data and create new data sources.
Role: Site Admin Explorer License Type: Max capabilities:
License type: Explorer Max capabilities: Same access to site and user configuration as Site Administrator Creator, but can't connect to external data from the web editing environment. Can connect to Tableau published data sources to create new workbooks, and edit and save existing workbooks.
Run as User account
Needs to have access to external databases, network shares, or cloud data. This account accesses these for Tableau Server
Messaging Service Process Name? Purpose? Notes? Licensed?
Process Name: activemqserver Purpose:support communication between microservices in Tableau Server. Automatically installed on initial node when you install Tableau Server. One instance of the service is required. On multi-node installations of Tableau Server, you can move the Messaging Service to a different node. In version 2020.1 you can add a second instance of the Messaging Service on an additional node to provide some redundancy (in 2019.4 you cannot configure more than one instance in a cluster). For more information, see Licensed: No
Metrics Service Process Name? Purpose? Notes? Licensed?
Process Name: metrics Purpose: responsible for reading and writing Metric data in Tableau Server. Notes: Automatically installed on initial node with a single instance when you install Tableau Server. One instance of the service is required. You can add additional instances as necessary . We recommend at least one instance of the Metrics service on each node in a multi-node installation of Tableau Server Licensed: No
Internal Data Source Properties Process Name? Purpose? Notes? Licensed?
Process Name: tdsnativeservice Purpose: internal service that only communicates with the Data Source Properties service. Notes: One instance of Internal Data Source Properties is automatically configured on each node that has an instance of Data Source Properties on it.Added in 2020.1 Licensed: No
Data Source Properties Process Name? Purpose? Notes? Licensed?
Process Name: tdsservice Purpose: Provides published data source metadata to client services like Ask Data Notes: added by default on the initial node. A Tableau Server installation must include at least one instance. For performance reasons, we recommend installing the Data Source Properties service on any node that has Application Server (VizPortal) installed. Added in 2020.1 Licensed: No
Non-Interactive Microservice container Services? Purpose? Licensed? difference between interactive and non interactive?
Purpose: Container process for internal Tableau Server microservices that are bundled together for ease of deployment and scalability purposes. Relationship Ingestor Microservice External Content Provider Microservice Content Provider Microservice Flow Provider Microservice Notes: Can't be configured manually. one instance of the Non-Interactive Microservice Container is added to every node that has Backgrounder installed Licensed: No
Interactive Microservice container Services? Purpose? Licensed? difference between interactive and non interactive?
Purpose: Container process for internal Tableau Server microservices that are bundled together for ease of deployment and scalability purposes. Relationship Query Microservice Content Model Microservice Notes: Can't be configured manually. By default, one instance of the Interactive Microservice Container is added to every node that has Application Server (Vizportal) installed Licensed: No
Tabprotoserv - Purpose?
Purpose: Definition between VizQL and database drivers. Spawned by VizQL. Created to avoid VizQL crashing if driver causes an error.
Flows: Authenticate with AD
Request to access TS from browser Gateway receives and directs request to app server App server prompts for username App server passes results to Repository for verification and permissions Repository sends back to App server App server forwards request to Gateway Gateway forwards to AD controller AD controller verifies password and passes response to Gateway Gateway receives response and passes to App Server App server generates UI and forwards request back to Gateway Gateway forwards request to client Client displays UI
Flows: Authenticate with local
Request to access TS from browser Gateway receives and directs request to app server Application server prompts for user/pass App server passes to Repository for verification & permission Repository sends back to App server App server generates UI and sends back to Gateway Gateway sends response to client and client displays UI
Flows: Authenticate with SAML
Request to access TS send from client Gateway receives request and passes to App Server App Server redirects request to registered SAML idP SAML idP receives a request of user/pass and authenticates user SAML idP returns SAML success response to App Server App Server sends request to Repository Repository validates user and returns request to App Server App Server passes request to Gateway Gateway sends response to user User logs in
Flows: Access a View - Embedded Live Connection
Request to access view on TS from Client Gateway receives the request and passes to App Server App Server authenticates and sends request to VizQL to build frame VizQL queries to Repository for permissions and .twb file Repository validates and sends back to VizQL VizQL connects to data connections Data connections pull from DB and access data source Data is passed back to VizQL VizQL renders view and sends to Gateway Gateway delivers rendered view response to user Client displays rendered view
Flows: Access a View - Embedded Extract
Request to access view on TS from client Gateway receives request and passes to App Server App Server authenticates and sends request to VizQL to build frame VizQL queries Repository for permissions and .twb Repository validates and sends back to VizQL VizQL requests data from Data Engine Data Engine pulls extract and passes to VizQL VizQL renders view and delivers to Gateway Gateway sends response to user client displays rendered view
Flows: Access a View - Cached View
Request to access view on TS from client Gateway receives request and passes to App Server App server authenticates and sends request to VizQL to build framework VizQL queries Repository for permissions and .twb file Repository validates and sends back to VizQL VizQL checks in proc cache, if results aren't there, it checks Cache Server Cache Server retrieves cached query from external query cache and passes to VizQL VizQL renders view and sends to Gateway Gateway responds to user with rendered view Client displays rendered view
Flows: Access a View - External File
Request to access view on TS from client Gateway receives request and passes to App Server App server authenticates and sends request to VizQL to build framework VizQL queries Repository for permissions and .twb file Repository validates and sends back to VizQL VizQL queries Repository for data Repository sends results of query to VizQL VizQL renders view and sends to Gateway Gateway responds to user with rendered view Client displays rendered view
Flows: Access a view - Published Live Connection
Request to access view on TS sent through client Gateway receives request and passes to App Server App Server authenticates and sends request to VizQL to build frame VizQL queries Repository for permissions and .twb Repository sends back to VizQL VizQL sends query to Data Server through Gateway Data Server acts as proxy between data source and request Data Connections receive and are used to access Data Source Data Server interprets DB data Data Server passes back to VizQL VizQL renders view and delivers the Gateway Gateway sends view as response to user Client displays rendered view
Flows: Access a View - published extract
Request to access view on TS sent through client Gateway receives request and passes to App Server App server authenticates and sends request to VizQL to build frame VizQL queries Repository for valid user permissions then requests .twb Repository validates and sends .twb to VizQL VizQL sends a query through Gateway to Data Server to retrieve the data Data Server acts as a proxy to the published extract and queries Data Engine Data Engine pulls the extract and sends it to Data Server then sends to VizQL VizQL renders the view and delivers view via Gateway Gateway sends the rendered view to the user
License Manager (TSM process) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually Purpose: Handles licensing. Checks status of licensed processes every 72 hours, and every time a process spins up. If service is down when check is scheduled, server will go into unlicensed state. Notes: Automatically installed on the initial node when you install TSM. A single instance of this is installed on a Tableau Server cluster. The License Manager process should only be manually configured if the initial node fails. https://onlinehelp.tableau.com/current/server/en-us/distrib_ha_init_node_fail.htm Licensed: No
Database Maintenance (TSM process stopped unless they are actively running) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually Purpose: Service responsible for performing maintenance operations on the Tableau Server repository. Notes: Automatically installed on each node where you install Tableau Server. Shows a status of stopped in output of tsm status -v unless it is actively performing database maintenance. Maintenance can include updates related to enabling remote access to the repository. You cannot configure the Database Maintenance service manually. Licensed: No
Backup / Restore (TSM process stopped unless they are actively running) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually Purpose: The Backup and Restore service is responsible for performing backup and restore operations on the data stored in the Tableau Server repository and file store. Notes: Automatically installed on each node where you install Tableau Server. Shows a status of stopped in the output of tsm status -v unless it is performing a backup or restore operation. You cannot configure the Backup and Restore service manually. Licensed: No
SAML Service Server Processes Name/exe: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually Purpose: The SAML Server acts as a proxy between Tableau Server and SAML Identity Providers (IdPs) Notes: Automatically installed on each node where you install Tableau Server. Shows a status of stopped in output of tsm status -v unless site SAML is enabled Licensed: No
Site Import / Export (TSM process stopped unless they are actively running) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually Purpose: The Site Import and Export service is responsible for migrating Tableau Server sites between server clusters. Notes: Automatically installed on each node where you install Tableau Server. Shows a status of stopped in output of tsm status -v unless it is performing an import or export. You cannot configure the Site Import and Export service manually. Licensed: No
Administration Agent (TSM process) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually Purpose: The TSM agent monitors the Coordination Service for changes to configuration or topology and delivers new configurations to each service (configuration) or deploys new services and removes old ones (topology) Notes: Automatically installed when you install TSM on the initial node. Licensed: No
Ask Data Server Processes Name/exe: ? Underlying technology? Purpose: ? Notes: ? Licensed: ? N/A threading Bound by?
Server Processes Name: Cannot be configured manually (there should probably still be a server processes?) Purpose: Handles natural-language processing queries used to explore data sources. Tightly integrated with VizQL Server and Data Server to help users query with VizQL using NLP instead of drag-and-drop. Relies on Elastic Server to learn about data sources and the Content Model Microservice to show detailed information about data source fields. Can currently handle data sources with a maximum of 1,000 fields Notes: Runs automatically on all nodes where Data Server is running. Licensed: No Bound by: CPU, maybe memory
Administration Controller (TSM process) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually, except to move it to another node. Purpose: The TSM Controller handles requests to TSM and orchestrates configuration and topology changes and workflow across service processes. The controller also serves as the TSM REST API endpoint (HTTPS) Notes: Automatically installed when you install TSM on the initial node. You cannot configure the Administration Controller manually except to move it to another node. https://onlinehelp.tableau.com/current/server/en-us/distrib_ha_init_node_fail.htm Licensed: No
Data Engine Server Processes Name/exe: ? Underlying Technology? Purpose: ? Notes: ? Licensed: ? Single threaded? Bound by?
Server Processes Name: Cannot be configured manually./hyper.exe Underlying technology: proprietary Purpose: The Data Engine creates data extracts and processes queries. creating, refreshing or querying extracts. Notes: Automatically installed when you install File Store, VizQL Server, Application Server (VizPortal), Data Server, or Backgrounder. Licensed: Yes Single threaded: No Bound by: CPU, RAM, I/O, network
Service Manager (TSM process) Server Processes Name/exe: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: Cannot be configured manually/tabsvc.exe Purpose: Parent process for all Tableau Server processes. Install, configure, license, stop, start, manage server. The Service Manager manages the lifecycle of the Tableau Server business processes: Notes: Automatically installed on all nodes. You cannot configure the Service Manager Manually. Licensed: No
Backgrounder Server Processes Name/exe: ? Underlying Technology? Purpose: ? Notes: ? Licensed: ? Single threaded? Bound by? Scale?
Server Processes Name: backgrounder/backgrounder.exe Underlying technology: proprietary Purpose: Runs server tasks, including extract refreshes, subscriptions, 'Run Now' tasks, and tasks initiated from tabcmd, data driven alerts, refresh prep flows Notes: When Backgrounder is installed, Data Engine is also installed, unless the node already has an instance of Data Engine. In most situations you can change the number of backgrounder instances on an existing node of a running server without causing a stop and restart of the server. An exception is if you are adding backgrounder to an existing node that did not that did not previously have backgrounder or any other process that also installs Data Engine. Licensed: Yes Single threaded: Yes Bound by: CPU Scale: cores / 2
Cache Server Server Processes Name/exe: ? Underlying Technology? Purpose: ? Notes: ? Licensed: ? single threaded? Bound by?
Server Processes Name: cacheserver/redis-server.exe Underlying technology: Redis Purpose: Temporarily stores most frequently used data. A query cache distributed and shared across the server cluster. This in-memory cache server speeds user experience across many scenarios. VizQL server, backgrounder, and data server (and application server to a lesser extent) make cache requests to the cache server on behalf of users or jobs. The cache is single-threaded, so if you need better performance you should run additional instances of cache server. Licensed: No single threaded? yes bound by: minimal CPU consumption
Coordination Service (TSM process) Server Processes Name/exe: ? Underlying technology? Purpose: ? Notes: ? Licensed: ? Single threaded?
Server Processes Name: cannot be set with tsm topology-set procesess/zookeeper.exe Underlying technology: Apache Zookeeper Purpose: Coordinates activities on the server, guaranteeing a quorum in the event of a failure, and serving as the source of "truth" regarding the server topology, configuration, and state Notes: Automatically installed on the initial node. No other instances are installed unless you explicitly deploy a new Coordination Service ensemble. If coordination service detects that fewer than half of the instances of the service are running, it shuts the server down. Having at least 3 nodes ensure that coordination service can establish quorum Licensed: No Single threaded: yes
Client File Service (TSM process) Server Processes Name: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: clientfileservice Purpose: The Client File Service (CFS) Handles distribution of the following user-provided configuration files across all nodes in the cluster: Kerberos - keytab; SAML - certificate, key, metadata file; OpenID - metadata file; Customization - image files; External SSL - SSL certificate; Mutual SSL - CA cert. Notes: Automatically installed on the initial node. no other instances are installed unless you explicitly configure them. In multi-node deployments we recommend you configure an instances of CFS on each of the nodes where you deploy the Coordination Service. Redeploying the Coordination Service does not have any impact on CFS. CFS does not display in the Status page or the configuration page but is visible in the output of the tsm status -v command. To view or set instances of CFS use the tsm topology command Licensed: No
Cluster Controller Server Processes Name/exe: ? Underlying technology? Purpose: ? Notes: ? Licensed: ? single threaded?
Server Processes Name: clustercontroller/.exe Underlying technology: proprietary Purpose: The Cluster Controller is responsible for monitoring various components, detecting failures, and running fail-over when needed. Part of the base install, which means it is automatically installed on all nodes. n The "brains" of the Tableau Server system. n Has a broad view of the cluster because of the Coordination Service. If the cluster controller goes down on a node, all Tableau Server processes on that node go down. n Monitors server health and availability. n Measures and logs disk IO metrics every minute. n Reports on the status of the components. n Decides when to failover the active Repository. n Launches the Repository process and coordinates active and passive Repositories. n In a multi-node installation, one of the Cluster Controller processes is elected by the Coordination Service as the leader of the others; the node that hosts the lead Cluster Controller is random. Notes: Required on each node. Not automatically installed. Licensed: No single threaded? yes
Data Server Server Processes Name/exe: ? Underlying technology? Purpose: ? Notes: ? Licensed: ? Single threaded? Bound by?
Server Processes Name: dataserver/.exe Underlying technology: Proprietary Purpose: Data Server manages connections to PUBLISHED Tableau Server data connections. Serves as a proxy between requests for data and individual data sources Multiple workbooks can use the same data extract Enables data governance Centralized metadata management for data sources Centralized driver deployment Auditing Single source of truth.Manages published data-source metadata (not the data itself). n Acts as a proxy between requests for data (from VizQL Server or Tableau Desktop) and published data sources. n Enables centralized management of data connections. n Enables centralized driver deployment on the server (including ODBC) so individual users don't need to install drivers on their computers to access a data source. n Allows multiple workbooks to use the same data extract or live connection Notes: When Data Server is installed, Data Engine is also installed, Licensed: Yes Single threaded: No Bound by: Network, maybe CPU
Elastic Server Server Processes Name/exe: ? Purpose: ? Notes: ? Licensed: ? single threaded?
Server Processes Name: elasticserver Purpose: Elastic Server is used by Ask Data to index and cache data. Helps NLP learn about data sources by indexing and caching necessary data in a data repository Notes: Only one Elastic Server process can be running and it can optionally be moved to any node in the cluster. The Elastic Server heap size can be configured by using the elasticserver.vmopts TSM configuration option. For more information, see: https://onlinehelp.tableau.com/current/server/en-us/cli_configuration-set_tsm.htm Licensed: No single threaded? no
File Store Server Processes Name/exe: ? Underlying Technologies? Purpose: ? Notes: ? Licensed: ? N/A threaded Replication Triggers?
Server Processes Name: filestore/.exe Underlying technology: proprietary Purpose: Storage & replication for extract files. The File Store automatically replicates extracts across Data Engine nodes Notes: When File Store is installed, Data Engine is also installed, unless the node already has an instance of Data Engine Licensed: No, exception - data engine is and comes with it Replication Triggers? Publishing, extract refresh, decommissioning, backups
Tableau Prep Conductor Server Processes Name/exe: ? Purpose: ? Notes: ? Licensed: ?
Server Processes Name: flowprocessor Purpose: Tableau Prep Conductor runs a flow, checks connection credentials, and sends alerts if a flow fails. It leverages the scheduling and tracking functionality of Tableau Server so you can automate running flows to update the flow output. Notes: Requires Data Management Add-on to enable this on Tableau Server. By default, it is automatically enabled on a node where backgrounder is enabled. If the node role is set to exclude flows, then Tableau Prep Conductor is not installed on that node. https://onlinehelp.tableau.com/current/server/en-us/server_node_roles.htm Licensed: Yes
Gateway Server Processes Name/exe: ? Underlying Technology? Purpose: ? Notes: ? Required on any node with? Licensed: ? single threaded? Bound by?
Server Processes Name: gateway/httpd.exe Underlying technology: Apache Purpose: The Gateway is a web server that handles all requests to Tableau Server from browsers, Tableau Desktop, and other clients Notes: Required on any node with an instance of VizQL Server or Vizportal. The Gateway is an Apache instance. Licensed: No single threaded? no Bound by: low resource consumption
Repository Server Processes Name/exe: ? Underlying Technology? Purpose: ? Notes: ? Licensed: ? single threaded?
Server Processes Name: pgsql/postgres.exe Underlying technology: PostgreSQL Purpose: The PostgreSQL repository is the main database for Tableau Server. It stores app data, usage data - users & what did they access, security objects - users, groups, permissions Notes: Limited to a maximum of two instances of the repository in a cluster, and must have at least three nodes in the cluster to add a second repository instance. Licensed: No single threaded? N/A Bound by: consumes few resources
Search and Browse Server Processes Name/exe: ? Underlying technology? Purpose: ? Notes: ? Licensed: ? Single threaded? Bound by?
Server Processes Name: searchserver/.exe Underlying technology? SOLR Purpose: handles fast search, filter, retrieval, and display of content metadata on the server. Searching in Web UI for name of workbook, etc But when you click data sources, repository is polled for all the details (metadata). Maintains an index of all content on Tableau Server Notes: N/A Licensed: No Single threaded? No Bound by: memory, then I/O
Application Server: Server Processes Name/exe: ? Underlying Technology? Purpose: ? Notes: ? Licensed: ? single threaded? Bound by?
Server Processes Name: vizportal, vizportal.exe Underlying technology: proprietary Purpose: Handles the web application, REST API calls, Authentication, Authorization, Publishing, and supports browsing and searching. Notes: When Application Server is installed, Data Engine is also installed, unless the node already has an instance of Data Engine. Licensed: Yes single threaded? No Bound by: infrequent resource consumption
VizQL Server Server Processes Name/exe: ? Underlying technology: Purpose: ? Notes: ? Licensed: ? Single threaded? Bound by? Scale - process, concurrent requests:
Server Processes Name: vizqlserver/.exe Underlying technology: Proprietary Purpose: The VizQL Server loads and renders views, computes and executes queries. Notes: When VizQL Server is installed, Data Engine is also installed, unless Data Engine is already installed on the node. In most situations you can change the number of VizQL instances on an existing node of a running server without causing a stop and restart of the server. An exception is if you are adding VizQL to an existing node that did not previously have VizQL or any other process that also installs Data Engine. Licensed: Yes Single threaded? No Bound by: CPU, I/O, network Scale: 1 per 25-50 concurrent requests, cores/4, increases throughput
Hardware Min for prototyping
Single Node: Ram: 16 gb CPU: 4 core Disk Space: 15 gb
Hardware Min for Production
Single Node: Ram: 32 gb CPU: 8-core, 2.0 ghz Disk Space: 50 gb
Flows: Publish a Workbook - Live Connection
Tableau Desktop generates thumbnail for WB and requests to upload and sends .twbx file Gateway receives request and passes to App Server App Server sends XML request to be stored in repository Repository stores thumbnails and workbook XML (data connection info) App server creates Publish Workbook dialog window Gateway sends response to User Publish Workbook Results displayed
Flows: Publish a Workbook - Extract
Tableau Desktop generates thumbnail for WB and requests to upload and sends .twbx file Gateway receives request and passes to App server App server sends XML to repository Repository stores XML and thumbnail and sends response to App server App server sends request to file store File store sends path to Repository and begins replicating to other nodes App Server creates Publish data source results window Gateway sends response to user Publish Workbook Results displayed
Flows: Publish a data source - Extract
Tableau Desktop requests to upload data source Gateway receives request and passes to App Server App Server sends XML to be stored in Repository Repository stores XML (data connection info) and passes back to App Server App server queries Data Engine Data Engine creates extract from hard drive and sends to File Store File store sends new file path to Repository and replicates on other nodes Repository stores new path to data source and returns request to Gateway Gateway sends response to user Publish Datasource Results is displayed
Flows: Publish a data source - live connection
Tableau Desktop requests to upload datasource Gateway receives request and passes to App server Application server sends request as XML to Repository Repository stores XML (connection info) and returns request to App Server App Server creates publish WB results Gateway send response to user
Drivers
https://www.tableau.com/support/drivers install on initial node and any node that runs Application server (vizportal), Backgrounder, Data Server, VizQL Server
tsm maintenance cleanup
use the ___ command to remove Tableau Server log files, temporary files, and rows from the http_requests table of the Tableau Server PostgreSQL database By default, deletes log files older than seven days, and temporary files. Command options can modify which files are deleted.