You can control validation by setting properties on the Validate and Parser Options tabs for the nodes that are listed in the following table.
Node type | Nodes with validation options |
---|---|
Input node | MQInput, SCADAInput, HTTPInput, JMSInput, TimeoutNotification |
Output node | MQOutput, MQReply, SCADAOutput, HTTPReply, JMSOutput |
Other nodes | Compute, Mapping, JavaCompute, Validate, ResetContentDescriptor, MQGet, HTTPRequest, ![]() ![]() |
For an overview of message validation in the broker, refer to Validating messages.
Tab | Properties that affect validation |
---|---|
Validation | Validate, Failure Action |
Parser Options | Parse Timing |
Sets whether validation is required. All nodes provide the following options:
Some nodes also provide the following option:
The action that you want to be taken when a validation failure occurs. You can set it to the following values:
Node type | Nodes containing Parse Timing property options |
---|---|
Input nodes | MQInput, MQGet, SCADAInput, HTTPInput, HTTPRequest, Real-timeInput, JMSInput, TimeoutNotification |
Other nodes | Compute, JavaCompute, Mapping, ResetContentDescriptor, ![]() ![]() |
The Parse Timing property determines whether on demand parsing is to be used when parsing a message. It also gives you control over the timing of MRM input message validation:
If you enable MRM message validation, and you select On Demand or Immediate for Parse Timing, validation errors might not be detected until later in the processing of a message by a message flow, or might never be detected if a portion of the message is never parsed. To make sure that all fields in a message are validated, either select Complete, or select Immediate and make sure that you resolve all unresolved types with a Composition of Choice or Message at the start of your message flow.
The Parse Timing property has no effect on the validation of output messages.