This section describes how to configure the WSO2 ESB's JMS transport with ActiveMQ 5.5.1. Follow the instructions below to set up and configure.
1. Download and set up Apache ActiveMQ. Instructions can be found in section Installation Prerequisites.
2. Follow the Getting Started and set up WSO2 ESB.
Info |
---|
ActiveMQ should be up and running before starting the ESB. |
3. Copy the following client libraries from <AMQ_HOME>/lib directory to < ESB_HOME>/repository/components/lib directory.
...
ActiveMQ 5.8.0 and
...
above
- activemq- core
- broker-5. 5
- 8. 1
- 0.jar has been split into
- activemq- broker
- client-5.8.0.jar and
- activemq-kahadb- client
- store-5.8.0.jar
- geronimo-jms_1.1_spec-1.1.1.jar )
- geronimo-j2ee-management_1. 0
- 1_spec-1.0.1.jar
- geronimo- jms
- jta_1.0. 1
- 1B_spec-1.0.1.jar
- hawtbuf-1. jarIf you are using ActiveMQ version 5.8.0 or later, copy hawtbuf-1.2.jar to < ESB_HOME>/repository/components/lib directory .
- 9.jar
- Slf4j-api-1.6.6.jar
- activeio-core-3.1.4.jar (available in
<AMQ_HOME>/lib/optional
folder)
Earlier version of ActiveMQ
activemq-core-5.5.1.jar
geronimo-j2ee-management_1.0_spec-1.0.jar
geronimo-jms_1.1_spec-1.1.1.jar
4. Next, configure transport listeners and senders in ESB.
Note |
---|
When configuring JMS with ActiveMQ, you can append ActiveMQ-specific properties to the value of the
|
Setting up the JMS Listener
To enable the JMS transport listener, un-comment the following listener configuration related to ActiveMQ in <ESB_HOME>/repository/conf/axis2/axis2.xml file.
Code Block | ||
---|---|---|
| ||
<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> <parameter name="myTopicConnectionFactory" locked="false"> <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter> </parameter> <parameter name="myQueueConnectionFactory" locked="false"> <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter> </parameter> <parameter name="default" locked="false"> <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter> </parameter> </transportReceiver> |
Setting up the JMS Sender
To enable the JMS transport sender, un-comment the following configuration in <ESB_HOME>/repository/conf/axis2/axis2.xml file.
Code Block | ||
---|---|---|
| ||
<transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"/> |
Info |
---|
For details on the JMS configuration parameters used in the code segments above, see JMS Connection Factory Parameters. |
...