Informatica Big Data Management (BDM) Developer - 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 Informatica
Tool Name Big Data Management (BDM) Developer
Tool Version 9.x to 10.x
Tool Web Site https://www.informatica.com/products/big-data/big-data-edition.html
Supported Methodology [Data Integration] Multi-Model, Data Store (Logical Data Model), ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via Eclipse Java API on XML File
Data Profiling
Remote Repository Browsing for Model Selection
Multi-Model Harvesting
Incremental Harvesting

SPECIFICATIONS
Tool: Informatica / Big Data Management (BDM) Developer version 9.x to 10.x via Eclipse Java API on XML File
See https://www.informatica.com/products/big-data/big-data-edition.html
Metadata: [Data Integration] Multi-Model, Data Store (Logical Data Model), ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing)
Component: InformaticaDeveloperImport.InformaticaBigDataManagement version 11.0.0

OVERVIEW
This bridge imports Informatica Developer metadata objects from an XML file.

REQUIREMENTS
This bridge requires a Java version 1.6.

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
n/a


Bridge Parameters

Parameter Name Description Type Values Default Scope
File The bridge uses an XML file exported from Informatica Developer.

For example, to export one or more data models using Informatica Developer into an XML file:
1. Start the Developer tool.
2. From the 'File' menu, select the 'Export' menu item.
3. From the Export wizard, select 'Informatica', then 'Object Export File'.
4. Then, select a project, and the data model(s) to export.
5. Finally, specify the XML file location, name and click the 'Finish' button.

For more details about exporting and importing objects, refer to the Informatica documentation.

This bridge will use the generated XML file as input.
FILE *.xml   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

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Informatica Big Data Management (BDM) Developer"
Metamodel
InformaticaDeveloper
Mapping Comments
     
Association Reference  
Aggregation   computed from migrated FK attributes
Description Description  
Name Name  
AssociationRole Reference Two roles are created for each Reference
Multiplicity   set to 0..1 on the parent role, 0..* on the child role
Source   set to TRUE on parent role, FALSE on child role
AssociationRoleNameMap Reference created if FK attribute renaming occurs
Attribute Attribute  
Description Description  
InitialValue Default Value  
Name Name  
Optional Nullable  
Position Position  
BaseType Attribute Datatype BaseTypes are inferred from datatypes found in the model
DataType Datatype computed
CandidateKey Primary, Alternate Key  
Description Description  
Name Name  
UniqueKey   set to True
Class Logical Data Object  
CppClassType   set to ENTITY
CppPersistent   set to True
Description Description  
Name Name  
DerivedType Attribute Datatype  
DataType Datatype See datatype conversion arrays
Length Precision  
LowerBound Lower constraint  
Scale Scale  
UpperBound Upper constraint  
ForeignKey Reference  
StoreModel Model  
Description Description  
DesignLevel   set to LOGICAL_ONLY
Name Name