Message mappings define the blueprint for creating a message, where the
created message is known as the target message. Messages can contain the following
components:
- simple elements and attributes
- complex elements (structures)
- repeating simple or complex elements
- other (embedded) messages
Messages can contain protocol-specific headers, which might need to
be manipulated by
WebSphere Message Broker.
Dynamic setting of a message destination (routing) within the
WebSphere Message Broker might
also be required. Values for target message elements can be derived from:
- input message elements (the input message is also known as the source
message)
- database tables
- constant values
WebSphere MQ constants
- functions supplied by the Mapping node
- user-defined functions
The logic to derive values can be simple or complex; conditional statements
might be needed, as might loops, summations and other functions. All of the
above mappings can be achieved using a
Mapping node.