Page Comparison

This section describes how to configure WSO2 ESB Enterprise Integrator (WSO2 EI) to work as a JMS-to-JMS proxy service.

...

Follow the steps below to configure WSO2 ESB WSO2 EIto listen to a JMS queue and consume messages and then send those messages to another JMS queue.

Configure WSO2 ESB EI with Apache ActiveMQ and set up the JMS listener and sender. For instructions, see Configure with ActiveMQ.

Create a proxy service with the following configuration.To create a proxy service using ESB Tooling, see Working with Proxy Services via ESB Tooling.

Code Block

<proxy name="StockQuoteProxy" transports="jms">
   <target>
       <inSequence>
           <property action="set" name="OUT_ONLY" value="true"/>
           <send>
               <endpoint>
                  <address uri="jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&            java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616"/>
               </endpoint>
           </send>
       </inSequence>
   </target>
</proxy>

Note
When entering the above URLs in the management console, replace '`&`' character in the endpoint URL with '`&`'

Tip
In the sample configuration above, ESB WSO2 EI listens to a JMS queue named `StockQuoteProxy` and sends messages to another queue named `SimpleStockQuoteService.`

To place a message into a JMS queue, execute following command from <ESB<EI_HOME>/samples/axis2Client directory.

...

Generally, JMS is used for one-way, asynchronous message exchange. However you can perform synchronous messaging also with JMS. For more information, see JMS Synchronous Invocations : Dual Channel HTTP-to-JMS /wiki/spaces/EI600/pages/46727545 and JMS Synchronous Invocations : Quad Channel JMS-to-JMS.

Versions Compared

Old Version 1

New Version Current

Key