This is the latest release in the 6.x.x family. For EI 7.0.0, click here.

All docs This doc
Skip to end of metadata
Go to start of metadata

Note that WSO2 EI is shipped with the following changes to what is mentioned in this documentation:

  • <PRODUCT_HOME>/repository/samples/ directory that includes all Integration profile samples is changed to <EI_HOME>/samples/service-bus/.
  • <PRODUCT_HOME>/repository/samples/resources/ directory that includes all artifacts related to the Integration profile samples is changed to <EI_HOME>/samples/service-bus/resources/.

Objective: Demonstrate the use of the Call mediator for non-blocking web service invocations. It also demonstrates how we can use the Call mediator to implement service chaining scenarios.

<definitions xmlns="">
    <proxy  xmlns=""
           transports="https http"
                    <endpoint key="StockQuoteService"/>
                <header name="Action" value="urn:getQuote"/>
                        <m0:getQuote xmlns:m0="http://services.samples">
                    <endpoint key="StockQuoteService"/>
    <endpoint name="StockQuoteService">
        <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>


  • Deploy the SimpleStockQuoteService in sample Axis2 server, and start it on port 9000.
  • Create the above configuration and deploy it in the WSO2 EI profile, see Working with WSO2 Integration Studio.

In this sample, Call mediator does a direct service invocation to the StockQuoteService using the client request. After getting the response, a new payload is constructed using the Payload Factory mediator, and we invoke the StockQuoteService using the Call mediator again. Then, using the Respond mediator, the message is sent back to the client.

Invoke the client as follows.

ant stockquote -Dtrpurl=http://localhost:8280/services/StockQuoteProxy
  • No labels