Output WSO2 Message Broker JMS Event Adapter

Follow the instructions below to configure WSO2 Message Broker (MB) as a JMS output event adapter. 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.

Download and install WSO2 Message Broker. For instructions on WSO2 MB, go to Message Broker documentation.
Add the following JMS -specific JAR files to <PRODUCT_HOME>/repository/components/lib/ directory.
- <WSO2MB_HOME>/client-lib/andes-client-xx.jar
- <WSO2MB_HOME>/client-lib/geronimo-j2ee-management_1.1_spec-1.0.1xx.jar

Configuring the MB output JMS event adapter

You can configure WSO2 MB JMS output event adapter using the management console or using a configuration file.

When using WSO2 MB as the JMS message broker, add an entry to <PRODUCT_HOME>/reposiyory/conf/jndi.properties file in the following format to register the topic: topic.{topicName} = {topicName}. For an example, if the value of the field destination is BasicStockQuotes, then add the following entry: topic.BasicStockQuotes = BasicStockQuotes

Configure using the management console

Follow the instructions below to configure WSO2 MB output JMS event adapter using the management console. This deploys the event adapter in the <PRODUCT_HOME>/repository/deployment/server/outputeventadaptors/ directory.

Log in to product's management console, and click Configure.
Click Output Event Adaptors in the Event Processor Configs menu, and then click Add Output Event Adaptor.
Enter details as shown in the below example.
Click Add Event Adaptor.

Configure using a configuration file

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

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

<outputEventAdaptor name="MBJmsOutputAdaptor" 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.wso2.andes.jndi.PropertiesFileInitialContextFactory</property>
  <property name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</property>
  <property name="transport.jms.DestinationType">topic</property>
</outputEventAdaptor>

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.

When using WSO2 MB as the output event adapter, start product server by executing the following command: -Dqpid.dest_syntax=BURL. (For example: ./wso2server.sh -Dqpid.dest_syntax=BURL)

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.