XML Configuration Basics
A Frank!Framework application is defined by XML configuration files validated against FrankConfig.xsd. The root element is `, which contains one or more ` elements.
Error Message Formatters
Error message formatters control how the Frank!Framework formats error responses returned by adapters. When a pipeline finishes with a state other than SUCCESS, or when an unhandled exception occurs, the error message formatter determines the structure and content of the response sent back to the caller.
Exits and Global Forwards
This page covers advanced pipeline flow control: defining exits, using global forwards to reduce repetition, and structuring pipelines for clarity.
FrankSender and FrankListener
The FrankSender sends a message to another Frank!Adapter (or an external program running in the same JVM). It is the modern, preferred way to call one adapter from another and replaces the older IbisLocalSender and IbisJavaSender.
Includes
Frank!Framework configurations support including external XML files to promote reuse, reduce duplication, and improve maintainability. This lets you split large configurations across multiple files.
PipelinePart
A `` is a reusable piece of a pipeline stored in its own file, much like an include file — but instead of whole adapters it contains a fragment of pipeline (a set of pipes). This lets you factor out a sequence of pipes that is shared between adapters or that you simply want to keep in a separate file for readability.