This sample demonstrates how one-way messaging can be done in a fire-and-forget mode through the ESB.
For a list of prerequisites, see Prerequisites to start the ESB samples.
Building the sample
The XML configuration for this sample is as follows:
This configuration file
synapse_sample_12.xml is available in the
To build the sample
Start the ESB with the sample 12 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 the Axis2 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.
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
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.
This sample invokes the one-way
placeOrder operation on the
SimpleStockQuoteService using the custom client which uses the Axis2
To execute the sample client
Run the following command from the
Analyzing the output
Analyze the Axis2 server log.
You will see that the one-way message flows through the ESB into the sample Axis2 server instance, which reports the acceptance of the order as follows:
If you send the client request through TCPmon, you will see that the SimpleStockQuoteService replies to the ESB with a HTTP 202 reply and then the ESB in turn replies to the client with a HTTP 202 acknowledgement.