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] Data Store (Logical Data Model) via Eclipse Java API on XML File |
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] Data Store (Logical Data Model)
Component: InformaticaDeveloperExport.InformaticaBigDataManagement version 11.2.0
OVERVIEW
Importing Informatica Developer metadata objects exported into XML format.
This export bridge requires a Java JVM version 1.6.
REQUIREMENTS
n/a
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 troubleshooting 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 | |||||||
| Version | Select here the version of the tool you want to connect to. This software version must be installed on the computer that is running this export bridge. |
ENUMERATED |
|
Latest | ||||||||
| File | This export bridge generates an XML file. In order to load the converted model into the Informatica Developer: For example, to export one or more data model using Informatica Developer into an XML file: 1. Start the Developer tool. 2. From the 'File' menu, select the 'Import' menu item. 3. From the Import wizard, select 'Informatica', then 'Objects'. 4. Then, select the XML file, and the target project. 5. Finally, click the 'Finish' button. For more details about exporting and importing objects, refer to the Informatica documentation. |
FILE | *.xml | Mandatory | ||||||||
| Installation directory | The full path to the Informatica Developer installation directory. The directory is used to search for proper JAR files used by the export bridge at runtime. | 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 |
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 | only associations with valid ForeignKey attributes are exported |
| Description | Description | |
| Name | Name | |
| AssociationRole | Reference | |
| AssociationRoleNameMap | Reference | used when FK attribute renaming occurs |
| Attribute | Attribute | |
| Description | Description | |
| InitialValue | Default Value | |
| Name | Name | |
| Optional | Nullable | |
| Position | Position | |
| BaseType | Attribute Datatype | only when used by attributes |
| DataType | Datatype | See datatype conversion arrays |
| Length | precision | |
| Scale | scale | |
| CandidateKey | Primary, Alternate Key | |
| Description | Description | |
| Name | Name | |
| Class | Logical Data Object | |
| Description | Description | |
| Name | Name | calculated using name and schema name if available |
| 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 | |
| Name | Name |