Mappings > Mappings


A mapping defines reusable data flow logic that you can use in mapping tasks. Use a mapping to define data flow logic that is not available in synchronization tasks, such as specific ordering of logic or joining sources from different systems.
You can create the following types of mappings:
Use a mapping to deploy small to medium data integration solutions that are processed directly by a Secure Agent group using the infrastructure that you provide, or by the Hosted Agent.
Elastic Mapping
Use an elastic mapping to deploy large data integration solutions. When you run an elastic mapping, the mapping is pushed to an elastic cluster to achieve faster processing for broad data sets. The infrastructure of the elastic cluster is automatically optimized based on the number and size of elastic jobs.
Use the Data Integration Mapping Designer to configure mappings. When you configure a mapping, you describe the flow of data from source and target. You can add transformations to transform data, such as an Expression transformation for row-level calculations or a Filter transformation to remove data from the data flow. A transformation includes field rules to define incoming fields. Links visually represent how data moves through the data flow.
You can configure parameters to enable additional flexibility in how you can use the mapping. Parameters act as placeholders for information that you define in the mapping task. For example, you can use a parameter for a source connection in a mapping, and then define the source connection when you configure the task.
You can use components such as mapplets, business services, and hierarchical schema definitions in mappings. Components are assets that support mappings. Some components are required for certain transformations while others are optional. For example, a business services asset is required for a mapping that includes a Web Service transformation. Conversely, a saved query component is useful when you want to reuse a custom query in multiple mappings, but a saved query is not required.
To use mappings and components, your organization must have the appropriate licenses.