Table of Contents

Search

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

Developer Mapping Guide

Developer Mapping Guide

Rename Generated Ports

Rename Generated Ports

You can generate unique port names through a setting that renames generated ports with a prefix or suffix.
For example, you can add an
Agg_
prefix to indicate that the ports were generated in an Aggregator transformation.
The following image shows the renamed generated ports in the Aggregator transformation with an
Agg_
prefix:
The mapping contains a Read transformation and an Aggregator transformation. The Aggregator transformation has a dynamic port From_Read_EMPLOYEE with generated ports that have an Agg_ prefix.
When you add ports of the same name to a transformation, the Developer tool appends a number to the generated port to resolve port naming conflicts. You might want to rename generated ports if the Data Integration Service will not be able to resolve port conflicts at run time. If the mapping uses a dynamic source, the Data Integration Service might encounter a port name conflict at run time. If the Data Integration Service encounters a port name conflict, it tries to rename the generated port. The mapping fails if the Data Integration Service cannot resolve the port name conflict. The mapping fails in the following situations:
  • An unresolved link exists from the renamed generated port to a static port.
  • A transformation property, such as group by port or join condition, uses the renamed generated port.
To avoid mapping failures, rename generated ports to ensure that the names are unique within each transformation.

0 COMMENTS

We’d like to hear from you!