Install the Couchbase Tableau Connector on Tableau Server
- how-to
You can install the Couchbase Tableau Connector on Tableau Server.
This enables publishing of reports and workbooks that are created on Tableau Desktop to a Tableau Server project. The connector also allows users to publish the data sources they created on Tableau Desktop with the Couchbase Tableau Connector to Tableau Server. Other users with access to the project can build their own reports and workbooks using the same data sources.
|
Install the Connector on Tableau Server for Windows
On Windows:
-
Copy the
.tacofile intoC:\ProgramData\Tableau\Tableau Server\data\tabsvc\vizqlserver\Connectors. -
Copy the
.jarfile intoC:\Program Files\Tableau\Drivers. -
To apply the changes and install the connector, run the following command.
tsm pending-changes apply
Install the Connector on Tableau Server for Linux
On Linux:
-
Copy the
.tacofile into/var/opt/tableau/tableau_server/data/tabsvc/vizqlserver/Connectors. -
Copy the
.jarinto/opt/tableau/tableau_driver/jdbc. -
To apply the changes and install the connector, run the following command.
$ tsm pending-changes apply
Verify the Connector Installation
To verify if the Couchbase Tableau Connector is installed correctly:
-
Log in to Tableau Server.
-
Go to .
Here, you should now see the option to select Operational Insights by Couchbase.
Configure SSL Certificates for Tableau Server
If you use a certificate from a trusted public certificate authority (CA), no manual SSL configuration is required.
If you use a certificate from a private CA or require client certificate authentication, you must configure a properties file as follows.
-
Create a file named
couchbase-operational-insights.propertiesand save it in the following directory:- Windows
-
Save the file to
ProgramData\Tableau\Tableau Server\data\tabsvc\vizqlserver\Datasources - Linux
-
Save the file to
/var/opt/tableau/tableau_server/data/tabsvc/vizqlserver/Datasources/
-
To trust a certificate from a private CA, specify the path to the certificate using
sslCertPath.The certificate must be a PEM-encoded file.
sslCertPathreplaces the default trust store instead of adding to it.sslCertPath=<path to your PEM-encoded CA certificate>The connector does not support the sslKeystorePathandsslKeystorePasswordproperties and ignores them if specified. -
To authenticate using a client certificate, configure either PEM files or a keystore.
- PEM Files
-
clientCertPath=<path to client certificate pem> clientKeyPath=<path to client key pem> # Optional; required only if the private key is encrypted clientKeyPassword=<private key password> - Keystore
-
clientCertKeystorePath=<path to keystore file> clientCertKeystorePassword=<keystore password>The keystore must contain exactly one entry.