Talend Master Data Management (MDM) - Import - Cloud

Talend Cloud Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
Cloud
EnrichProdName
Talend Cloud
EnrichPlatform
Talend Data Catalog

Note: This bridge is not available in Talend Cloud Data Catalog by default. You need to set up a remote harvesting agent to import metadata from this source. For more information, see Deploying a remote harvesting agent in Talend Cloud Data Catalog Administration guide.

Bridge Requirements

This bridge:
  • requires the tool to be installed to access its SDK.

Bridge Specifications

Vendor Talend
Tool Name Talend Master Data Management (MDM)
Tool Version 5.x to 7.x
Tool Web Site https://www.talend.com/products/mdm/
Supported Methodology [Data Modeling] Data Store (Logical Data Model) via Eclipse Java API on XML XSD File
Data Profiling
Remote Repository Browsing for Model Selection
Multi-Model Harvesting
Incremental Harvesting

SPECIFICATIONS
Tool: Talend / Talend Master Data Management (MDM) version 5.x to 7.x via Eclipse Java API on XML XSD File
See https://www.talend.com/products/mdm/
Metadata: [Data Modeling] Data Store (Logical Data Model)
Component: TalendMdm version 11.0.0

OVERVIEW
This bridge imports data model as XSD Schema generated by Talend MDM.

REQUIREMENTS
The bridge relies on the Talend Data Fabric or Talend Open Studio for MDM tools.
Talend MDM Server is not supported.

The necessary plugins are installed as part of the tool. There is no extra SDK to install.

FREQUENTLY ASKED QUESTIONS
Q: Does the bridge have any 3rd party dependencies?
A: Yes. The bridge depends on a set of plugin files that you can find under your Talend Data Fabric's or Talend Open Studio for MDM's plugins directories in version 6.x.
Here is the list of ids for the required plugin files:

org.apache.commons.lang
org.apache.log4j
org.apache.xerces
org.eclipse.emf.common
org.eclipse.emf.ecore
org.eclipse.emf
org.eclipse.xsd
org.talend.datatools.xml
org.talend.mdm.commmon
org.talend.repository.mdm

Please configure the 'Installation directory' option to specify the Talend Data Fabric or Talend Open Studio for MDM installation path.

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 option -backup)


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Specify here the file path of the model to import. FILE *.xsd   Mandatory
Default Language Specify the language you would like to use. ENUMERATED
English
French
Spanish
Abkhazian
Afar
Afrikaans
Albanian
Amharic
Arabic
Armenian
Assamese
Aymara
Azerbaijani
Bashkir
Basque
Bengali (Bangla)
Bhutani
Bihari
Bislama
Breton
Bulgarian
Burmese
Byelorussian
Cambodian
Catalan
Chinese
Corsican
Croatian
Czech
Danish
Dutch
Esperanto
Estonian
Faeroese
Farsi
Fiji
Finnish
Frisian
Galician
Georgian
German
Greek
Greenlandic
Guarani
Gujarati
Hausa
Hebrew
Hindi
Hungarian
Icelandic
Indonesian
Interlingua
Interlingue
Inuktitut
Inupiak
Irish
Italian
Japanese
Yiddish
Javanese
Kannada
Kashmiri
Kazakh
Kinyarwanda
Kirghiz
Kirundi
Korean
Kurdish
Laothian
Latin
Latvian (Lettish)
Lingala
Lithuanian
Macedonian
Malagasy
Malay
Malayalam
Maltese
Manx Gaelic
Maori
Marathi
Moldavian
Mongolian
Nauru
Nepali
Norwegian
Occitan
Oriya
Oromo (Afan)
Pashto (Pushto)
Polish
Portuguese
Punjabi
Quechua
Rhaeto-Romance
Romanian
Russian
Samoan
Sangro
Sanskrit
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Shona
Sindhi
Singhalese
Siswati
Slovak
Slovenian
Somali
Sundanese
Swahili
Swedish
Tagalog
Tajik
Tamil
Tatar
Telugu
Thai
Tibetan
Tigrinya
Tonga
Tsonga
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Volapuk
Welsh
Wolof
Xhosa
Yoruba
Zulu
EN  
Import model as Specifies how to import the model from Talend MDM.

'Talend MDM'
Import Talend MDM model.

'Talend DI'
Import of the model same way as DI import bridge does. It needs for PDM to implement stitching.
ENUMERATED
Talend MDM
Talend DI
Talend MDM  
Installation directory The full path to the Talend Data Fabric or Talend Open Studio for MDM installation directory. The directory is used to search for proper JAR files used by the bridge.

For version 6.x, it should contain the 'plugins' directory.
DIRECTORY     Mandatory
Miscellaneous INTRODUCTION
Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="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
-m <Java Memory's maximum size>
1G by default on 64bits JRE or as set in conf/conf.properties, e.g.
-m 8G
-m 8000M

-j <Java Runtime Environment command line options>
This option must be the last one in the Miscellaneous parameter as all the text after -j is passed "as is" to the JRE, e.g.
-j -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.
-j -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass

-jre <Java Runtime Environment full path name>
It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-v <Environment variable value>
None by default, e.g.
-v var1=value1 -v var2="value2 with spaces"

MODEL IMPORT OPTIONS
-model.name <model name>
Override the model name, e.g.
-model.name "My Model Name"

-prescript <script name>
The script must be located in the bin directory, and have .bat or .sh extension.
The script path must not include any parent directory symbol (..).
The script should return exit code 0 to indicate success, or another value to indicate failure.
For example:
-prescript "script.bat arg1 arg2"

-cache.clear
Clears the cache before the import, and therefore will run a full import without incremental harvesting.
Warning: this is a system option managed by the application calling the bridge and should not be set by users.

-backup <directory>
Full path of an empty directory to save the metadata input files for further troubleshooting.

DATA CONNECTION OPTIONS
Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following options allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs.

-connection.cast ConnectionName=ConnectionType
Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g.
-connection.cast "My Database"="SQL SERVER".
The list of supported data store connection types includes:
ACCESS
CASSANDRA
DB2
DENODO
HIVE
MYSQL
NETEZZA
ORACLE
POSTGRESQL
PRESTO
REDSHIFT
SALESFORCE
SAP HANA
SNOWFLAKE
SQL SERVER
SYBASE
TERADATA
VECTORWISE
VERTICA

-connection.rename OldConnection=NewConnection
Renames an existing connection to a new name, e.g.
-connection.rename OldConnectionName=NewConnectionName
Multiple existing database connections can be renamed and merged into one new database connection, e.g.
-connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase

-connection.split oldConnection.Schema1=newConnection
Splits a database connection into one or multiple database connections.
A single database connection can be split into one connection per schema, e.g.
-connection.split MyDatabase
All database connections can be split into one connection per schema, e.g.
-connection.split *
A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g.
-connection.split MyDatabase.schema1=MySchema1

-connection.map DestinationPath=SourcePath
Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file).
On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a HIVE table implemented (external) by the same file specified using a relative path with default file name and extension, e.g.
-connection.map hdfs://host:8020/users/user1/folder/file.csv=/user1/folder
On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g.
-connection.map /users/John=/data -connection.map /users/paul=/data
On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g.
-connection.map M:\=C:\data -connection.map N:\=C:\data

-pppd
Create the connections and connection data sets in DI/ETL design models. This feature should only be used when intending to export to another DI/ETL tool.
STRING      

 

Bridge Mapping

Mapping information is not available