Physical transmission wrapper

All FTM applications must have one or more physical transmission wrapper flows. These flows provide a mapping between real world inputs (IBM® MQ, HTTP, File, and so on) and the core physical transmission flow. It is also used to:
  • Manage channel identification.
  • Override default transmission persistence values.
  • Manage and log failed messages.
  • Provide a deployment point for inbound mappers.
Figure 1. A sample physical transmission wrapper flow
SampAppPhysTranWrapperFlow.jpg
Any standard or custom input node can be used to provide input into an FTM application. This includes, but is not limited to:
  • MQInput
  • HTTPInput
  • FileInput
  • TCPIPInput
  • JMSInput