The following types of message headers and
folders can be included for source and target messages in a message map (note
that a submap does not include message headers):
- LocalEnvironment
- Properties
- MQ Headers
- HTTP Headers
- JMS Transport Header
If you choose not to map message headers or the LocalEnvironment explicitly
in your message map, then the output message is produced with the same message
headers as the input message. When you Populate the message map, the Properties
folder for the source and target are displayed in the message map, with MessageSet
and MessageFormat initially mapped to the input message. MessageType is also
mapped to the input message if the parser domain is MRM. The
other properties are blank initially, and the message headers are copied from
the input message.
Alternatively, if you choose to map any message
headers or the LocalEnvironment in your message map, then no message headers
are copied from the input message. You must add mappings for these headers
to ensure that the target message contains appropriate headers to make a valid
output message.
To add message headers or other folders to a message map:
You can use
Add or Remove Headers
and Folders to remove message headers or the LocalEnvironment
folder. Right-click on either the
$source or the
$target to
open the
Select Message Headers dialog. Clear the headers
or other folders to remove them from the message map. Removing a message header
or other folder from the message map removes any associated mappings that
you have created. You can remove the Properties folder from the message map,
but note that all built-in parsers require some values in the Properties folder
for the output message.
You can map multiple instances of a header
by right clicking on the header in the Message
Mapping editor Spreadsheet pane and
selecting Insert Before or Insert After .
Select the header from the Insert Statement dialog.