Versions Compared

Key

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

 The configurations of the Apache ActiveMQ input JMS event adapter are explained below. It can be configured with XML, map, JSON, and text input mapping types.

Excerpt
hiddentrue

NOTE TO WRITERS: Add the TOC here.

Table of Contents
maxLevel3

Prerequisites

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

  1. Install Apache ActiveMQ JMS event adapter. 

    Info

    This guide uses ActiveMQ versions 5.7.0 or below. If you want to use a later version, for instructions on the necessary changes to the configuration steps, go to Apache ActiveMQ Documentation.

  2. Add the following ActiveMQ JMS-specific JAR files to  <PRODUCT_HOME>/repository/components/lib/ directory.  
    • <ACTIVEMQ_HOME>/lib/activemq-core-xxx.jar  
    • <ACTIVEMQ_HOME>/lib/geronimo-j2ee-management_1.1_spec-1.0.1.jar

Configuring the ActiveMQ input JMS event adapter

You can configure the ActiveMQ input JMS event adapter either using the management console or using a configuration file as explained below.

Anchor
Using the management console
Using the management console
Configure using the management console

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

...

  1. Start ActiveMQ, and then start the product. 

  2. Log in to the product's management console and click Configure.
  3. Click Input Event Adaptors in the Event Processor Configs menu, and then click Add Input Event Adaptor.
  4. Enter details as shown in the below example.
    create input  ActiveMQ JMS event adapter 
  5. Click Add Event Adaptor.

Anchor
Using a configuration file
Using a configuration file
Configure using a configuration file

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

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

    Code Block
    languagehtml/xml
    <inputEventAdaptor name="activemqJmsInputAdaptor" statistics="disable"
      trace="disable" type="jms" xmlns="http://wso2.org/carbon/eventadaptormanager">
      <property name="java.naming.provider.url">tcp://localhost:61616</property>
      <property name="transport.jms.SubscriptionDurable">false</property>
      <property name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</property>
      <property name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</property>
      <property name="transport.jms.DestinationType">topic</property>
    </inputEventAdaptor>
  2.  Add the XML file to <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.

Info

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.

 

Excerpt
hiddentrue

NOTE TO WRITERS: Link "Configuring Input JMS Event Adapter Message Properties" of the above text to the page titled the same.