A message flow represents the set of actions performed on a message when
it is received and processed by a broker. The content and behavior of a message
flow is defined by a set of files that you create when you complete your definition
and configuration of the message flow content and structure:
- The message flow definition file <message_flow_name>.msgflow.
This is a required file and is created automatically for you. It contains
details about the message flow characteristics and contents (for example,
what nodes it includes, its promoted properties, and so on).
- The ESQL resources file <message_flow_name>.esql.
This file is required only if your message flow includes one or more of the
nodes that must be customized using ESQL modules. You can create this file
yourself, or you can cause it to be created for you by requesting specific
actions against a node.
You can customize the following built-in
nodes by creating free-form ESQL statements that use the built-in ESQL statements
and functions, and your own user-defined functions:
- The mappings resource file <message_flow_name><_nodename>.mfmap.
This file is required only if your message flow contains one or more of the
nodes that must be customized using mappings. You can create this file yourself,
or you can cause it to be created for you by requesting specific actions against
a node. A different file is required for each node in the message flow that
uses the mapping editor.
You can customize the following built-in nodes
by specifying how input values map to output values:
- DataDelete
- DataInsert
- DataUpdate
- Extract
- Mapping
- Warehouse
You can use built-in ESQL functions and statements to define
mappings, and you can use your own ESQL functions.