Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Mapping Outputs
  6. Generate a Mapping from an SQL Query
  7. Dynamic Mappings
  8. How to Develop and Run a Dynamic Mapping
  9. Dynamic Mapping Use Cases
  10. Mapping Administration
  11. Export to PowerCenter
  12. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Connection Assignments

Connection Assignments

When you import data sources and other objects from PowerCenter, you can assign a data source connection type.
For example, you can create a source definition, a target definition, or a Lookup transformation in PowerCenter that connects to an Oracle database. When you import these objects in the Developer tool, use the
Connection Assignment
dialog box to specify the connection type for each object.
When you select a connection type for PowerCenter repository objects, use one of the following methods to assign connections:
Assign a single connection to multiple PowerCenter objects at the same time.
You can assign a single connection to all sources, all targets, all Lookup transformations, or all objects that do not have an assigned connection. Or, you can assign a single connection to all objects with names that match a specified name pattern. Select an option from the
Select
list and click
Assign Connection
.
Assign a single connection to multiple PowerCenter objects of different object types.
Choose the
Custom
option in the
Select
list, select multiple PowerCenter objects, and then click
Assign Connection
.
Assign a connection to a PowerCenter object.
Select a PowerCenter object and click the
Open
button in the
Connection Name
column.
You can assign a connection to an object that is different from the original connection type. You might do this if Developer tool does not support the original connection type. If you assign a different connection type than the original one, the Developer tool warns you that the connection types do not match.
If you choose to ignore the warning and proceed, the import succeeds and assigns the new connection to imported data sources. The source or target are valid when the metadata for the chosen connection matches the schema of the imported data sources.
For Lookup transformations created with a connection type that the Developer tool does not support, information about the original connection type is not available, and the Developer tool does not warn about a connection mismatch.

0 COMMENTS

We’d like to hear from you!