This sample demonstrates how to receive incoming JSON, Text, XML events adheres WSO2 Event format via jms transport. Here we do not do any processing on the incoming event and to verify the messages we use log event publisher to log the received event.
Follow the steps below to set up the prerequisites before starting the configuration.
Set up the prerequisites required for all samples.
<ACTIVEMQ_HOME>/bin/directory, and execute the following command to start the Apache ActiveMQ server:
This guide uses ActiveMQ versions 5.7.0 - 5.9.0. If you want to use a later version, for instructions on the necessary changes to the configuration steps, go to Apache ActiveMQ Documentation.
Configure WSO2 CEP by adding relevant libraries to support JMS transport.
Configure sample client by adding relevant jars. See setting up JMS for JMS sample clients.
Building the sample
Start the WSO2 CEP server with the sample configuration numbered 0011. For instructions, see Starting sample CEP configurations. This sample configuration does the following:
- Changes the default Axis2 repo from
- Creates a stream with id org.wso2.event.sensor.stream:1.0.0.
- Create and event receivers namely jmsReceiverJSON, jmsReceiverText, jmsReceiverXML
- Create and event publisher to log the received messages with name jmsLogger.
Executing the sample
Wait until the CEP terminal prompts a message similar as follows.
Open another terminal, go to
and run one of the the following commands according to the type of event format to be published:
ant -DtopicName=topicJSON -Dformat=json -Dbroker=activemq -Dsn=0011
ant -DtopicName=topicText -Dformat=text -Dbroker=activemq -Dsn=0011
ant -DtopicName=topicXML -Dformat=xml -Dbroker=activemq -Dsn=0011
It builds the jms client and publishes the events at
<CEP_HOME>/samples/cep/artifacts/0011/topicMap.csvto the jms receiver endpoint.
You can see the events getting received by CEP by the logs in its console.
for JSON formatted events:
for Text formatted events:
for XML formatted events: