User Guide > Designing and Executing Map
Was this helpful?
Designing and Executing Map
 
Exploring Map Editor
Creating a Map Using New Map Wizard
Creating a Map Without Joins Using Map Wizard
Creating a Map With Joins Using Map Wizard
Creating a Map Within Process Designer
Creating a Map Without Using Map Wizard
Setting Up Source Data
Specifying Source Connector, Parts, and Properties
Confirming Source Schema
Defining and Applying Filters to Source Data
Defining Sort Options
Defining Sample
Browsing Source Data
Clearing Source Connection
Saving and Reusing Source Configuration
Setting Up Join Sources
Specifying New Schema for Join
Deleting Join
Setting Up Target Data
Specifying Target Connector, Parts, and Properties
Confirming Target Schema
Defining and Applying Filters to Target Data
Defining Sample
Browsing Target Data
Clearing Target Connection
Saving and Reusing Target Configuration
Managing Multiple Targets
Viewing Map File Properties
Saving a Map as RTC File
Saving and Reusing a Connection
Refreshing Map Connection Schema
Reconnecting Target Connector
Setting Up Multimode Target Connectors
Setting Up Multimode Target Connectors
Managing Constants
Adding Constants
Searching Constant
Deleting Constant
Example
Managing Intermediate Targets
Managing Lookups
Managing Temporary Targets
Setting Up Reject Data
Confirming Reject Schema
Using Reject Data Browser
Clearing Reject Connection
Saving Reject Configuration
Using Map Navigator
Configuring Map
Configuring Macros
Using Script Library Files
Defining Global Variables
Configuring Map Events
Configuring Logging Options for a Map
Configuring Engine Profiler
Configuring Execution Options for a Map
Mapping Target from Source Data
Mapping Methods
Common Options
Mapping Fields Using Simple View
Mapping Fields Using Advanced View
Common Tasks in Simple View and Advanced View
Dragging and Dropping Fields From Source to Target
Using Map Recommend
Target File Mapping Scenarios
Custom Search Navigator
Managing Record Types in Advanced View
Managing All Record Instances in Advanced View
Managing Groups in Advanced View
Managing Field Records in Advanced View
Managing Events and Actions
Managing Record Rules in Advanced View
Adding Target Record Write Condition Rules in Advanced View
Validating Maps
Validating a Map
Running Maps
Troubleshooting Map Execution
Migrating Connectors in an Existing Map
This topic describes how to use the Map Editor to design and execute a data transformation map. The data transformation maps can be designed and saved for future use. These map files can be executed interactively in the Map Editor environment and are suitable for ad-hoc testing and prototyping. The map files can also be executed using the command line interface and can be packaged and scheduled using the Integration Manager or through a custom application.
A transformation map uses specialized data transformation components called connectors. Connectors facilitate data transformation by reading data from a source (source connectors), converting it to a specific format, and then writing the data into a target (target connectors). These connectors are plug-and-play, flexible, and highly efficient. They easily transform bulk quantities of data in real-time and facilitate migration. The transformation capabilities are very powerful and can be controlled using the Event, Condition, and Action (ECA) rules.
What the data looks like on the target side is determined by Field Mappings and Event Actions:
Field Mapping: What the target field value will be is determined by its “Field Mapping”. Each target field can have a very simple field mapping like that of a constant string [for example, “myFieldValue”] or take on of the source field’s values [for example, FieldAt("/SOURCE_1/Sheet1/StateName")]. A target field can take the value of some aggregated other field, or the target field can also take a value that is calculated using a very complex expression script.
Event Actions: How and when Field Mappings get executed is determined by ECA rules. The transformation engine executes various events at different times during a transformation. You can choose to perform different actions when these events occur. For example, the engine executes a TransformationStarted event before any source records are read. You can use this event to initialize variables, create tables, or perform other actions. For a complete list of events and actions, see ECA Rules. Most events return a TRUE or FALSE based on a condition. Separate actions can be defined for TRUE and FALSE conditions. For example, a condition can state that “if the balance field is <=2000” is TRUE then write the record to the target otherwise, reject the record because the balance should never be greater than 2000.
Note:  Events and actions are filtered based on the connector capabilities and the nature of the schema. For example, for connectors that do not support hierarchical schemas, SubTreeStarted and SubTreeEnded events and their corresponding actions are not available.
Using the Map Editor, you can design and run maps that include data transformation instructions for an integration project.
At the basic level, a map consists of the following:
• Map metadata properties (metadata properties such as creator, create date, date modified, and description)
• Maps use datasets to read and write data. The source datasets are read, and the target datasets are written. You select source or target when you create a dataset.
Tip...  You can design a map using source and target datasets and switch to other datasets in the configuration that runs the map.
• Source contains the following:
– Connect information (parts and properties)
– Schema (defines record, field, and field data type information that enables the connector to parse the data and pass it in a common format to the engine). Some connectors have built-in schema. For other connectors, you must set an external schema that can be used by the connector.
– Sort keys (can be set if source schema has one record type)
– Filters (allows you to fine tune the data you want to transform)
– Sample settings
• Targets:
– Connect information (parts and properties)
– Schema (defines record, field, and field data type information that enables the connector to parse the data and pass it in a common format to the engine). Some connectors have built-in schema. For other connectors, you must set an external schema that can be used by the connector.
– Update keys (only for connectors that supports Update as the output mode)
– Filters (allows you to fine tune the data you want to transform, not applicable for reject)
• Map that includes:
– Field mapping (from source to target)
– Events and actions (at the transformation, source, target, or source/target record level)
• Configuration settings
– Macros
– Script Libraries (contain functions that can be executed while transforming data)
– Global Variables (used in expressions)
– Map events (for pre and post data transformation processing)
– Execution Configuration
• Execution properties
• Log settings
• Profile settings
The actual mapping has two views Map Fields (Simple) View and a Map All (Advanced) View. The Advanced view allows to set events and actions.
For more information about the types of artifacts and the supported editors, see Integration Artifacts and Editors.
Last modified date: 07/26/2024