As we attempt to master the latest Tableau BI software to learn about the new BI tool, it’s essential to know about Tableau structure. If you know what’s underneath the hood, you’ll be able to develop an understanding of the technical aspects of the application. In this article we’ll go over the Tableau architecture in depth. This will be followed by a general understanding of Tableau’s functions. In addition we will be able to understand the components along with the Architecture for Tableau Server. If you dont have any Prior knowledge on Tableau architecture the a brief TableauTableau Server Course will help you enhance your knowledge.
Are you now ready to discover Tableau Architecture?
First, let’s make the larger picture clear in our minds; then let’s speak about the whole architectural framework Tableau operates within. It is classified into three distinct segments. The segments include –
- Data Sources
- Tableau Server
- Tableau Desktop and the clients.
- Data Source
The initial section of Tableau structure is where users are able to get data from a range of options for data sources such as SAP, Oracle, Salesforce, Excel file, MySQL, Teradata etc. The user can establish a data connection using two methods: live data connections which instantly sends queries to the source and immediately receives the results. Another option is to collect information from the source and keep an individual copy of the data to serve as an interim database. Data can be downloaded via live connections or extracted from the two databases Tableau Desktop and Tableau Server.
1. Tableau Server and Desktop
Before moving on to Tableau Server Let’s first look at the
Tableau Desktop as the platform that users get the ball rolling to allow for other actions to occur. Based on the request of the user, the actions of elements of the architectural system are set. Tableau Desktop is an authoring tool that lets users can create workbooks, visualizations and dashboards based on the data coming from Tableau Desktop, the sources of data in Tableau. These workbooks and visualizations are shared with users in a variety of ways. It could be shared with individuals who aren’t using it (just to be viewed) as well as to web or mobile device Workbook packages are shared to users of the Tableau Reader where users can see and modify the visualizations. The visualizations can also be loaded or published into it’s Tableau Server.
Tableau Server: Tableau Server has many components that work together to manage various crucial processes. It has parts taking care of the user and data security, a repository which stores all the visualizations published to the Server, a cache for performance improvement, a manager/automation to manage data loads and schedule updates, a presentation layer that is responsible for all the visualization/presentation related activities. It is the Tableau Server primarily serves the large and dynamic base of web and mobile users who interact with data via Tableau platforms.
The clients are the final users of Tableau via a web or mobile device in-cloud, on-premise or via a command line interface to development. They interact via Tableau Server for accessing workbooks or other visualizations. The server components will then function according to the request of the client and provide the result.
Tableau Server Components
As discussed, Tableau Server is an essential component of the Tableau architecture since it has been carefully designed to control and run crucial processes. It is crucial to know what’s going on inside Tableau Server since it’s an essential component that helps to better understand Tableau more thoroughly.
Let’s go over the various components in Tableau Server and discover how they function.
Gateway is a form of web-server that lets clients communicate with the server using HTTP as well as HTTPS. The server is able to receive incoming requests and redirects them to the right server to take actions. Gateways handle procedures like load balancers, traffic routing, URL writing and providing static file downloads to customers, and serving multi-thread processes as well as other processes. The gateway server that is used in Tableau Tableau includes Apache Tomcat.
2. Application Server
Gateway communicates with applications servers, which is also called a workgroup server. The application server handles the login process, domain authentication as well as data authorization, group or user permission management, content search and other such. It operates in close coordination with the server’s repository , and handles data access operations. It also renders the operations that are related to the user interface in addition to the visualizations , which are the job for VizQL. VizQL server. It is the user’s interface webpage that provides users with an overview of their workbooks and projects that they are able to access.
The repository within Tableau Server stores server metadata that pertains to permissions, users assignment, groups and projects. In addition to the metadata, it also stores visualizations in plain files (TWS, TDS), and performance data to aid in auditing. If a server application or component requires metadata, it’s provided by the repository. Additionally, it works together with the directory active to supply valuable information to the application server to verify logins.
4. VizQL Server
It is a crucial element of Tableau Server since it loads all visualizations you can see and use on Tableau. It comes with an inbuilt caching feature to improve performance and edit tasks. If a user makes a request for an image or wants to modify any existing visualization, the query made by VizQL is converted to an SQL statement before being sent into the respective data source through the appropriate data source driver. The data requested by the source is sent into the VizQL server once more after which it is completed with a few last adjustments to the calculations, and then delivered directly to users. Any new visualization generated by sources of data is saved in VizQL to be used later on.
5. Data engine
Data engine an powerful component that manages procedures that are related to Tableau information extraction (TDE). It’s activated only when the query is executed that requires information that comes from TDE. The data engine can store several TDEs and is able to run on two servers (maximum). It can also handle multiple requests simultaneously at any given time. The data engine stores the data in memory taken from the TDE when it receives an inquiry by the client.
Backgrounder is an important multi-process, multi-process element that controls schedules for information refresh and assures the correct operation for it. Tableau Server and Data Engine.
7. Data Server
The data server assists in centralizing the management of metadata as well as driver deployment and manage extracts. It also aids in access control and acts as a proxy for data sources. It also hosts the user’s queries and queries to stop users from accessing directly to the source of data.
8. Search and License
The other two crucial components are search and license. The search component handles the indexing of searches for information in the repository. While the licensing component handles setting up and licensing on the Tableau server. Both of these services are run on the main server of Tableau’s server cluster.