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 the PayloadFactory Mediator can be used to perform transformations as an alternative to the XSLT mediator, which is demonstrated in Sample 8: Introduction to Static and Dynamic Registry Resources and Using XSLT Transformations . In this sample, the ESB implements the message translator enterprise integration pattern, and acts as a translator between the client and the back-end server when mediating a message to the sample back-end server from a sample client.
In this scenario, there is a web service endpoint that has the
getQuote operation that expects a symbol parameter. However, the client that invokes the service sends the
getQuote operation with the Code parameter. Therefore, the request message will be sent in the following format:
The service expects the message in the following format:
Similarly, the service will send the response in the following format:
The client expects the response in the following format:
To resolve this discrepancy, the PayloadFactory mediator is used to transform the message into the request format required by the service and the response format required by the client.
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_17.xml is available in the
To build the sample
Start the ESB with the sample 17 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 incoming message is transformed by the PayloadFactory Mediator into a standard stock quote request as expected by the SimpleStockQuoteService deployed on the Axis2 server.
printf() style formatting is used to configure the transformation performed by the mediator. Each argument in the mediator configuration can be a static value or an XPath expression.
When an expression is used, the argument value is fetched at runtime by evaluating the provided XPath expression against the existing SOAP message.
The response from the SimpleStockQuoteService is converted back into the custom format as expected by the client during the out message processing, once again using the PayloadFactory Mediator.