This documentation is for WSO2 ESB version 4.8.0. View documentation for the latest release.

||
Skip to end of metadata
Go to start of metadata

Introduction

This sample demonstrates simple content-based routing where a message is passed through the ESB in the Dumb-Client mode. The ESB acts as a gateway to accept all messages, and then performs mediation and routing based on message properties or content.

Prerequisites

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

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. The synapse configuration for the ESB used for message mediation in this sample is provided in <ESB_HOME>/repository/samples/synapse_sample_1.xml as shown below:

4. 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

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 each of the following ant command from <ESB_HOME>/samples/axis2Client directory to trigger a sample message to the back-end service. If the message is mediated successfully, it should display an output on the Axis2 server's start-up console.

Dumb Client Mode

Execute the Dumb Client as:

Note the ESB receiving a message to which ESB is set as the ultimate receiver. ESB performs a match to the path /StockQuote based on the To EPR in the following location: http://localhost:8280/services/StockQuote

 As the request matches the XPath expression of the Filter Mediator, the Filter Mediator's child mediators execute. It sends the message to a different endpoint as specified by the endpoint definition. During response processing, the filter condition fails. Therefore, the implicit Send Mediator forwards the response back to the client.
  • No labels