Skip to main content

Einstein Discovery on Tableau Server

 To Enable Einstein Discovery on Tableau Server  We need to enable Extension on Tableau Server . There are few Prerequisites and requirements to enable it. The whole process is described below. 

  1. CORS

A prerequisite for this is configuring CORS in Salesforce Org. Here is the process to enable CORS

  1. Sign in to your Salesforce.com developer account, click your user name in the upper-right, and then select Setup.

  2. In the left navigation column, search for "cors" and select CORS .

  3. In CORS, in the Allowed Origins List section, click New.

  4. In CORS Allowed Origin List Edit, enter the URL of your Tableau server, beginning with "https://".

    For more information about the URL pattern, see the Salesforce developer documentation: https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/extend_code_cors.htm

  5. Click Save.


Reference: https://help.tableau.com/current/server/en-us/config_cors_sfdc.htm


  1. OAUTH

If you are integrating Einstein Discovery extensions with Tableau Server, you need to do this OAuth client ID and secret configuration. The ability to integrate Einstein Discovery and Tableau Server was added in version 2021.1.0

Set up OAuth by following these general steps:

  1. Create a Connected App in Salesforce.

  2. Use the information you obtained in step 1 to configure Tableau Server.

  3. (Optional) Configure site-specific OAuth.

Step 1: Create a Salesforce connected app

Note: This procedure documents the process in Salesforce Lightning. If you are using the traditional interface, the navigation may be different but the configuration is the same.

  1. Sign in to your Salesforce.com developer account, click your user name in the upper-right, and then select Setup.

  2. In the left navigation column, under Apps, select App Manager.

  3. In the Connected Apps section, click New Connected App.

  4. In Basic Information, give the app a name, tab through the api field so it will self-populate in the correct format, and enter a contact email for the app.

  5. In the API [Enable OAuth Settings] section, select Enable OAuth Settings.

  6. In the new OAuth settings that appear, for Callback URL, type the fully qualified domain name of your server, using the https protocol, and append the following text to the URL: auth/add_oauth_token.
    For example:
    https://www.your_tableau_server.com/auth/add_oauth_token

  7. Move the following items from Available OAuth Scopes to Selected OAuth Scopes:

    • Access and manage your data (api)

    • Access your basic information (id)

    • Perform requests on your behalf at any time (refresh_token)

  9. Click Save.

After you save the app, Salesforce populates the API section with the following IDs that you will use to configure Tableau Server:

  • Consumer Key

  • Consumer Secret

  • Callback URL

Step 2: Configure Tableau Server for Salesforce.com OAuth

Once your connected app is created in Salesforce and you have the Customer Key, Customer Secret, and the Callback URL, you can configure Tableau Server for Salesforce data connections and outputs, and Einstein Discovery.

  1. On the Tableau Server computer, at a command prompt, run the following commands:
    tsm configuration set -k oauth.salesforce.client_id -v <your_customer_key>
    tsm configuration set -k oauth.salesforce.client_secret -v <your_customer_secret>
    tsm configuration set -k oauth.salesforce.redirect_uri -v <your_redirect_URL>

  2. (Optional) To change the default login server, type the following command:
    tsm configuration set -k oauth.salesforce.server_base_url -v <URL>

  3. Enter the following command to apply changes:
    tsm pending-changes apply
    If the pending changes require a server restart, the pending-changes apply command will display a prompt to let you know a restart will occur. This prompt displays even if the server is stopped, but in that case there is no restart. You can suppress the prompt using the --ignore-prompt option, but this does not change the restart behavior. If the changes do not require a restart, the changes are applied without a prompt. 

Configure custom OAuth for a site

You can configure a custom Salesforce OAuth client for a site.

Consider configuring a custom OAuth client to 1) override an OAuth client if configured for the server or 2) enable support for securely connecting to data that requires unique OAuth clients.

When a custom OAuth client is configured, the site-level configuration takes precedence over any server-side configuration and all new OAuth credentials created use the site-level OAuth client by default. No Tableau Server restart is required for the configurations to take effect.

