Profundus Health

HOME
ABOUT US
SERVICES
CLIENT SERVICE
CLINICAL RESEARCH
INFORMATION TECHNOLOGY
PRODUCT DEVELOPMENT
CLINICAL RESEARCH
CLINICAL DATA MANAGEMENT
CLINICAL OPERATIONS
MEDICAL WRITING
PHARMACOVIGILANCE
QUALITY CONTROL
STATISTICAL ANALYSIS SYSTEM
TECHNOLOGIES
DATA SCIENCE
INFORMATION TECHNOLOGY
SYSTEM APPLICATIONS AND PRODUCTS
TABLEAU
PARTICIPANTS
CAREER
CONTACT US

TABLEAU

TABLEAU

Profundus Health Technologies, gives extensive services on server administrators command-line and web-based options for configuring and maintaining Tableau Server, including performing administrative task like backing up server data, restoring backups, creating log archives, and managing multi-node clusters. It can perform the following tasks:

  • Initial configuration of Tableau Server after installation
  • Ongoing configuration management, including editing settings and changing the server topology
  • Running administrative tasks such as backup, restore, and zip-logs

For administrators familiar with earlier versions of Tableau Server, TSM replaces the following tools from previous versions of Tableau Server:

  • Tableau Server Configuration utility
  • Tab-admin command line utility
  • Tableau Server Monitor

TSM processes are administrative services which manage Tableau Server processes. TSM processes run continuously after TSM is initialized, even when the rest of Tableau Server is offline.

TSM processes that run, even when Tableau Server is stopped include:

  • Administration Agent
  • Administration Controller
  • Client File Service
  • Coordination Service
  • Service Manager
  • Licensing Service

Whether you use the TSM Web UI, the command line interface, or the TSM API, you need to authenticate to Tableau Server before you can perform administrative tasks. This user account is distinct from Tableau Server user accounts, including Tableau Server administrators and site administrators.

Profundus Health Technologies delegates authentication of users to the underlying operating system. On Linux, this means that authentication is handled using Pluggable Authentication Modules (PAM). PAM is the standard on all Linux distributions on which Tableau Server is supported. If your organization has configured PAM to authenticate with your directory service in this scenario, any authenticated PAM user that is a member of the admin group is authorized to access TSM.

Profundus Health Technologies uses the standard PAM login service to authenticate. You can further customize TSM authentication behaviour by creating a tableau PAM service file in etc., If this file exists, then it will be consulted instead of the PAM login service.

You authenticate to TSM with a user that exists on the Tableau Server computer. The TSM user account must use password-based authentication. By default, the TSM user account must be a member of the admin group on the computer where Tableau Server is running. Alternatively, you can specify a different authorization group for TSM administration. To specify a different default group during the install process, see Help Output for initialize Script. To specify a different authorization group after you have installed Tableau Server.

As a security measure, you can only connect to TSM with clients (CLI, Web UI, Rest API) over HTTPS. This is because TSM allows you to perform administrative tasks and to connect to TSM from other computers.

When you are connecting with a TSM client, you must connect to the Tableau Server instance running the TSM Administration Controller service.

TSM HTTPS connections rely on a self-signed certificate generated by the Tableau Server installer. This certificate is the Tableau installation CA certificate that signs the SSL certificates Tableau creates for encrypting traffic over HTTP. The Tableau installation CA certificate must be trusted by the systems connecting to TSM Administration Controller.

The TSM CLI client validates certificate trust from a different store than the TSM Web UI uses. The TSM CLI client refers to the trusted store in the local Java keystore to validate trust for CA certificates. Since the TSM Web UI must establish connection with a web browser, trust is validated with the operating system’s trusted keystore. The difference in how CA certificates are stored determines different trust configuration scenarios as outlined here:

  • For TSM CLI communications on Tableau Server, the certificate trust is configured by default as part of the installation, node bootstrap, and upgrade processes. The Tableau installation CA certificate is added to the trusted store in the Java keystore. This allows you to access TSM using the CLI from any computer in the cluster without additional configuration. However, when accessing TSM Web UI, the browser will prompt you to trust the host running TSM Administration Controller service.
  • For TSM CLI connections from remote computers, you will be prompted to trust the Tableau installation CA certificate the first time you connect to the Tableau Server running TSM Administration Controller.