Qpid JMS output event adapter is used to publish events in map, XML, JSON, and text formats via JMS transport.
...
Install Qpid JMS Broker and Qpid JMS Client.
- Add the following Qpid JMS-specific JAR files to
<CEP_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
Register a connection factory in the
<CEP_HOME>/repository/conf/jndi.properties
. For example, if the connection factory JNDI name isTopicConnectionFactory
, it will point the default Qpid host to localhost and port to 5672 as shown below. Furthermore, add the topics to be sent to the Qpid broker in the format: topic.{topicName} = {topicName}Code Block language text connectionfactory.TopicConnectionFactory=amqp://admin:admin@clientid/default?brokerlist='tcp://localhost:5672' topic.topicMap = topicMap topic.topicJSON = topicJSON
Start Qpid Broker, and then start the product.
Creating a Qpid JMS output event adapter
...
For instructions on creating a Qpid JMS output event adapter, see Publishing Events .
Configuring adapter properties
...
Specify the Static and Dynamic Adapter Properties, when creating a Qpid JMS output event adapter using the management console as shown below.
...
Adapter Property | Description | Configuration file property | Example |
---|---|---|---|
JNDI Initial Context Factory Class | The JNDI initial context factory class. The class must implement the java.naming.spi.InitialContextFactory interface | java.naming.factory.initial | org.apache.qpid.jndi.PropertiesFileInitialContextFactory |
JNDI Provider URL | URL of the JNDI provider | java.naming.provider.url | repository/conf/jndi.properties |
Username | Valid username for the JMS connection | transport.jms.UserName | jms-user |
Password | Valid password for the JMS connection | transport.jms.Password | jms-password |
Connection Factory JNDI Name | The JNDI name of the connection factory | transport.jms.ConnectionFactoryJNDIName | TopicConnectionFactory |
Destination Type | The sort order for messages that arrive on a specific destination | transport.jms.DestinationType | topic/queue |
Destination | The topic or queue to which WSO2 CEP sends messages by publishing. | transport.jms.Destination | test_topic |
...
Adapter Property | Description | Configuration file property | Example |
---|---|---|---|
Header | Define Transport Headers as a valid header name in a header value pair format | transport.jms.Header | header_name1:header_value1,header_name2:header_value2 |