This sample demonstrates how to receive incoming JSON, 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.
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.
<CEP_HOME>/repository/conf/jndi.propertiesfile and register a connection factory named
TopicConnectionFactoryby entering the following in the
register some connection factoriessection. ( the "default" is the name of the virtually hosted node in Qpid)
By default jndi.properties file may contain a connection factory named TopicConnectionFactory. You can simply replace it with above to register for Qpid as shown below.
# register some connection factories
# connectionfactory.[jndiname] = [ConnectionURL]
Start JMS-Qpid Broker using command 'bin\qpid-server' from Qpid Broker home.
Building the sample
Start the WSO2 CEP server with the sample configuration numbered 0012. For instructions, see Starting sample CEP configurations. This sample configuration does the following:
- Changes the default Axis2 repo from
- Creates a stream named
- Creates three event receivers named
- Creates an event publisher named
jmsLoggerto log the received messages.
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=topicMap -Dformat=map -Dbroker=qpid -Dsn=0012
ant -DtopicName=topicXML -Dformat=xml -Dbroker=qpid -Dsn=0012
It builds the jms client and publishes the events at
topicXML.txtto the jms receiver endpoint.
You can see the events getting received by CEP by the logs in its console.
for Map formatted events:
for XML formatted events: