Use a Channel Adapter that can access the application's API or data and publish messages on a channel based on this data, and that likewise can receive messages and invoke functionality inside the application.
Use a separate Datatype Channel for each data type, so that all data on a particular channel is of the same type.
Dead Letter Channel
When a messaging system determines that it cannot or should not deliver a message, it may elect to move the message to a Dead Letter Channel.
Use Guaranteed Delivery to make messages persistent so that they are not lost even if the messaging system crashes.
Invalid Message Channel
he receiver should move the improper message to an Invalid Message Channel, a special channel for messages that could not be processed by their receivers.
Structure the connecting middleware between these applications as a Message Bus that enables them to work together using messaging.
Connect the applications using a Message Channel, where one application writes information to the channel and the other one reads that information from the channel.
Use a Messaging Bridge, a connection between messaging systems, to replicate messages between systems.
Send the message on a Point-to-Point Channel, which ensures that only one receiver will receive a particular message.
Send the event on a Publish-Subscribe Channel, which delivers a copy of a particular event to each receiver.