Launcher overview

The Launcher runs systems of maps that are created and generated using the Integration Flow Designer (IFD).

These systems of maps that are generated specifically to run in the Launcher are called system files (.msl), sometimes referred to as Launcher control files.

When the Launcher starts running, it is initialized with .msl files in the deployment directory.

The new HTTP Listener component of the Launcher provides secure, two-way communication between external clients and the Launcher. An external HTTP client can trigger a map in a Launcher system by sending a request to the Launcher HTTP Listener. Regardless of whether it runs successfully, the map returns a response through the HTTP Listener to the external HTTP client. If the map fails or the output card does not return a response to the client, the input card automatically returns a response. For more information on the HTTP Listener, see Launcher HTTP Listener overview.

You can specify a deployment directory from the Launcher Administration interface. (For more information about this, see "Launcher Administration".)