Physical transmission wrappers

There are six physical transmission wrappers, which provide mappings between real world inputs such as IBM® MQ, HTTP, file, and so on, and the core physical transmission flow. They are also used to:
  • Manage channel identification.
  • Manage and log failed messages.
  • Provide a deployment point for inbound mappers.
The following figure shows an example of one of the physical transmission wrapper flows, the sanction response PT wrapper flow. A similar PT wrapper exists for each of the following message flows:
  • Command
  • Payment Pacs
  • Fragmentor
  • DeFragmentor
Figure 1. Sanction response physical transmission wrapper flow
fragSampAppRespPhysTranWrapperFlow.jpg
Figure 2. Fragmentor.msgFlow
fragmentor.jpg
Figure 3. DeFragmentor.msgFlow
defragmentor.jpg

The sample application is using separate failed queues for each input channel. The default naming convention for the fragmentation sample application is <input queue name>.FAILED, with the exception of the command queue. For the command queue, the input queue name is FXH.COMMAND and the failed queue name is FXH.FRAG_SAMP.COMMAND.FAILED.

Channels are resolved by name, based on the MQInput node from which they have been read.
Note: The old sample application used the input queue name from the MQMD.