Bridge Specifications
| Vendor | Informatica |
| Tool Name | PowerCenter |
| Tool Version | 8.x to 10.x |
| Tool Web Site | https://docs.informatica.com/data-integration/powercenter/ |
| Supported Methodology | [Data Integration] Multi-Model, ETL (Source and Target Data Stores, Transformation Lineage, Expression Conversion) via XML File |
SPECIFICATIONS
Tool: Informatica / PowerCenter version 8.x to 10.x via XML File
See https://docs.informatica.com/data-integration/powercenter/
Metadata: [Data Integration] Multi-Model, ETL (Source and Target Data Stores, Transformation Lineage, Expression Conversion)
Component: InformaticaPowerCenter version 11.2.0
OVERVIEW
Importing Informatica PowerCenter metadata objects exported into XML format.
Exporting Informatica PowerCenter objects (sources, targets, mappings or workflows) can be done From the Informatica PowerCenter RepositoryManager tool by selecting the appropriate object or group of objects in the tree control on the left and click 'Repository'->'Export Objects...' menu.
For more details on the object export please refer to the Informatica PowerCenter User Guide.
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
Q: What PowerCenter transformations are supported by this bridge?
A: The bridge currently supports these primary transformations: Readers, Writers, Expressions, Aggregations, Lookups, Joins, and Filters. Any others will be undefined.
LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/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 | |||||||||
| File | This bridge generates an XML file. In order to load the converted model into the PowerCenter repository: 1 - Start PowerCenter Designer 2 - Choose Import Objects... from the Repository menu. 3 - Select the XML file generated by this bridge and import it into the PowerCenter repository For more details about exporting and importing objects, see 'Exporting and Importing Objects' in the Informatica Repository Guide. |
FILE | *.xml | Mandatory | ||||||||||
| Export objects | Specify whether you want to export tables as sources or targets. | ENUMERATED |
|
Tables as sources | ||||||||||
| Export folders | Specify whether you want to export source model folders as Informatica folders or export all objects into a single folder. | BOOLEAN |
|
True | ||||||||||
| Database type | Specify the database type. 'Auto detect' Will try to auto-detect the target database from the originating model. The bridge uses the database type information to map data types appropriately. |
ENUMERATED |
|
Auto Detect | ||||||||||
| Database name | Specify the database name. PowerCenter allows you to group tables by database in the Navigator. The bridge places all tables under the group name if it is specified. Otherwise, the bridge will generate the group names according to the table's database information. |
STRING | ||||||||||||
| Codepage | Specify the codepage of the Informatica PowerCenter Repository. | STRING | MS1252 | |||||||||||
| XML Indentation (pretty printing) | Controls the pretty printing of XML, for the purpose of opening the generated file in a text editor. E.g. 'space characters' Several space characters as indentation. 'tab key' Tab character as indentation. 'empty' No indentation which leads to a more compact file. |
STRING | ||||||||||||
| Export Metadata Extensions | Allows to export additional descriptions, comments or notes as Informatica PowerCenter Metadata Extensions. | BOOLEAN |
|
True | ||||||||||
| Path to the Informatica installation | Enter the path to the Informatica PowerCenter client binary files. Typically a path would look like, e.g. F:\\Informatica\\PowerCenter8.6.0 In order to locate the correct path, be sure that the 'client' and 'java' directories are present in the path. If this parameter is not specified, the bridge will not generate Java byte code for business rules. |
DIRECTORY | ||||||||||||
| 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 PowerCenter" Metamodel InformaticaPowerCenter |
Mapping Comments |
| Association | The foreign key information is exported | |
| AssociationRole | The foreign key information is exported | |
| AssociationRoleNameMap | SourceField, TargetField | |
| Attribute | SourceField, TargetField | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| Name | BusinessName | Attribute Name. Computed if not set |
| NativeId | Comment | Mapped only if comment is empty. |
| Optional | Nullable | |
| PhysicalName | Name | Attribute Physical Name.Computed from 'name' if not set |
| Position | FieldNumber | |
| Stereotype | Comment | Mapped only if comment is empty. |
| BaseType | SourceField, TargetField | |
| DataType | Datatype | See datatype 'DataType Mapping' worksheet |
| CandidateKey | SourceField, TargetField, TargetIndex | |
| UniqueKey | KeyType, TargetIndex.Unique | |
| Class | Source, Target | |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| DimensionalRole | dimensional Role metadata extension | |
| DimensionalType | dimensional Role Type metadata extension | |
| Name | BusinessName | Class Name. Computed if not set |
| PhysicalName | Name | Class Physical Name.Computed from the 'name' if not set |
| DatabaseSchema | Source, Target | Tables and views belonging to the owner |
| Name | DBD name | for sources only |
| DerivedType | SourceField, TargetField | |
| DataType | Datatype | See datatype 'DataType Mapping' worksheet |
| Length | Precision | |
| Scale | Scale | |
| DesignPackage | Source, Target | Package hierarchy is flatten |
| Name | DBDName | Unique name. If the original package name was not unique a numeric suffix is added to make it unique |
| ForeignKey | SourceField, TargetField | |
| Index | TargetIndex | |
| Generate | if set to false the index is not exported | |
| Name | Name | |
| IndexMember | TargetIndexField | use linked attribute's name for the target index field name |
| Position | position in XML file | |
| SQLViewAttribute | SourceField, TargetField | Used to find the associated class attribute |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| Name | BusinessName | View Name. Computed if not set |
| PhysicalName | Name | View Physical Name.Computed from the 'name' if not set |
| Position | The attributes are ordered by position in the XML file | |
| SQLViewEntity | Source, Target | Views might be inconsistent if objects have been renamed. |
| Comment | Comment | |
| Description | Comment | Mapped only if comment is empty. |
| Name | BusinessName | View Name. Computed if not set |
| PhysicalName | Name | View Physical Name.Computed from the 'name' if not set |
| StoreModel | FolderVersion | Used an XML mandatory parent element for Source and Target tables |
| Name | DBDName | for table objects that are not in a user defined package |