A mapping is a set of source and target definitions linked by transformation objects that define the rules for data transformation. Mappings represent the data flow between sources and targets. When the Integration Service runs a session, it uses the instructions configured in the mapping to read, transform, and write data.
Every mapping must contain the following components:
Describes the characteristics of a source table or file.
Modifies data before writing it to targets. Use different transformation objects to perform different functions.
Defines the target table or file.
Connect sources, targets, and transformations so the Integration Service can move the data as it transforms it.
A mapping can also contain one or more mapplets. A mapplet is a set of transformations that you build in the Mapplet Designer and can use in multiple mappings.
When you add an object to a mapping, you configure the properties according to the way you want the Integration Service to transform the data. You also connect the mapping objects according to the way you want the Integration Service to move the data. You connect the objects through ports.
The Mapping Designer displays objects in three different views:
Shows an icon of the object with the object name.
Shows the columns in the ports tab and the input and output port indicators. You can connect objects that are in the normal view.
Shows the object properties. You can switch between the different tabs and configure the object in this view.