Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page will guide you through the setup of Tableau Server in K using the direct connect method.

Integration details

Scope

Included

Comments

Metadata

Status
colourGreen
titleYES

Lineage

Status
colourGreen
titleYES

 

Usage

Status
colourGreen
titleYES

Sensitive Data Scanner

Status
titleN/A

...

Step 1) Tableau Server Configuration

The following Tableau server settings needs to be configured. This will require a restart of the tableau server.

Note

Changing these settings will require a restart of the tableau server.

...

Step 2) Setup Tableau APIs Access

  • A user needs to be configure to access Tableau API.

Info

The user can not be a SSO user. SSO users are not supported to access the Tableau APIs.must exists on tableau server as REST APIs do not support SSO. https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_auth.htm

  • User needs Site Administrator Creator or Server Administrator role, Roles are dependent on both Licensing and Server version see https://help.tableau.com/current/server/en-us/users_site_roles.htm

    • Site Administrator Creator is only available on Role Based Licensing Model

    • Server Administrator is available on both Role Based and Core Based Licensing Model

...

Step 3) Manually run an ad hoc load to test

  • Next to your new Source, click on the Run manual load icon

    image-20240520-123952.pngImage Added
  • Confirm how your want the source to be loaded

    Image Added
  • After the source load is triggered, a pop up bar will appear taking you to the Monitor tab in the Batch Manager page. This is the usual page you visit to view the progress of source loads

Info

A manual source load will also require a manual run of

  • DAILY

  • GATHER_METRICS_AND_STATS

To load all metrics and indexes with the manually loaded metadata. These can be found in the Batch Manager page

 

Warning

Troubleshooting failed loads

  • If the job failed at the extraction step

    • Check the error. Contact KADA Support if required.

    • Rerun the source job

  • If the job failed at the load step, the landing folder failed directory will contain the file with issues.

    • Find the bad record and fix the file

    • Rerun the source job

  • If you noticed that some reports do not have lineage