Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

The configurations of WSO2 Message Broker (MB) as a JMS input event adapter are explained below. You can configure it with m ap, XML, JSON, and text input  mapping types .

Prerequisites

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

  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  

Configuring the MB input JMS event adapter

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

Configure using the management console

Follow the instructions below to configure WSO2 MB input JMS event adapter using the management console. This deploys the event adapter in the <PRODUCT_HOME> /

repository/ deployment/ server/ inputeventadaptors/ directory.

  1. Log in to product's management console, and click   Configure. 

  2. Click  Input Event Adaptors in the Event Processor Configs menu, and then click Add Input Event Adaptor. 

  3. Enter details as shown in the below example. 

    create input WSO2 MB JMS event adapter

  4. Click   Add Event Adaptor.

Configure using a configuration file

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

When using WSO2 MB 2.0.1 as the input event adapter follow the syntax Burl :{topic} at the time you define the topic, which is a message-related property . Add Burl: as the prefix of the actual topic.

  1. Create an XML file with the following WSO2 MB input event adapter configurations. Input event adapter implementation must start with    <inputEventAdaptor>  as the root element.

    <inputEventAdaptor name="MBJmsInputAdaptor" 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="transport.jms.SubscriptionDurable">false</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>
</inputEventAdaptor>

  2. Add the XML file to the  <PRODUCT_HOME>/repository/deployment/server/inputeventadaptors/  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.

Configuring input JMS event adapter message properties

For instructions on configuring input JMS event adapter message properties, see Configuring Input JMS Event Adapter Message Properties.

 

  • No labels
Unknown macro: {next_previous_links2}