Message Channel
This is the second pattern that I am going to talk about. This presents how the two application can be integrated. The simplest definition of this pattern is “Sender Application writes information to a Message Channel and Receiver application reads the information from the same Message Application”.
The Sender Application puts the message to a specific Channel and the Receiver Application reads the information from a specified Channel only. There are multiple possible paths possible within two application based on this pattern.
In today’s integration environment, it is not just about creating multiple channel for each path only. It goes into so much complicated paths that it is not possible to maintain different channel. Innovations have lead to re-use of existing channel for multiple Receiver applications based on several properties of Information including header and data.
I have explained more about this in the Message Pattern where I talk about the message properties. Just to give you an idea about the concept, now-a-days, we use Message selector and header data to identify where, whom the message should be transmitted and picked up.
When this is applied to Weblogic, the Message Channel becomes a Weblogic JMS Queue/Topic. Several properties and configurations are possible with Weblogic Message Channel which you can find on Weblogic documentation.
Hope you like the post. Encourage to share your ideas.
[…] Message Channel […]