Qpid JMS output event adapter can be used to publish events having map, XML, JSON, and text formats via jms transport.
Prerequisites
Follow the steps below to set up the prerequisites before starting the configuration.
Install Qpid JMS Broker and Qpid JMS Client.
- 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
Refer the
<PRODUCT_HOME>/reposiyory/conf/file to register a connection factory and add the topics to be sent to the ActiveMQ broker. This example uses Topic Connection Factory. Therefore, the following entry points the default ActiveMQ host to localhost and port to 5672:jndi.propertiesconnectionfactory.TopicConnectionFactory=amqp://admin:admin@clientid/default?brokerlist='tcp://localhost:5672'topic.topicMap = topicMaptopic.topicJSON = topicJSONStart Qpid Broker , and then start the product.
Configuring jms output adapter
Qpid JMS output event adapter requires following adapter configurations;
Static Adapter Properties
Adapter Property | Possible Values | Default | Description |
|---|---|---|---|
| JNDI Initial Context Factory Class | org.apache.qpid.jndi.PropertiesFileInitialContextFactory | JNDI initial context factory class. The class must implement the java.naming.spi.InitialContextFactory interface. | |
| JNDI Provider URL | repository/conf/jndi.properties | URL of the JNDI provider. | |
| Username | A valid username for the JMS connection | Set a username for the JMS connection. | |
| Password | A valid password for the JMS connection | Set a password for the JMS connection. | |
| Connection Factory JNDI Name | TopicConnectionFactory | The JNDI name of the connection factory. | |
| Destination Type | topic/queue | topic | Define the sort order for messages that arrive on a specific destination. |
| Destination | topicMap | CEP send messages by publishing to a topic or a queue. |
Dynamic Adapter Properties
Adapter Property | Possible Values | Default | Description |
|---|---|---|---|
| Header | A valid header name: header value pair eg header_name1:header_value1,header_name2:header_value2 | Define Transport Headers |