Creating a new submap for a wildcard source

This topic describes how to map a wildcard value in the source to a wildcard value in the target. You might expect a wild card in a Mapping node for example, when you are using a SOAP message (where the Body element contains a wildcard). This type of wildcard represents the payload of the message, where the payload is a message that is defined elsewhere in the message set. The submap can involve from 0 to n source wildcards and 0 or 1 target wildcards.

The Message Mapping editor shows three kinds of wildcard, all of which allow you to create a submap:
Mapper construct Message model construct Choose concrete item for submap
Wildcard element Wildcard element Global element
Wildcard attribute Wildcard attribute Global attribute
Message with Wildcard Message child Group with Composition of Message and Content Validation of Open or Open Defined Message
  1. Switch to the Broker Application Development perspective.
  2. Open the message map for the required node.
  3. In the Source pane, expand the tree and select the source wildcard.
  4. In the Target pane, expand the tree and select the target wildcard.
  5. Right-click either the source or the target wildcard, and click Create new submap. The Wildcard Specification wizard opens.
  6. From the Wildcard Specification wizard, select the concrete item that will replace the source wildcard, according to the values shown in the table at the beginning of this topic.
  7. Click Next.
  8. From the Wildcard Specification wizard, select the concrete item that will replace the target wildcard, according to the values shown in the table at the beginning of this topic.
  9. Click Finish.
  10. Click OK. The submap opens in the Message Mapping editor.
  11. From the submap, map the source message elements to the target message elements as required.
  12. Click OK.
Related concepts
Mapping node
Related tasks
Creating a new submap
Calling a submap
Calling a submap from ESQL
Creating and calling submaps and subroutines