Skip to main content

[Tableau] How to install Tableau Server on Centos 7 / Redhat

Step 1: Install Tableau Server package and start Tableau Services Manager

1. Log on as a user with sudo access to the computer where you want to install Tableau Server.

2. Downalod installer from below Tableau download page.
https://www.tableau.com/products/server/download/linux

// use WINSCP or any preferred utility to move Tableau Server installation file to Centos.



3. Use the package manager to install the Tableau Server package.

sudo yum update
sudo yum install tableau-server-<version>.x86_64.rpm

--
Non-default location—To install to a non-default location, you must use rpm -i. You will also need to install all dependent packages. See the note below.
Run the following command:
sudo rpm -i --prefix /preferred/install/path tableau-server.rpm

Refer to https://onlinehelp.tableau.com/current/server-linux/en-us/setup.htm
--

4. Navigate to the scripts directory:
cd /opt/tableau/tableau_server/packages/scripts.'version'/

5. Run the following script to start TSM:
sudo ./initialize-tsm --accepteula

--
The -d flag to specify a non-default location of the "data directory" where Tableau Server stores extracts, information about extracts, and more.
By default, Tableau Server uses the following location for the directory:
/var/opt/tableau/tableau_server

Refer to https://onlinehelp.tableau.com/current/server-linux/en-us/setup.htm
--

6. After initialization is complete, close the terminal session:
exit or logout
source /etc/profile.d/tableau_server.sh


**Firewall**
Single-node configuration
1. Open a bash shell and run the following TSM command to retrieve the port number for the tabadmincontroller port:

tsm topology list-ports

Make a note of the tabadmincontroller port. By default, this port is 8850.

2. Start firewalld:
sudo systemctl start firewalld

3. Verify that the default zone is a high-security zone, such as public. If it is not, we recommend changing it to a high-security zone.
sudo firewall-cmd --get-default-zone
sudo firewall-cmd --set-default-zone=public

4. Add ports for the gateway port and the tabadmincontroller port. In the example below we use the default ports (80 and 8850).
sudo firewall-cmd --permanent --add-port=80/tcp
sudo firewall-cmd --permanent --add-port=8850/tcp

5. Reload the firewall and verify the settings.
sudo firewall-cmd --reload
sudo firewall-cmd --list-all


Step 2: Activate and register Tableau Server

Before you can configure Tableau Server you must activate a license and register.

1. Log on as a user with sudo access and log in to TSM. Run the following command:
tsm login -u <username>

2. Activate the Tableau Server license. Run the following command:
tsm licenses activate -k <license_key>
tsm licenses list

3. Register Tableau Server. Generate a template that you can edit by running the following command:
tsm register --template > /path/to/registration_file.json

-- sample is attached as below.
tsm register --template > ./regi.json
vi regi.json

--example
{
"zip" : "2000",
"country" : "AU",
"city" : "Sydney",
"last_name" : "Whoknows",
"industry" : "IT",
"eula" : "yes",
"title" : "System Engineer",
"phone" : "82825959",
"company" : "Example",
"state" : "NSW",
"department" : "Engineering",
"first_name" : "NoName",
"email" : "test@test.com"
}

4. Open a text editing program, fill in the registration file, save it, then pass it with the following command:
tsm register --file /path/to/registration_file.json

tsm register --file ./regi.json

Step 3: Configure local identity store
You must configure the identity store settings. This procedure simplifies installation setting identity store to local authentication. Workbook examples are installed by default. For more details on customizing these defaults, see Configure Initial Node Settings.

○ Pass the configuration file with the following command:
tsm settings import -f /opt/tableau/tableau_server/packages/scripts.<version>/config.json

{
  "configEntities": {
    "identityStore": {
      "_type": "identityStoreType",
      "type": "local"
    }
  }
}


Step 4: Finalize installation
The final steps of installation are to apply changes, initialize and start TSM, and then to create the administration account. More details about these steps are at Configure Initial Node Settings.

1. Apply the configurations you made in the previous steps. Run the following command:
tsm pending-changes apply

2. Initialize and start Tableau Server. Run the following command:
tsm initialize --start-server --request-timeout 1800

3. Create the Tableau Server administrator account. Run the following command:
tabcmd initialuser --server 'localhost:80' --username 'admin' --password '<password>'

Where '<password>' is a strong password. Enclose the password and other arguments in single quotes.
Use the admin account that you created to access the Tableau Server admin web pages.
See Sign in to Tableau Server Admin Pages.


Step 5: Install PostgreSQL drivers
To validate that Tableau Server is installed and running properly and to review the built-in administrative views, you must install the PostgreSQL driver.

1. Download PostgreSQL drivers from the Driver Download page.
2. Install the drivers on your Tableau Server computer:
i. Download the .rpm file.
wget https://downloads.tableau.com/drivers/linux/yum/tableau-driver/tableau-postgresql-odbc-09.06.0500-1.x86_64.rpm

ii. To install the driver, run the following command:
sudo yum install tableau-postgresql-odbc-9.5.3-1.x86_64.rpm

3. To validate that the drivers installed, navigate to the Administrative Views in Tableau Server.


** Yotube Demo


Comments

Popular posts from this blog

How to configure LDAPS, LDAP over SSL, using CA Certificate Service on Domain Controller in Windows Server 2016

This post is to provide an instruction on how to set up LDAPS (LDAP over SSL) on Domain Controller using single-tier CA hierachy. Reasons for Enabling LDAPS By default, LDAP communications between client and server applications are not encrypted. This means that it would be possible to use a network monitoring device or software and view the communications traveling between LDAP client and server computers. This is especially problematic when an LDAP simple bind is used because credentials (username and password) is passed over the network unencrypted. This could quickly lead to the compromise of credentials.  Reasons for enabling Lightweight Directory Access Protocol (LDAP) over Secure Sockets Layer (SSL) / Transport Layer Security (TLS) also known as LDAPS include: Some applications authenticate with Active Directory Domain Services (AD DS) through simple BIND. As simple BIND exposes the users’ credentials in clear text, use of Kerberos is preferred. If simp...

[AD LDAP] How to install LDAP in AD in Windows Server 2019 in VirtualBox