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 Liquidity Response PT wrapper flow. A similar physical transmission wrapper exists for each of the following message flows:
  • Payment Gateway Response
  • Command
  • Payment MT103
  • Payment Pain
  • Repair Response
Figure 1. Liquidity response physical transmission wrapper flow
SampAppLiqdRespPhysTranWrapper.jpg

The sample application is using separate FAILED queues for each input channel. The default naming convention for the sample application is <input queue name>.FAILED, with the exception of the command queue. In the case of the command queue, the input queue name is FXH.SAMP1.COMMAND and the failed queue is FXH.SAMP1.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.