Data Transformation Engine Integration Flow Designer Reference Guide

Chapter 1 - Introduction Using the Integration Flow Designer
Integration Flow Designer Reference Guide
8
You do not need the IFD if you are using a Command Server. However, you will
find it to be very useful as a client facility for managing maps that will be run by a
Command Server. The IFD generates process control information for Command
Servers in the form of command files. Generating these command files manually is
tedious and error-prone. Using the IFD eliminates possible manual errors.
Using the Integration Flow Designer
When you use the IFD to create systems from collections of maps, you will
typically have maps already created and ready to use. However, the IFD enables
you to create placeholder maps called pseudo maps. You can add input and output
cards to these pseudo maps and create source maps as you move forward with
your design.
For each system, you can select a server and choose the execution mode: Event
Server or Command. If you are using the Event Server, you must generate an
Event Server system file (.msl). The .msl file is the only file that the Event Server
recognizes. If you are using the Command Server, you can generate text
command files.
When you select a server for the system, the system is called an executable
system. For each executable system, you can create and run deploy scripts that
automate the process of generating and deploying a system to a different server.
After you generate an .msl file, you are ready to run the system using the Event
Server.