Page Comparison

...

Create a proxy service with the following configuration. For information on how to create a proxy service, see Creating a Proxy Service.

Code Block

language	xml

<proxy xmlns="http://ws.apache.org/ns/synapse" name="JMStoHTTPStockQuoteProxy" transports="jms">
       <target>
           <inSequence>
               <property action="set" name="OUT_ONLY" value="true"/>
           </inSequence>
           <endpoint>
               <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
           </endpoint>
           <outSequence>
               <send/>
           </outSequence>
       </target>
</proxy>

Tip

title	Proxy Service ConfigurationTip

The OUT_ONLY property is set to true to indicate that message exchange is one-way.

You can make the proxy service a JMS listener by setting the transport as jms. Once the JMS transport is enabled for a proxy service, the ESB starts listening on a JMS queue with the same name as the proxy service.

If you take a look at the sample configuration above, the ESB listens to a JMS queue named JMStoHTTPStockQuoteProxy. To make the proxy service listen to a different JMS queue, define the transport.jms.Destination parameter with the name of the destination queue.

...

Code Block

language	html/xml

<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="Proxy1"
       transports="jms"
       startOnLoad="true"
       trace="disable">
   <description/>
   <target> 
      <inSequence>
         <send>
            <endpoint>
               <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
            </endpoint>
         </send>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </target>
   <parameter name="transport.jms.ContentType">
      <rules>
         <jmsProperty>contentType</jmsProperty>
         <default>text/xml</default>
      </rules>
   </parameter>
</proxy>

Tipinfo

title	Note

In two-way JMS scenarios the OUT_ONLY property is not used.

Execute the following command from the <ESB_HOME>/samples/axis2Client directory.

Tip

title	Tip

See how the transport.jms.ReplyDestination element is specified.

Code Block

language	xml

ant stockquote -Dsymbol=WSO2 -Dtrpurl="jms:/JMStoHTTPStockQuoteProxy?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.ContentTypeProperty=Content-Type&transport.jms.DestinationType=queue&transport.jms.ReplyDestination=ResponseQueue"

You can view the responses from the back-end service in the ResponseQueue by accessing the ActiveMQ management console via http://0.0.0.0:8161/admin, and using admin as both the username and password.

Defining the content type of incoming JMS messages

...

Anchor

	differentQueueName
	differentQueueName

Tip

title	Proxy Service ConfigurationTip

You can specify a different content type within the transport.jms.ContentType parameter. In the configuration above, the content type is defined as application/xml.

If you want the proxy service to listen to a queue where the queue name is different from the proxy service name, you can specify the queue name using the transport.jms.Destination parameter. In the configuration above the ESB listens to a JMS queue named MyJMSQueue.

Versions Compared

Old Version 4

New Version Current

Key

Defining the content type of incoming JMS messages