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:
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:
Node | Usage |
---|---|
DataDelete node | Use this node to delete one or more rows from a database table without creating an output message. |
Datalnsert node | Use this node to insert one or more rows in a database table without creating an output message. |
DataUpdate node | Use this node to update one or more rows in a database table without creating an output message. |
Extract node | Use this node to create a new output message that contains
a subset of the contents of the input message. Use the Extract node only if
no database is involved in the map. The Extract node is deprecated in WebSphere Message Broker Version 6.0. Although message flows that contain an Extract node remain valid in WebSphere Message Broker Version 6.0, where possible, redesign your message flows so that any Extract node is replaced by a Mapping node. |
Mapping node | Use this node to construct output messages and populate them with information that is new, modified from the input message, or taken from a database. You can also use the Mapping node to update, insert or delete rows in a database table. |
Warehouse node | Use this node to store all or part of a message in a database table without creating an output message. |
You can use built-in ESQL functions and statements to define message mappings, and you can use your own ESQL functions.