WSO2 Message Broker JMS Event Receiver

WSO2 Message Broker (MB) JMS event receiver is an internal event receiver that comes with WSO2 products by default . You can configure it with map, XML, JSON, and text input mapping types.

Prerequisites

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

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

Creating a WSO2 MB JMS event receiver

For instructions on creating a WSO2 MB JMS event receiver, see Configuring Event Receivers .

Configuring adapter properties

Specify the Adapter Properties , when creating a WSO2 MB JMS event receiver using the management console as shown below.

After entering the above adapter properties, select the Event Stream to which you want to map the incoming events, and the Message Format which you want to apply on the receiving events. Also, click Advanced to define custom input mappings based on the Message Format you selected. For more information on custom input mapping types, see Input Mapping Types .

You can also d efine the respective adapter properties of the event receiver based on the transport type within the <from> element of the event receiver configuration in the <PRODUCT_HOME>/repository/deployment/server/eventreceivers/ directory as follows.

<eventReceiver name="WSO2MBJMSInputEventAdapter" statistics="disable" trace="disable" xmlns="http://wso2.org/carbon/eventreceiver">
    <from eventAdapterType="jms">
        <property name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</property>
        <property name="java.naming.provider.url">repository/conf/jndi.properties</property>
        <property name="transport.jms.DestinationType">topic</property>
        <property name="transport.jms.SubscriptionDurable">false</property>
        <property name="transport.jms.Destination">test_topic</property>
        <property name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</property>
        <property encrypted="true" name="transport.jms.Password">P2ve4G8+qF7JXkiGnP9/Ew5GXALEWTu7znEwxZGYa/MQMaQBRfsXiP094fn9U+0rntdBMitXU9o7h5uV3m5h97Po8WTJRpnFBV5YCGZEO+ELSg6twY3386MipwFhFMrbUMKamI2sXksDRcogojWKtoHNmODnt8Ud1dh0LK5zqec=        </property>
        <property name="transport.jms.UserName">jms-user</property>
        <property name="transport.jms.DurableSubscriberClientID">subscriber</property>
        <property name="jms.properties">SessionTransacted:false</property>
    </from>
    .....................
</eventReceiver>

The above adapter properties are described below.

Related samples

For more information on WSO2 MB event receiver type, see the following sample in WSO2 CEP Documentation.

Sample 0013 - Receiving Map, Text Events via JMS Transport - WSO2 MB