This documentation is for WSO2 Enterprise Service Bus version 4.8.1 . View documentation for the latest release.

All docs This doc
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 2 Next »

Introduction

This sample demonstrates one-way messaging / fireAndForget through ESB.

Prerequisites

For a list of prerequisites, see the Prerequisites section in Setting up the ESB Samples.

Building the Sample

1. Start the ESB with sample 1 configuration using the instructions given in Starting Sample ESB Configurations.

2. A message should appear in the command or text Linux console stating the server started successfully.

3. Deploy the back-end service 'SimpleStockQuoteService' and start the Axis2 server using the instructions given in section Starting Sample Back-End Services.

5. Now you have a running ESB instance and a back-end service deployed. In the next section, we will send a message to the back-end service through the ESB using a sample client.

Executing the Sample

This example invokes the one-way placeOrder operation on the SimpleStockQuoteService using the custom client which uses the Axis2 ServiceClient.fireAndForget() API.

1. The sample client used here is 'Stock Quote Client' which can operate in several modes. For instructions on this sample client and its operation modes, refer to Stock Quote Client. Run the following ant command from <ESB_HOME>/samples/axis2Client directory.

ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dmode=placeorder

2. Note the one-way message flowing through the ESB into the sample Axis2 server instance, which reports the acceptance of the order as follows:

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

3. Send the client request through TCPmon to notice that the SimpleStockQuoteService replies to ESB with a HTTP 202 reply. The ESB in turn replies to the client with a HTTP 202 acknowledgement.

`

  • No labels