Editing a default-generated map manually

Sometimes, the map that is generated by the Message Mapping editor does not do everything that you want. If this is the case, there are a number of things that you can change manually. You can edit the structure directly by inserting, moving, copying, pasting, and deleting rows. The context menu provides a list of available editing actions with their keyboard equivalents. Here are some specific operations that you might want to perform:

Creating message headers

When you create a map, if you select the option This map is called from a message flow node and maps properties, headers and message body, the map that is created allows additional elements, including MQ, HTTP, and JMS headers, to be mapped.

If you use a Mapping node for a database to message mapping, and you select the option This map is called from a message flow node and maps properties and message body, the Message Mapping editor cannot generate an output MQMD header for the map file that is created. To ensure that an output MQMD header is created, perform one of the following steps:

Creating conditional mappings

When a mapping involves one of the following items:
  • schema choice group
  • derived type element
  • substitution group member
  • wildcard
  • repeating element
the default mapping that is generated by the Message Mapping editor might be placed under a "condition" statement. If the condition is not what you had expected, edit the statements; here are the changes that you can make:
See the Configuring conditional mappings topic for more information about conditional mappings.

Selecting the MQRFH2C compact parser

If you are using a Compute node downstream from a Mapping node, and the Compute node produces an MQRFH2C field, select Use MQRFH2C Compact Parser for MQRFH2 Domain on the MQInput node. When you select this property, the MQRFH2C compact parser is used for MQRFH2 headers instead of the MQRFH2 parser.
Related reference
Compute node
Mapping node