Complex Event Processor 3.0.0
Expand all   Collapse all
Child pages
  • Output Qpid JMS Event Adapter

This documentation is for WSO2 CEP 3.0.0. View the home page of the latest release.

                                                                                                                                                                                                                                                                                                                                                                                                       
||
Skip to end of metadata
Go to start of metadata

The configurations of the Apache Qpid output JMS event adapter are explained below. You can configure it with map, XML, JSON, and text output  mapping types.

Prerequisites

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

  1. Install Qpid JMS Broker and Qpid JMS Client.

  2. Add the following Qpid JMS-specific JAR files to  <PRODUCT_HOME>/repository/components/lib/ directory.   
    • <ACTIVEMQ_HOME>/lib/geronimo-jms_1.1_spec-1.0.jar   
    • <QPID-CLIENT_HOME>/lib/qpid-client-xxx.jar
    • <QPID-CLIENT_HOME>/lib/qpid-common-xxx.jar 

Configuring the Qpid output JMS event adapter

You can configure the Qpid output JMS event adapter using the management console or using a configuration file as explained below. This deploys the event adapter in the <PRODUCT_HOME>/repository/ deployment/ server/ outputeventadaptors/ directory.

Configure using the management console

Follow the instructions below to configure JMS Qpid output event adapter.

  1. Log in to the product's management console, and click Configure.

  2. Click Output Event Adaptors in the Event Processor Configs menu, and then click Add Output Event Adaptor.

  3. Enter details as shown in the below example.

    Refer the <PRODUCT_HOME>/reposiyory/conf/jndi.properties file. This example uses Topic Connection Factory. Therefore, the following entry points the default Qpid host to localhost and port to 5672:
    connectionfactory.TopicConnectionFactory = amqp:     //admin:[email protected]/test?brokerlist='tcp://localhost:5672'


    create output Qpid JMS event adapter

  4. Click Add Event Adaptor.

Configure using a configuration file

Follow the instructions below to configure Qpid output JMS event adapter using a configuration file.

  1. Create an XML file with the following Qpid output event adapter configurations. Output event adapter implementation must start with <outputEventAdaptor> as the root element. 

    <outputEventAdaptor name="QpidJmsOutputAdaptor" statistics="disable"
  trace="disable" type="jms" xmlns="http://wso2.org/carbon/eventadaptormanager">
  <property name="java.naming.provider.url">repository/conf/jndi.properties</property>
  <property name="java.naming.factory.initial">org.apache.qpid.jndi.PropertiesFileInitialContextFactory</property>
  <property name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</property>
  <property name="transport.jms.DestinationType">topic</property>
</outputEventAdaptor>

  2. Add the XML file to the <PRODUCT_HOME>/repository/deployment/server/outputeventadaptors/ directory. Since hot deployment is enabled, you can simply add/remove files to deploy/undeploy to/from the server.  

 

After an adapter is successfully added, it gets added to the list of adapters displayed under Event Processor Configs in the Configure menu of the product's management console. Click Edit to change its configuration and redeploy it. This opens an XML-based editor allowing you to edit the event adapter configurations from the UI. Do your modifications and click Update. You can also delete it, enable/disable statistics or enable/disable tracing on it using the provided options in the UI.

Configuring output JMS event adapter message properties

For instructions on configuring output JMS event adapter message properties, see Configuring Output JMS Event Adapter Message Properties.
  • No labels
||

 
Copyright © WSO2 Inc. 2005-2015