WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.
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 CEP:

    • Start WSO2 MB 3.0.0
  2. Configure WSO2 CEP by adding relevant libraries to support JMS transport

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

  4. Open the  <CEP_HOME>/repository/conf/ file and register a connection factory named TopicConnectionFactory by entering the following in the register some connection factories section. And 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 CEP server with the sample configuration numbered 0061 with an off-port since the WSO2 MB has started 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  <CEP_HOME>/repository/deployment/server to <CEP_HOME>/sample/artifacts/0061
  • Creates a stream with id
  • Create and event publisher namely jmsPublisherMap, jmsPublisherXML
  • Hot deploys event.csv file along with event configuration xml

Executing the sample

  1. Start WSO2 CEP with sample 0061 configurations. For more information, see Starting sample CEP configurations.
  2. Open two separate terminals for <CEP_HOME>/samples/cep/consumers/jms,and run the following commands according to the type of topic name of the messages suppose to consume

    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.

  4. You can see the events getting published by CEP by the logs in the jms consumer console.

    for Map formatted events: 

    for XML formatted events:

  • No labels