Map components

A map component is an Integration Flow Designer object that represents an executable map with a defined set of interfaces based on sources, targets, and a surrounding layer of execution settings used at run time.

There are three classes of map components.

A map component references an executable map; it does not consume it. That is, the executable map exists externally and is reusable such that another map component can also reference it. You define an executable map once and then use it as many times as you want in the Integration Flow Designer. Since the Integration Flow Designer treats every map component as a unique instance, you can define multiple map components that reference the same executable map.

The Integration Flow Designer enables you to work from the bottom up. You can roll existing executable maps up into systems. The Integration Flow Designer also enables you to work from the top down. You can start at the top defining systems of maps that have not yet been implemented and you work your way down later to implement these maps. You can also do a bit of both: reference existing executable maps and maps that will be implemented later within the same system.

A map component is an executable unit. The Integration Flow Designer maintains the execution settings that you specify separately with each map component. The referenced compiled map files and source map files are static and are not modified directly with this information. The settings are eventually used on designated servers to execute the maps.