The latest version for DAS is WSO2 Data Analytics Server 3.1.0. View documentation for the latest release.
WSO2 Data Analytics Server is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

All docs This doc
Skip to end of metadata
Go to start of metadata


This sample demonstrates how to publish map and XML events via JMS transport. You consume the published events in CEP using a JMS client which is subscribed to WSO2 Message Broker. This sample does not do any processing on the outgoing event. 


Follow the steps below to set up the prerequisites before starting the configuration.

  1. Before you configure the WSO2 DAS, start WSO2 MB (version 3.0.0 or later).

  2. Configure WSO2 DAS by adding relevant libraries to support JMS transport.

  3. Configure a sample client by adding relevant jars. See setting up JMS for JMS sample clients.

  4. Open the  <DAS_HOME>/repository/conf/ file and register a connection factory named TopicConnectionFactory by entering the following in the register some connection factories section. Then add the topics to be sent to the Qpid broker.


    connectionfactory.TopicConnectionFactory=amqp: //admin:[email protected]/carbon?brokerlist='tcp://localhost:5672'
    topic.topicMap = topicMap
    topic.topicXML = topicXML

Building the sample 

Start the WSO2 DAS server with the sample configuration numbered 0061 with a port offset because WSO2 MB is running in the default port. For instructions, see Starting sample CEP configurations and append - DportOffset=1 -Dqpid.dest_syntax=BURL  to the command as follows.

./ -sn 0061 -DportOffset=1 -Dqpid.dest_syntax=BURL

  • Changes the default Axis2 repo from  <DAS_HOME>/repository/deployment/server to <DAS_HOME>/sample/cep/artifacts/0061.
  • Creates a stream with ID
  • Creates event publishers named jmsPublisherMap and jmsPublisherXML.
  • Hot deploys the event.csv file along with the event configuration.xml file.

Executing the sample

  1. Start WSO2 DAS with sample 0061 configurations. For more information, see Starting sample CEP configurations.
  2. Issue the following commands from the <DAS_HOME>/samples/cep/consumers/jms directory using a separate terminal for each command. The commands should be issued according to the type of the topic name of the messages to be consumed.

    ant -Dbroker=mb -DtopicName=topicMap
    ant -Dbroker=mb -DtopicName=topicXML

    It subscribes to the WSO2 Message Broker under the mentioned topic name.

  3. Play the event.csv file deployed using the Event Simulator. This will send an event flow through the stream to the JMS publishers. For detailed instructions to play a file, see Sending Multiple Events Using a CSV File.

  4. Events published by WSO2 DAS are logged in the JMS consumer console as shown below.Y

    for Map formatted events: 

    for XML formatted events:

  • No labels