Using the MSMQ type trees

Depending upon how you want to map, either select one of the Message types as input or output or add a message content type as a MessageData component.

The type tree is arranged so you can integrate the definitions provided with any message data you want to define. The input card contains all message header properties. The output card contains only the message header properties you want. To optimize performance on the output card, select MSMQ_out.mtt and delete any unnecessary message header properties.