Check node

Use the Check node to compare the template of a message that is arriving on its input terminal with a message template that you supply when you configure the Check node.

Attention: The Check node is deprecated in WebSphere® Message Broker Version 6.0 and subsequent versions. Although message flows that contain a Check node remain valid, redesign your message flows where possible to replace Check nodes with Validate nodes.

This topic contains the following sections:

Purpose

The message template comprises the Message domain property. If the message domain is MRM, you can also specify any combination of message set and message type. The Check node checks only the message structure; it does not check the message body.

The message domain, message set, and message type of the message are collectively called the message template. The domain defines the parser that is used for the message. The set is the message set to which the message belongs. The type is the structure of the message itself. You can check the incoming message against one or more of these properties. The message property is checked only if you select its corresponding Check property, which means that a message property that contains a null string can be compared.

If the message properties match the specification, the message is propagated to the Match terminal of the node. If the message properties do not match the specification, the message is propagated to the Failure terminal. If the Failure terminal is not connected to some failure handling processing, an exception is generated.

The Check node is contained in the Validation drawer of the palette, and is represented in the workbench by the following icon:

Check node icon

Using this node in a message flow

Use the Check node to ensure that the message is routed appropriately through the message flow. For example, you can configure the node to direct a message that requests stock purchases through a different route from that required for a message that requests stock sales.

Another example of this node's use is for the receipt of electronic messages from staff at your head office. These messages are used for multiple purposes; for example, to request technical support or stationery, or to advise you about new customer leads. These messages can be processed automatically because your staff complete a standard form. If you want these messages to be processed separately from other messages received, use the Check node to ensure that only staff messages with a specific message type are processed by this message flow.

Terminals and properties

When you have put an instance of the Check node into a message flow, node into a message flow, you can configure it. For more information, see Configuring a message flow node. The properties of the node are displayed in the Properties view. To display the properties of the node in the Properties dialog, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

The Check node terminals are described in the following table.

Terminal Description
In The input terminal that accepts a message for processing by the node.
Failure The output terminal to which the message is routed if the incoming message does not match the specified properties.
Match The output terminal to which the message is routed if the incoming message matches the specified properties.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the BAR file to deploy it).

The Check node Description properties are described in the following table.

Property M C Default Description
Node name No No Check The name of the node
Short description No No   A brief description of the node.
Long description No No   Text that describes the purpose of the node in the message flow.

The Check node Basic properties are described in the following table.

Property M C Default Description
Domain No No   The name of the domain.
Check domain Yes No Cleared This property checks that a message belongs to a particular domain. To check the parser that is to be used for the incoming message, select this check box and select one of the values from the Domain list.
Set No No   The message set to which the incoming message belongs.

If you are using the MRM, IDOC, or XMLNSC parser, check that the incoming message belongs to a particular message set by selecting Check set and entering the identifier of the message set in Set. This identifier can be found in the properties of the message set when you view it in the editor. WebSphere Message Broker generates the identifier when you create the message set; it is something like DHHJEQC06U001. You must enter the identifier exactly as shown in the message set properties.

Leave Set clear for other parsers.

Check set Yes No Cleared If you select this check box, the incoming message is checked against the Set property.
Type No No   The message identifier.

If you are using the MRM parser, check that the incoming message is a particular message type by selecting Check type and entering the identifier of the message in Type.

This identifier can be found in the properties of the message when you view the message in the editor. You specify the message identifier when you create the message. You must enter the identifier exactly as shown in the message properties.

Leave Type clear for other parsers.

Check type Yes No Cleared If you select this check box, the incoming message is checked against the Type property.
Related reference
Validate node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:09

ac04770_