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 how to copy message content to a property as well as how to enrich a message from a given source.
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_15.xml is available in the
To build the sample
Start the ESB with the sample 15 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.
To execute the sample client
Run the following command from the
Analyzing the output
When you analyze the debug log output on the ESB console, you will see that the original IBM request is changed to MSFT using the enrich mediator.
According to the configuration file
synapse_sample_15.xml, the original payload and the symbol is stored as synapse properties. Once the reply comes to synapse, the
lastTradeTimestamp value of the response is added as a soap header in order to show the functionality of the enrich mediator. Also the request payload and request symbol values are logged in the out sequence.
Different parts of the message are stored in or copied to properties inside the in-sequence. Just before sending the message to the a back-end service the request value is modified based on the local entry. Then in the out-sequence, the enrich mediator is used to enrich the soap header based on the lastTradeTimestamp value of the response.
You can try this sample with different local entries as the source with the correct target xpath values.