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. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Mapplet Input

Mapplet Input

Mapplet input can originate from a data source or from an Input transformation.
You can create multiple pipelines in a mapplet. Use multiple data sources or Input transformations. You can also use a combination of data sources and Input transformations.
Use one or more data sources to provide source data in the mapplet. When you use the mapplet in a mapping, it is the first object in the mapping pipeline and contains no input ports.
Use an Input transformation to receive input from the mapping. The Input transformation provides input ports so you can pass data through the mapplet. Each port in the Input transformation connected to another transformation in the mapplet becomes a mapplet input port.
When you use an Input transformation to provide the input for a mapplet, you can set default values in the output ports of the Input transformation. The default values in the Input transformation output ports become default values for the mapplet input ports. If NULL data is passed from the mapping to the Input transformation, the Data Integration Service replaces the NULL value with the default value. The mapplet input uses the default value.
You can connect an Input transformation to multiple transformations in a mapplet. You can also connect one port in an Input transformation to multiple transformations in the mapplet.
Input transformations can receive data from a single active source. Unconnected ports do not appear in the mapping editor.

0 COMMENTS

We’d like to hear from you!