Header router
Header router
The header router is a producer which makes it possible to route messages to other flows based on selected header information. You can choose to send one message to flow A, another to flow B and delete yet another.
The routing works according to mappings and a header name (property). The header name determines which part of the message is evaluated against the mapping values.
When a mapping value is found, the message is sent to the flow referred to. If multiple mappings satisfy, the message is sent to multiple flows.
The full ConnectMessage and all associated headers and properties are always sent.
In the table below, you will find an explanation of these properties. All attributes with a ‘*’ are mandatory.
|
Attribute |
Description |
|
Name* |
By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional. |
|
Enabled |
Set this value to true, if you want this producer to be enabled. |
|
Default Flow |
If no matching route can be found, the message will routed to this default flow. If you set inter-interface routing to true, you can select flows outside your current interface. If the field is 'red', there is a problem with the value of the field. |
|
Inter-interface routing |
When set to true, Message Routing over interfaces is available. The default is false. |
|
Mapping |
Here you can set a routing value and refer to a flow. By pressing At routing, you indicate for which returned value of a routerStrategy the message has to be routed. |
| Header name |
Name of the header you want to use. |
In the table below, you will find an explanation about the properties of a mapping rule. All attributes with a ‘*’ are mandatory.
|
Attribute |
Description |
|
Routing value* |
Here you enter the expression value on which to route. |
|
Flow Name* |
Here you enter the name of the Flow to route to. |
| Description
|
Description of the specific producer. This is for documentation purposes. |