Message mappings overview

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: 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: 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.

Find out more about message flows, ESQL, and mappings.

This section also contains information about Advanced schema structures.

Related concepts
Message flows, ESQL, and mappings
Message flows overview
Related tasks
Developing message mappings
Related reference
Message mappings
Mapping node