Copy Right
© 2012 WSO2 Inc. Powered by 
JMS Message Delivery Reliability and Acknowledgement PatternsStore and forward messaging model brings loose coupling to exchanging messaging in a distributed computer system. With that, several concerns arise such as message delivery reliability and fault tolerance for network, hardware and software failures during message transmission. During the coordination of message delivery, to ensure that the messages are delivered without problems acknowledgements for messages are very important. Thus there is a close connection between message acknowledgements and delivery reliability. In this article we will explore message acknowledgement and delivery reliability patterns with respect to Java Message Service (JMS). The scenarios are described using WSO2 Message Broker as the intermediate broker.
Publishing Messages To Message Broker Using Event MediatorStoring mediated messages in an intemediate location to be used later is a huge requirement which all ESB users expect. If it is possible to view those stored messages and modify them, it will be more and more valuable. With using WSO2 ESB and WSO2 MB, it is very easy to fullfill the above task with out any pain. There are only two configurations and once you completed them, you will be there.
Messaging and Eventing in SOAMessaging is used with distributed computing to achieve asynchronous communication. An Event is a change of state in a software system. Eventing is referred to as propagating messages which contain those event information through publish and subscribe. WSO2 Message Broker (WSO2 MB) addresses messaging and eventing in WSO2 Carbon platform. This article gives a detailed description on how those concepts are realized using WSO2 MB with relevant samples.
|