Optionally, use nodes that determine the order and flow of control in the message flow to decide how messages are processed by the flow.
The Validate node replaces the Check node, which is deprecated in WebSphere® Message Broker Version 6.1. The Validate node works in the same way as the Check node, but it has more Validation properties to enable the validation of message content by parsers that support that capability.
The node terminals are True, False, Unknown, and Failure. The message is propagated to the True terminal if the test succeeds, and to the False terminal if it fails. If the statement cannot be resolved (for example, it tests the value of a field that is not in the input message), the message is propagated to the Unknown terminal. If any other error is detected, the message is propagated to the Failure terminal.
The test in the ESQL statement can depend on message content, database content, or a combination of the two.
If you refer to a database, you can control how it is accessed by this node by specifying user and password information for each data source that is defined in the registry on the broker system. Use the mqsisetdbparms command to initialize and maintain these values.
Use this node in preference to the Compute node to provide message selection and routing; the Filter node is more efficient for this task.
Use the Route node to implement message routing with minimal programming logic. For more advanced routing scenarios, use a Compute node or a JavaCompute node.
The Label node routes the message to the next node in the flow and completes no processing.