Integration Flow Designer components

The Integration Flow Designer enables you to overwrite settings compiled into maps.

Map components of a system provide:

• Visual indication of audit log generation.
• Identification of the source or target type: message, database, file, or application.
• Ability to override map and card settings compiled into a map.
• A method of recording your system design with linked documents.

A map component is an Integration Flow Designer object that represents an executable map and displays its relationship with other components in the same system.

Systems can contain one or more map components. To keep the system manageable, you may create smaller systems and then include them as a subsystem of a larger system. Map components and system components are executable units.

Execution settings specify how the map or subsystem executes. The execution settings for system components are maintained in the Integration Flow Designer and are eventually used on designated servers to execute the system components. Each component in a system has separate execution settings. The referenced files (maps or subsystems) are static and are not modified directly with this information.

A map component that references an executable map has a default set of sources and targets defined within the referenced map. Map settings and card settings for sources and targets are defined in the Map Designer, and may be overwritten in the Integration Flow Designer.

The sources and targets defined in the map are the interface points of the map component used within a system. The sources and targets of executable map components are displayed in the main window of the Integration Flow Designer.

In the Integration Flow Designer, the expanded view of a map component distinguishes its sources from its targets.