Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

  1. Download and install WSO2 Message Broker (MB). For instructions on WSO2 MB, go to Message Broker documentation.

  2. 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  

...

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

WSO2 MB JMS input event adapter propertiesImage Removed Image Added

Info

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 .

...

Code Block
languagexml
<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.DurableSubscriberNameDurableSubscriberClientID">subscriber</property>
        <property name="jms.properties">SessionTransacted:false</property>
    </from>
    .....................
</eventReceiver> 

The above adapter properties are described below.

...

Valid name for the JMS topic. WSO2 CEP/DAS sends and receives messages by subscribing to a topic or using named queues.

...

transport.jms.Destination

...

JNDI initial context factory class. The class must implement the java.naming.spi.InitialContextFactory interface.

...

java.naming.factory.initial

...

java.naming.provider.url

...

transport.jms.Password

...

transport.jms.UserName

...

transport.jms.ConnectionFactoryJNDIName

...

transport.jms.DestinationType

...

transport.jms.SubscriptionDurable

...

A valid name of the durable subscriber (If any value added, Durable subscription will be enabled).

...

transport.jms.DurableSubscriberName

...

.

...

For more information on Axis2 JMS properties, go to Apache AXIS2 Transports Documentation.

...

jms.properties

...

Related samples

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