Skip to main content

Server Management Add-on

Server Management Add-on
  1.  Licensing
Server Management Add-on is licensed on a per Deployment basis, which may be User-Based or Core-Based. A Deployment includes a licensed production Tableau Server installation and two licensed non-production Tableau Server installations that support the production installation.
The Server Management Add-on can only be activated on a licensed Tableau Server Deployment
  1. Tools:
Server Management has multiple tools like Resource Monitoring Tools(RMT) and Content Migration Tool (CMT).
    1. Resource Monitoring tool 
Monitors the health of the server and identifies slow loads by analyzing logs and help in performance tuning. Proactive method to describe the issues.
An agent runs on each of the nodes in your Tableau cluster to monitor their performance and activity.this Agent has to be installed on every machine that runs Tableau server processes.
The Resource Monitoring Tool provides a web user interface for all of its features.
Resource Monitoring Tool can monitor multiple Tableau Server installations.Meaning, this can be used for both prod and non-prod installations on single tool installation.
The chart represented in the tool is a line chart with 80 point resolution for any period of time.
This is not available in Linux Installations.
The agent typically uses 200 MB RAM or less with infrequent spikes during periods of heavier Tableau Server activity.
The Processor, Memory, Disk Queue, and Network charts are all calculated and each point is an average of data collected for that period of time.
For Background process and concurrent users, each point is a summation of data collected.
A minimum of 10 GB free disk space is recommended for the agent.
      1. Hardware requirements:
8 physical CPU cores (16 vCPUs)
32GB RAM
500GB Disk Space (SSD is recommended)
The Resource Monitoring Tool Master Server hosts the web application that users interact with. It also does much of the background processing to collate and monitor the data from the agents
      1. Installation Prerequisites
  1. Admin privileges on the machines that includes all tableau server nodes and machine to install RMT
  2.  .Net Framework 4.6.2 or newer installed.
  3. port 5672,80 to be opened (TCP) for inbound traffice to collect data on the RMT Server
  4. port 5672,80 to be opened for outbound traffice on all nodes.
  5. Validate the connectivity between server to contact RMT server. The web interface hosted by the Master application is bound to a specific host name or IP address during the setup process. It will only answer requests sent to that specific host name. 
  6. Need Tableau Server Administrator Account to gather data using API
  7. For this to work, access to the repository must be enabled
  8. REST API has to be enabled
  9. SMTP server to send emails 
    1. Content Migration Tool:
Content Migration tool is used to Copy and migrate content between servers, projects, sites and deployments.
      1. prerequisites:
  • The Content Migration Tool must be installed on a version of Microsoft Windows that supports .NET 4.6.1 (Windows 7 or later, Windows Server 2008R2 or later).
  • REST API enabled on both source and target
      1. Installation:
To install Content Migration Tool:
  • Run the Content Migration Tool Setup program.
  • After reading the EULA, select I agree to the license terms and conditions, and click Install.
  • If the User Account Control dialog opens, click Yes to allow the installer to make changes.
      1. Migration Plan :
  • sign into the source server and the destination server.
  • You can only migrate content that the user has access to.The user account used to sign in to the source/Target must have an Interactor or Explorer role or higher, and the following permissions for the content you want to migrate:
  • View
  • Download/save as
  • Optional: Admin (to select workbooks, to access a user list)
  • For Target site, userid needs Publishing permission
  • Connections with Saved passwords will be prompted for password while migrating.
You can specify the content by selecting particular object or all objects like projects, workbooks.
It has multiple steps.
1.projects
2.workbooks
3.workbook transformations
4.datasource transformations
5.publishing options
You can perform actions like workbook mappings to destination like renaming,changing workbook names and locations. 
Also modify workbooks using transformations like replacing URL, change parameter value, changes to images, urls and txts in workbooks.
Datasource Transformations includes Replace table/schema, remove extract, set custom SQL, calculation formula, display name, connection information
The final step in the Workbooks phase is to select publish options and create transformations for tags, extract refresh schedules, and permissions.
By default, when you use the Tableau Content Migration Tool to migrate a workbook or data source that contains an extract, that extract is migrated along with the workbook or data source that contains it.
The Content Migration Tool gives you a couple options for controlling this behavior:
  • Switching to a Live Connection
  • Refreshing Extracts after Migration
