WSO2 Message Broker brings messaging and eventing capabilities into your SOA framework. This latest addition to the WSO2 family of products possesses following key features.

  • WS-Eventing
  • Message store based on Amazon SQS API
  • JMS Pub/Sub and Queuing

The underlying messaging framework of the WSO2 Message Broker is powered by Apache Qpid, one of the leading Advanced Message Queuing Protocol (AMQP) messaging engines available today. The Message Broker is compliant with the latest WS-Eventing specification. It's easy-to-use Amazon SQS API provides a standard interface for your message queuing requirements.The underlying JMS engine handles WS-Eventing/JMS synchronisation that enables exposing and consuming your events using two different standard API's.

Articles

Messaging and Eventing in SOA

- Amila Suriarachchi
Messaging 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.
More Articles
Webinars

Await!

Forums

Error in address endpoint while sending a message to JMS queue

I am trying to send messages to a queue on MB.
Wed, 4th Jan, 2012 - 21.27 PST

qpid-client-0.11.0.wso2v2.jar - maven repo ambiguity

   I googled for maven2 repository and found http://dist.wso2.org/maven2/org/apache/qpid/qpid-client/. Judging by the artifact name I thought it was the one I needed but it turned out that it lacks v2 of the jar (it only holds 0.9-wso2v1 and 0.11-wso2v1).   Another google query led me to http://dist.wso2.org/maven2/org/apache/qpid/wso2/qpid-client/ (mind the wso2 part). And qpid-client-0.11.0.wso2v2.jar is there.  
Fri, 25th Nov, 2011 - 01.37 PST

Using Message Broker with JMS in a Java/Spring/GRails application

Hi. I am trying to use WSo2 Messsage Broker(ver. 1.0.2) with a GRails(ver. 1.3.7) application and i run into some connection (I think) problems. In order to use the grails jms plugin(ver. 1.2) I have to create a bean responsible for connecting to the server. To do that i have to use a ConnectionFactory class. I found out that my broker is using something like org.apache.qpid.client.AMQConnectionFactory, but i'm not sure if it is the right one. I had to add the qpid-client jar from server folder to the classpath My code is: resources.groovy:
Tue, 22nd Nov, 2011 - 11.37 PST

Creating Axis2 Asynchronous Webservice(Server Side)

We are trying to implement Axis 2 Asynchronous webservice but we dnt know how to test that webservice, to make sure that is asynchronous or not. Is it require for us to enable WS-Addressing in Axis2 ? if it is that so how do we do that ?
Thu, 10th Nov, 2011 - 19.33 PST

How to use Message Broker queues in ESB

Hi everyone! I have a problem... I have created a proxy service in my wso2 ESB. This proxy use the JMS transport protocol. I have already created a queue on the Message Broker, and i have configured the jms transport in axis2.xml and axis2-client.xml files. I want to use this queue to store the messages send to the proxy when the proxed service is down. It's possible to implement this scenario?
Mon, 17th Oct, 2011 - 06.59 PDT
Read More
library project main code
Taxonomy Categories (MB)
  • Message Broker Home
  • Documentation
    • Popular Content