Using Anypoint Studio to Configure Tableau Connector 1.0 - Mule 4

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files.

To add and configure a connector in Studio:

Create a Mule project.
Add the connector to your Mule project.
Configure a source for the connector’s flow.
Add a connector operation to the flow.
Configure a global element for the connector.
Configure the other connector fields.

When you run the connector, you can view the app log to check for problems in real time, as described in View the App Log.

If you are new to configuring connectors in Studio, see Using Anypoint Studio to Configure a Connector. If, after reading this topic, you need additional information about the connector fields, refer to the Tableau Connector Reference.

Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

In Studio, select File > New > Mule Project.
Enter a name for your Mule project and click Finish.

Add the Connector to Your Mule Project

Add Anypoint Connector for Tableau (Tableau Connector) to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s pom.xml file:

In the Mule Palette view, click (X) Search in Exchange.
In the Add Dependencies to Project window, type tableau specialist in the search field.
Click Tableau Specialist Connector in Available modules.
Click Add.
Click Finish.

Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace.

Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources to use with Tableau Connector:

HTTP Listener
Initiates a flow each time it receives a request on the configured host and port
Scheduler
Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener source, follow these steps:

In the Mule Palette view, select HTTP > Listener.
Drag Listener to the Studio canvas.
On the Listener configuration screen, optionally change the value of the Display Name field.
Specify a value for the Path field.
Click the plus sign (+) next to the Connector configuration field to configure a global element that can be used by all instances of the HTTP Listener source in the app.
On the General tab, specify the connection information for the connector.
On the TLS tab, optionally specify the TLS information for the connector.
On the Advanced tab, optionally specify reconnection information, including a reconnection strategy.
Click Test Connection to confirm that Mule can connect with the specified server.
Click OK.

Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to perform.

To add an operation for Tableau Connector, follow these steps:

In the Mule Palette view, select Tableau Specialist and then select the desired operation.
Drag the operation onto the Studio canvas to the right of the source.

Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials that the connector requires to access the target Tableau system. Tableau Connector supports Hyper connection for the Hyper configuration, and Basic authentication and PAT authentication for the Rest configuration.

To configure the global element for Tableau Connector, follow these steps:

Select the operation in the Studio canvas.
In the configuration screen for the operation, click the plus sign (+) next to the Connector configuration field to access the global element configuration fields.
On the General tab, in Connection, select the authentication method to configure:
- Hyper Configuration
  - Hyper Connection
- Rest Configuration
  - Basic Authentication
  - PAT Authentication
You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your authorization credentials in the global configuration properties. For information about the benefits of using property placeholders and how to configure them, refer to Anypoint Connector Configuration.
On the Advanced tab, optionally specify reconnection information, including a reconnection strategy.
Click Test Connection to confirm that Mule can connect with the specified server.
Click OK.

Hyper Connection

Enter the following information on the General tab of the Global Element Properties screen to configure Hyper Connection:

Field User Action

Field	User Action
Name	Enter the configuration name.
Working Directory	Directory that is considered the root of every relative path used with this connector. If not provided, the value defaults to the value of the `user.home` system property. If that system property is not set, then the connector fails to initialize.
Hyperd Directory	Directory that makes the hyperd executable.
Telemetry	Enumeration, one of: SEND_USAGE_DATA_TO_TABLEAU DO_NOT_SEND_USAGE_DATA_TO_TABLEAU

Name

Enter the configuration name.

Working Directory

Directory that is considered the root of every relative path used with this connector. If not provided, the value defaults to the value of the user.home system property. If that system property is not set, then the connector fails to initialize.

Hyperd Directory

Directory that makes the hyperd executable.

Telemetry

Enumeration, one of:

SEND_USAGE_DATA_TO_TABLEAU
DO_NOT_SEND_USAGE_DATA_TO_TABLEAU

Basic Authentication

Enter the following information on the General tab of the Global Element Properties screen to configure Basic Authentication:

Field	User Action
Name	Enter the configuration name.
Server URL	URL of the Tableau server.
API version	API version to use.
Content URL	Content URL (subpath) of the site you sign into.
Username	Username used to initialize the session.
Password	Password used to authenticate the user.

Field

User Action

Name

Enter the configuration name.

Server URL

URL of the Tableau server.

API version

API version to use.

Content URL

Content URL (subpath) of the site you sign into.

Username

Username used to initialize the session.

Password

Password used to authenticate the user.

PAT Authentication

Enter the following information on the General tab of the Global Element Properties screen to configure PAT Authentication:

Field	User Action
Name	Enter the configuration name.
Server URL	URL of the Tableau server.
API version	API version to use.
Content URL	Content URL (subpath) of the site you sign into.
Personal Access Token Name	Personal access token name defined in the Tableau server UI. The personal access token name and personal access token secret are mutually exclusive with the Username and Password fields.
Personal Access Token Secret	Personal access token secret defined in the Tableau UI. The personal access token name and personal access token secret are mutually exclusive with the Username and Password fields.

Field

User Action

Name

Enter the configuration name.

Server URL

URL of the Tableau server.

API version

API version to use.

Content URL

Content URL (subpath) of the site you sign into.

Personal Access Token Name

Personal access token name defined in the Tableau server UI. The personal access token name and personal access token secret are mutually exclusive with the Username and Password fields.

Personal Access Token Secret

Personal access token secret defined in the Tableau UI. The personal access token name and personal access token secret are mutually exclusive with the Username and Password fields.

Configure Additional Connector Fields

After you configure a global element for Tableau Connector, configure the other required fields for the connector. The required fields vary depending on which connector operation you use.

View the App Log

To check for problems, you can view the app log as follows:

If you’re running the app from Anypoint Platform, the app log output is visible in the Anypoint Studio console window.
If you’re running the app using Mule from the command line, the app log output is visible in your OS console.

Unless the log file path is customized in the app’s log file (log4j2.xml), you can also view the app log in the default location MULE_HOME/logs/<app-name>.log.