Datasource connection modification can be done using the Content Migration Tool Set Connection Info transformation in migration plan.
Option 1: Use Published Data Sources
You can change your workbooks so that they use published data sources instead. This way, the extract will be managed as part of the published data source and migrating updates to the workbooks that use that data source can be simplified by not having to worry about the connection to the live database or the data extract.
Option 2: Remove the Extract During Migration
You can add a Remove Extract transformation to your migration plan. This will remove the extract from your workbook, effectively switching the data source to a live connection.
Option 3: Refresh the Extract After Migration
You can use the Refresh Extracts After Migrationoption in your migration plan. This will migrate the extract along with workbook but will schedule an immediate extract refresh task for that workbook after the migration is complete.
      1. Limitations of Migrations
The following user configurations from the source site will not be migrated to the destination site when using the Content Migration Tool.
  • Data-driven alerts
  • Subscriptions
  • Custom views
  • Favorites
  • Comments
The following server-level configurations from the source site will not be migrated to the destination site when using the Content Migration Tool:
  • Users
  • Project permissions and locked state
  • Site settings
Tableau Prep flows published to the source site are not migrated to the destination site when using the Content Migration Tool. To run flows on a schedule and refresh the flow output using Tableau Prep Conductor, users must republish flows to the destination site with Tableau Prep Builder
Workbooks and views that are migrated using the Content Migration Tool will retain their original thumbnails, even if the migration plan includes transformations that result in the views being rendered differently (for example, if data connections change). To update thumbnails, edit the workbook or view on the destination site and re-save it.



This will have more content added in future.

Labels:

Comments

Post a Comment

Popular posts from this blog

Gateway port to use 80 to 443 on Tableau Server

Change Gateway port from 80 to 443 or 8080       To change the Gateway port from 80 to 443 then use below commands First , list your nodes with the command. tsm topology list-node  Then execute the command to set port  tsm topology set-ports --node-name node1 --port-name gateway:primary --port-value 443 The above command will ask for a restart.  Check ports using  tsm topology list-ports  If some error occurs in applying changes: try disabling (enable later) external ssl first- tsm security external-ssl disable You might need to run init command again with new port- tsm reset tabcmd initialuser --server localhost:443 --username 'ADMINUSER' --password 'adminpwd'
Post a Comment
Read more

Creating Groups using Tableau API and Python Script

 Creating Tableau Groups using Python and API Prerequisites: Python on the machine tableauserverclient module API enabled on Tableau server. Permissions to update for the user Groups.csv file . list all groups in a csv file Changes to be made in the script for below lines in the script groups = open('<Filepath>/groups.csv') pat='getyourpersonaltoken' server = TSC.Server('http://myserver.tableau.com',use_server_version=True) tokenName = 'mytokenname' Script: import tableauserverclient as TSC import csv groups = open('<Filepath>/groups.csv') grp = csv.reader(groups) sourcegroups=[] createdgrps=[] pat='getyourpersonaltoken' server = TSC.Server('http://myserver.tableau.com',use_server_version=True) tokenName = 'mytokenname' ta = TSC.PersonalAccessTokenAuth(token_name=tokenName, personal_access_token=pat) with server.auth.sign_in_with_personal_access_token(ta):    groupslist, pagination_item  = server.groups.get() ...
Post a Comment
Read more

Tableau dirty Backup

Steps for performing a dirty restore 1. Install Tableau Server 2019.1.0 on the Dev machine 2. Stop Tableau Server 3. Copy the following folders from the current production: D:\Tableau Server\data\tabsvc\pgsql D:\Tableau Server\data\tabsvc\dataengine 4. Update the pg_hba.conf D:\Tableau Server\data\tabsvc\config\pgsql_0.<version>/pg_hba.conf Change "md5" to "trust" for the user "tblwgadmin" like this: host    all         tblwgadmin         <address>/32          md5 to : host    all         tblwgadmin        <address>/32         trust 5. Regenerate the internal token: tsm security regenerate-internal-tokens [options] [global options] tsm pending-changes apply 6. Re-index tsm maintenance reindex-search 7. Make a proper backup: tsm maintenance backup -f myBackup At this point, we w...
Post a Comment
Read more