Mapping headers and folders

Include message headers and folders for source and target messages in a message map.
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, 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 MessageType initially set based on the target message.

MessageFormat is set to the default wire format of the message set 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, 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.

Before mapping headers and folders, ensure that you do the following tasks:
  1. Create a message flow project
  2. Create a message flow
  3. Define message flow content
  4. Create a message map file from the navigator or create a message map from a node.

To add message headers or other folders to a message map:

  1. Right-click your message map in the Broker Development view and select Open or right-click your mapping node and select Open Map to open the Message Mapping editor.
  2. Right-click $source in the Source pane and select Add or Remove Headers and Folders to add message headers or other folders to the source message. The Add or Remove Headers and Folders dialog box opens.
  3. Ensure that Selected headers and other folders is selected. If No folders (map body element only) is selected your map is a submap, and can not have headers associated with it. You can change the submap to a message map by selecting Selected headers and other folders.
  4. Select the headers that you want to map from the list. If you want to map MQ Headers or HTTP Headers, you must select individual headers by expanding the list. If you are using MQ Headers you must include the MQMD, and so this is automatically selected for you.
  5. Click OK to add the selected message headers or folders to the message map.
  6. Right-click $target in the Target pane and select Add or Remove Headers and Folders to add message headers or other folders to the output message.
  7. Repeat steps 3 to 5 to add the headers and folders that you require to the target message.
  8. Configure the message header and folder mappings in the same way as other mappings.
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 box. 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 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.

Related concepts
Message tree structure
Local environment tree structure
Related tasks
Creating a message map file in the Broker Development view
Configuring message mappings
Configuring the LocalEnvironment
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:23:03

ar37530_