Defining input message characteristics

When a message is received by an input node in a message flow, the node detects how to interpret that message by determining the domain in which the message is defined and starting the appropriate parser.

Before you start:
Read the following concept topic:

You can provide message domain information to the input node in one of two ways:

  1. You can configure the built-in input nodes to indicate the message domain, and therefore the parser to be started, for each message that is received.
  2. You can set values in the input message itself that specify this information. Include an MQRFH2 header, which contains a folder that defines the message characteristics. This approach is more flexible because it means that the input node can start the appropriate parser based on the content of each message.

If the input message is defined in the MRM domain, and is therefore interpreted by the MRM parser, you must specify the following additional properties:

The way that these properties are set depends upon the type of message, or node, that you want to use:
  • If the message is a WebSphere® MQ message, these properties can be set either in the input node or in the MQRFH2 header of the incoming message. If the properties are set in both, the properties of the MQRFH2 header take precedence.
  • If the input message belongs to a Message domain other than those for which a parser is supplied, you must provide a user-defined parser to handle it, and a user-defined input node to accept it for processing in the message flow. Check the documentation provided with the user-defined parser and node for further information.
  • If the input node cannot determine the message characteristics, the default value is empty and the message is considered to be in the BLOB domain, and the BLOB parser is started.
Import either of the following samples, or another sample that uses a Message set, from the Samples Gallery, and look at the values on the Input Message Parsing properties tab of the input node in the sample's message flow. You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.
Related concepts
Message flows overview
Parsers
Logical tree structure
Message modeling
How the message tree is populated
Related tasks
Designing a message flow
Defining message flow content
Related reference
Built-in nodes
ESQL reference
MQRFH2 structure
Notices | Trademarks | Downloads | Library | Support | Feedback

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

ac12250_