Important: Existing OAuth credentials established before the custom OAuth client is configured are temporarily usable but both server administrators and users must update their saved credentials to help ensure uninterrupted data access.

Step 1: Prepare the OAuth client ID, client secret, and redirect URL

Before you can configure the custom OAuth client, you need the information listed below. After you have this information prepared, you can register the custom OAuth client for the site.

  • OAuth client ID and client secret: First register the OAuth client with the data provider (connector) to retrieve the client ID and secret generated for Tableau Server.

  • Redirect URL: Note the correct redirect URL. You will need this during the registration process in Step 2 below.
    https://<your_server_name>.com/auth/add_oauth_token
    For example, https://example.com/auth/add_oauth_token

Step 2: Register the OAuth client ID and client secret

Follow the procedure described below to register the custom OAuth client to the site.

  1. Sign in to your Tableau Server site using your admin credentials and navigate to the Settings page.

  2. Under OAuth Clients Registry, click the Add OAuth Client button.

  3. Enter the required information, including the information from Step 1 above:

    1. For Connection Type, select the connector whose custom OAuth client you want to configure.

    2. For Client ID, Client Secret, and Redirect URL, enter the information you prepared in Step 1 above.

    3. Click the Add OAuth Client button to complete the registration process.

  5. (Optional) Repeat step 3 for all supported connectors.

  6. Click the Save button at the bottom or top of the Settings page to save changes.

Step 3: Validate and update saved credentials

To help ensure uninterrupted data access, you (and your site users) must delete the previous saved credentials and add it again to use the custom OAuth client for the site.

  1. Navigate to your My Account Settings page.

  2. Under Saved Credentials for Data Sources, do the following:

    1. Click Delete next to the existing saved credentials for the connector whose custom OAuth client you configured in Step 2 above.

    2. Next to connector name, click Add and follow the prompts to 1) connect to the custom OAuth client configured in Step 2 above and 2) save the latest credentials.

Step 4: Notify users to update their saved credentials

Make sure you notify your site users to update their saved credentials for the connector whose custom OAuth client you configured in Step 2 above. Site users can use the procedure described in Update saved credentials to update their saved credentials.



  1. Enable Analytics Extension

Before you configure extensions, you must enable analytics extensions server-wide.

  1. Sign in to the Tableau Server Admin Area.

    • If you only have a single site (default) on your server, click Settings, and then go to Step 2.

    • If you have multiple sites on your server:

      1. Under All Sites, click Manage all sites.

      2. Click the Extensions tab.

  2. Scroll to Analytics Extensions, select Enable analytics extensions, and then click Save.


  1. Configure Analytics Extension

  1. Sign in to the Tableau Server Admin Area.

  2. On the Settings page, click the Extensions tab and then scroll to Analytics Extensions. (On multi-site deployments of Tableau Server, navigate to the site where you want to configure analytics extensions, and then click Settings>Extensions.)

  3. Multi-site deployments only: you must enable Analytics Extensions on each site. Under Analytics Extensions, select Enable analytics extensions for site.

  4. Under Analytics Extensions, click Create new connection.

  5. In the New Connection dialog, click the connection type you want to add, then enter the configuration settings for your analytics service:

  6. The options you need to configure depend on the connection type you choose:

    • For an Einstein Discovery connection, click Enable.

    • For TabPy, RServer and Analytics Extensions API connections, enter the following information:

      • Connection Name: (Required) Specify the server type you are connecting to. RSERVE supports connections to R using the RServe package. TABPY supports connections to Python using TabPy, or to other analytics extensions.

      • Require SSL (Recommended): Select this option to encrypt the connection to the analytics service. If you specify a HTTPS URL in the Hostname field, then you must select this option.

      • Hostname: (Required) Specify the computer name or URL where the analytics service is running. This field is case sensitive.

      • Port:  (Required) Specify the port for the service.

      • Sign in with a username and password(Recommended): Select this option to specify user name and password that is used to authenticate to the analytics service.

  7. Click Create.

Edit or delete an analytics extension connection

To edit or delete a configuration, navigate to Analytics Extensions on the Extensions tab of your site.

Click the Edit or Delete icon and follow the prompts to change the configuration

Labels

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