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.
You can also create a reusable form of message map known as a
submap. Submaps can be called from message maps and ESQL code.
You must have message definitions for any messages that you want
to include in a message mapping. You can select the messages from your existing
message definitions when you create a new message map. The following message
domains are supported by the
Mapping node:
- MRM
- XMLNSC
- XMLNS
- MIME
- JMSMap
- JMSStream
- XML
If you use an unsupported parser to perform mappings, for example IDOC,
BLOB or a user-defined parser, error messages might be generated
when messages pass through your message flow. See
Change the target message domain for information about setting the message domain for
the target message.
Find out more about message flows, ESQL, and
mappings.
This section also contains information about Advanced schema structures.