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

Parameters in Dynamic Mappings

Parameters in Dynamic Mappings

A parameter is a constant value that can change between mapping runs. Use parameters in a dynamic mapping to change sources and targets for flat files or relational resources. You can also use parameters to change the input rules, selection rules, transformation properties, and run-time links.
The following table lists the functionality of parameters that you can create for the dynamic mapping components:
Dynamic Mapping Component
Parameter Functionality
Aggregator transformation
Change the group by port.
Joiner transformation
Change the join condition.
Lookup transformation
Change the lookup condition.
Rank transformation
Change the group by port.
Read transformation
Create parameters to perform the following tasks:
  • Change the input file name or directory of a flat file source.
  • Change the connection of a relational source.
  • Change a flat file data object, customized data object, or a relational data object.
Rules
Create parameters to perform the following tasks:
  • Change the input rule criteria by name or pattern.
  • Change the selection rule criteria by name or pattern.
Run-time links
Change the set of ports to link between transformation groups.
Sorter transformation
Change the sort key.
Write transformation
Create parameters to perform the following tasks:
  • Change the output file name or directory of a flat file target.
  • Change the connection of a relational target.
  • Change a flat file data object, customized data object, or a relational data object.

0 COMMENTS

We’d like to hear from you!