Stage 1: defining systems

Use the Integration Flow Designer at design time to model what-if scenarios and visualize the results.

In the first stage, you use the Integration Flow Designer to construct system definition files. A system definition file is a model of a system of maps that you want to execute. System definition files are maintained in various system windows that you open and view. The diagrams include map and subsystem components and their execution properties. Data flow relationships are automatically derived and displayed. The system definitions are stored in system definition files (.msd) based on how you decide to organize them. The Navigator helps you to graphically interact with system definition files and the various systems that they contain.

The Integration Flow Designer includes a Doc Links feature that helps you document your design. You can link any text or Windows-registered document type to both map and system components. Then you can view and edit this document by referencing it through the system component to which it is linked. For example, you can link a Microsoft Word document to a map component that specifies design information for this map. You can link a document from a preferred project management tool to a map or a system to assist in managing the project plan. In addition to Doc Links, the Integration Flow Designer enables you to enter free-form text directly to the system definition file.

While you are defining systems, you can use the Integration Flow Designer to open the Map Designer and/or the Database Interface Designer using a map you select in a system. You can also open the Type Designer using a type tree associated with a map input or output card that you select.