Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Informatica Data Engineering Integration (DEI) Developer

Bridge Specifications

Vendor Informatica
Tool Name Data Engineering Integration (DEI) 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

SPECIFICATIONS
Tool: Informatica / Data Engineering Integration (DEI) 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: InformaticaDeveloper 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 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

GENERAL 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.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.

-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 Data Engineering Integration (DEI) 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  

Last updated on Fri, 25 Sep 2020 17:37:51

Copyright © Meta Integration Technology, Inc. 1997-2020 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.