Note that WSO2 EI is shipped with the following changes to what is mentioned in this documentation :
repository/samples/directory that includes all Integration profile samples is changed to
repository/samples/resources/directory that includes all artifacts related to the Integration profile samples is changed to
This sample demonstrates message routing to a set of dynamic endpoints and aggregate responses.
For a list of prerequisites, see the prerequisites for starting the ESB samples.
Building the sample
The XML configuration for this sample is as follows:
This configuration file
synapse_sample_62.xml is available in the
To build the sample
Start the ESB with the sample 62 configuration. For instructions on starting a sample ESB configuration, see Starting the ESB with a sample configuration.
The operation log keeps running until the server starts, which usually takes several seconds. Wait until the server has fully booted up and displays a message similar to "WSO2 Carbon started in n seconds."
Start three instances of the sample Axis2 server on HTTP ports 9001, 9002 and 9003 and give unique names to each server. For instructions on starting the Axis2 server, see Starting the Axis2 server .
Deploy the back-end service SimpleStockQuoteService. For instructions on deploying sample back-end services, see Deploying sample back-end services.
Executing the sample
The sample client used here is the Stock Quote Client, which can operate in several modes. For further details on this sample client and its operation modes, see Stock Quote Client.
To execute the sample client
Run the following command from the
Analyzing the output
When you have a look at the
synapse_sample_62.xml configuration, you will see that it routes a cloned copy of a message to each recipient defined within the dynamic recipient list , and that each recipient responds back with a stock quote. When all the responses reach the ESB, the responses are aggregated to form the final response, which will be sent back to the client.
If you sent the client request through a TCP based conversation monitoring tool such as TCPMon, you will see the structure of the aggregated response message.