Tableau (File) - Export - 7.3

Talend Data Catalog Bridges

Version
7.3
Language
English
Product
Talend Cloud
Module
Talend Data Catalog
Last publication date
2023-08-17

Bridge Specifications

Vendor Tableau
Tool Name Tableau Desktop
Tool Version 8.x to 2023.x
Tool Web Site https://www.tableau.com/products/desktop
Supported Methodology [Business Intelligence] BI Report (Relational Source, Expression Parsing, Report Structure) via XML File

SPECIFICATIONS
Tool: Tableau / Tableau Desktop version 8.x to 2023.x via XML File
See https://www.tableau.com/products/desktop
Metadata: [Business Intelligence] BI Report (Relational Source, Expression Parsing, Report Structure)
Component: Tableau version 11.1.0

OVERVIEW

REQUIREMENTS
This export bridge generates .tds Data Source XML files.

This export bridge converts a Data Model into multiple Tableau files.
- if the model is using dimensional modeling notation (tables marked as Fact, Dimension or Outrigger), it will generate one Tableau Data Source file representing each star, centered on a Fact table, with its connected Dimension tables around it.
- if the model is not using dimensional modeling notation, it will split the model and generate one file per schema, and for each island of tables connected by Foreign Keys.

If such Data Source files already exist in the target directory, the export bridge can update such DataSources and add descriptions as well as business names from the source model.
In such update mode, the export bridge uses the file name as identifier of the fact or dimension table to match with in the model.

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).


Bridge Parameters

Parameter Name Description Type Values Default Scope
Directory Specify an empty directory here, to generate new Data Source files, or a directory with existing .tds files to update.

These data source files can then be opened with the Tableau Desktop application where user can either:
- Publish them to a Tableau Server
- Connect a data source to the actual data, build a report and make it embedded.

For more information about published and embedded datasources please refer to: http://onlinehelp.tableau.com/current/server/en-us/datasource_about.htm).
DIRECTORY     Mandatory
Miscellaneous INTRODUCTION
Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="MICROSOFT SQL SERVER"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.
ETL/Miscellaneous.txt

JAVA ENVIRONMENT OPTIONS
-java.memory <Java Memory's maximum size> (previously -m)

1G by default on 64bits JRE or as set in conf/conf.properties, e.g.
-java.memory 8G
-java.memory 8000M

-java.parameters <Java Runtime Environment command line options> (previously -j)

This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g.
-java.parameters -Dname=value -Xms1G
The following option must be set when a proxy is used to access internet (this is critical to access https://repo.maven.apache.org/maven2/ and exceptionally a few other tool sites) in order to download the necessary third-party software libraries.
Note: The majority of proxies are concerned with encrypting (HTTPS) the outside (of the company) traffic and trust the inside traffic that can access proxy over HTTP. In this case, an HTTPS request reaches the proxy over HTTP where the proxy HTTPS-encrypts it.
-java.parameters -java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass

-java.executable <Java Runtime Environment full path name> (previously -jre)

It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-java.executable "c:\Program Files\Java\jre\bin\javaw.exe"

Some API based bridges (e.g. JDBC) may require a SSL / TLS based secure connection, no setup is needed when using an official certificate signed by a Certificate Authority (CA). However, when using a self signed certificate, then such a certificate needs to be imported in your java environment (before restarting your Java application) typically as follows:
cd $JAVA_HOME/jre/lib/security
mv jssecacerts jssecacerts.old
$JAVA_HOME/bin/keytool -importkeystore -srckeystore {your_keystore} -keystore jssecacerts

-environment.variable <name>=<value> (previously -v)

None by default, e.g.
-environment.variable var2="value2 with spaces"
STRING      

 

Bridge Mapping

Mapping information is not available