This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

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 4 Next »

Objective: Demonstrate one way message bridging from JMS to HTTP using inbound JMS endpoint.

Prerequisites
  • Download and set up Apache ActiveMQ. Instructions can be found in section Installation Prerequisites. 

  • Copy the following client libraries from <AMQ_HOME>/lib directory to <ESB_HOME>/repository/components/lib directory. 

            ActiveMQ 5.8.0 and above 
    • activemq-broker-5.8.0.jar
    • activemq-client-5.8.0.jar
    • geronimo-jms_1.1_spec-1.1.1.jar
    • geronimo-j2ee-management_1.1_spec-1.0.1.jar
    • hawtbuf-1.9.jar 

          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

  • Start the Axis2 server and deploy the SimpleStockQuoteService if not already done.
  • Start the Synapse configuration numbered 901: wso2esb-samples.sh -sn 901
 

This example invokes the one-way placeOrder operation on the SimpleStockQuoteService using the Axis2 ServiceClient.fireAndForget() API at the client. To test this, use ant -Dmode=placeorder... and you will notice the one way JMS message flowing through ESB into the sample Axis2 server instance over HTTP, and Axis2 acknowledging it with a HTTP 202 Accepted response.

ant stockquote -Dmode=placeorder -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"

SimpleStockQuoteService :: Accepted order for : 7482 stocks of IBM at $ 169.27205579038733

The second example shows how ESB can be made to respond with a HTTP 202 Accepted response to a request received. The Proxy Service simply logs the message received and acknowledges it. On the ESB console you could see the logged message, and if TCPMon was used at the client, you would see the 202 Accepted response sent back to the client from ESB.

ant stockquote -Dmode=placeorder -Dtrpurl=http://localhost:8280/services/OneWayProxy

HTTP/1.1 202 Accepted
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1
SOAPAction: "urn:placeOrder"
Date: Sun, 06 May 2007 17:20:19 GMT
Server: Synapse-HttpComponents-NIO
Transfer-Encoding: chunked

0
  • No labels