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
Mapping node supports
the following message domains:
- MRM
- XMLNSC
- XMLNS
- MIME
- JMSMap
- JMSStream
- XML
If you use an unsupported parser to perform mappings, for example
IDOC or a user-defined parser, error messages might be generated when
messages pass through your message flow. See
Changing 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.