Filter Node In IBM App Connect
Here in this blog, we will learn about Filter Node in IBM App Connect
The use of the Filter node in IBM App Connect Enterprise v12 (ACE) for working with projects and artefacts will be covered in this blog post. Using the Filter node, a message flow can control the order in which messages are handled.
Filter Node In IBM App Connect:
- The Filter node is represented in the IBM App Connect Enterprise Toolkit and is located in the Routing drawer of the palette.
- In ESQL, create a filter expression that specifies the path the message should take. The filter expression can be completed with data stored in an external database, and it can contain parts of the input message or message properties.
- The destination of the message upon evaluation of the expression is determined as either true, false, or unknown.
- Link the terminals that address every scenario that the filter might produce; even transactional messages are rejected if the node sends them to an unconnected terminal.
- In the same manner as the Compute and Database nodes, the Filter node accepts ESQL statements. An ‘expression’ statement with a return value that evaluates to a Boolean value must be the final statement to be executed.
- The message’s destination terminal is chosen by this Boolean value. Routing algorithms are frequently as simple as comparing the values of message fields. The expression describes the comparison, and there is only one statement the return statement. The node spreads the message to the Unknown terminal if you code RETURN with a null expression or without an expression.
Terminals:
In: The input terminal that receives messages for the node to process.
Failure: the output terminal that receives the message in the event that a computation error is discovered.
Unknown: If the specified filter expression evaluates to null or unknown, the message is routed to the output terminal.
False: If the specified filter expression evaluates to false, the message is routed to the output terminal.
True: The destination terminal for the message, in case the given filter expression yields a true result.
Working of Flow:
Below diagram show the working of filter node in the message flow. We can use this any where in the flow.
Flow propagates from in terminal to filter node inside node based on content message will filter and propagation will be decided like true, false or unknow.
In the Filter node we can read the data but we cannot write the data. So we need to use root to read the data from filter node.
