Informatica PowerCenter - Export - 7.1

Talend Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

Bridge Specifications

Vendor Informatica
Tool Name PowerCenter
Tool Version 8.x to 10.x
Tool Web Site http://www.informatica.com/products_services/powercenter/Pages/index.aspx
Supported Methodology [Data Integration] Multi-Model, ETL (Source and Target Data Stores, Transformation Lineage, Expression Conversion) via XML File

Export tool: Informatica PowerCenter 8.x to 10.x (http://www.informatica.com/products_services/powercenter/Pages/index.aspx)
Export interface: [Data Integration] Multi-Model, ETL (Source and Target Data Stores, Transformation Lineage, Expression Conversion) via XML File to Informatica PowerCenter Export bridge: 'InformaticaPowerCenter' 10.1.0

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 refere to the Informatica PowerCenter User Guide.

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.


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
Sources, targets and mappings
Tables as sources
Tables as targets
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' means that the bridge 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
Oracle
DB2
Microsoft SQL Server
ODBC
Teradata
Informix
Sybase
Flat File
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.

The default codepage is MS1252.
STRING   MS1252  
XML Indentation (pretty printing) This option controls the pretty printing of the XML, for the purpose of opening the generated file in a text editor.

For example, specify here a tabulation character, or some space characters.

By default, there is 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: 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      

 

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