You can control validation by setting properties presented by the Validation tab and General Message Options tab on the following nodes:
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 please refer to Validating messages.
Tab | Properties that affect validation |
---|---|
Validate | Validate, Failure Action, Include All Value Constraints, Fix |
General Message 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:
The check box is selected. You cannot change this option.
Include All Value Constraints specifies which basic value constraint checks are to be performed on the values of fields in the message when Validate resolves to Content And Value. The checks performed are:
For more details on value constraints, see Simple type logical value constraints.
The default value is none. You cannot change it.
None specifies that no extra remedial action is to be taken when Validate resolves to Content or Content And Value and validation failures occur, The remedial action taken depends on the setting of Failure Action.
If Failure Action is set to User Trace or Local Error Log, the remedial action is limited to the default remedial action that takes place when no validation is being performed, as described in Validating messages:
If Failure Action is set to Exception or Exception List, the remedial action is limited to the third item in the above list, and an exception is thrown for the first two items.
Node type | Nodes containing Parse Timing property options |
---|---|
Input nodes | MQInput, MQGet, SCADAInput, HTTPInput, HTTPRequest, Real-timeInput, JMSInput, Compute JavaCompute, Mapping, ResetContentDescriptor, TimeoutNotification |
Other nodes | 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 switch on 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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac18870_ |