Page Comparison

...

This example scenario demonstrates how WSO2 ESB can be used to activate only a specific amounts amount of services, which are is exposed in to a back-end Axis2 server. Using the publishWSDL, the service WSDL file was modified to filter out only a specific amount of services. The ability of the ESB to create proxy services will allow allows the client to invoke the ESB proxy instead of invoking the service in Axis2 server.      

...

The diagram below depicts how to simulate the example scenario using the WSO2 ESB.

Image Removed

Image Added

Figure 2: Example Scenario of the Service Activator EIP

Before digging into implementation details, let's take a look at the

...

relationship between the example scenario and

...

the Service Activator EIP by comparing their core components.

Environment SetupSet up

1. Download and an install the WSO2 ESB from from http://wso2.com/products/enterprise-service-bus. For a list of prerequisites and step-by-step installation instructions, refer to Installation Guide in Getting Started in the WSO2 ESB documentation.

2. Start two Sample Axis2 server instances in ports 9001 and 9002. For instructions, refer to section section ESB Samples Setup - Starting Sample Back-End Services in in the WSO2 ESB Documentationdocumentation.

ESB Configuration

3. Start the WSO2 ESB and copy the following configuration to the "Source View" in the management console (Main Menu -> Service Bus -> Source View), using which the example scenario can be explored.server and log into its management console UI (https://localhost:9443/carbon). In the management console, navigate to Main Menu, click Service Bus and then Source View. Next, copy and paste the following configuration, which helps you explore the example scenario, to the source view.

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
   <proxy name="ServiceActivatorProxy" startOnLoad="true">
      <target>
         <endpoint>
            <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
         </endpoint>
         <outSequence>
            <send/>
         </outSequence>
      </target>
      <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
   </proxy>
   <sequence name="fault">
      <log level="full">
         <property name="MESSAGE" value="Executing default &#34;fault&#34; sequence"/>
         <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
         <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
      </log>
      <drop/>
   </sequence>
   <sequence name="main">
      <in/>
      <out>
         <send/>
      </out>
   </sequence>
</definitions>

Simulating the Sample Scenario

4. Back-end StockQuoteService offers the following services,:

• getFullQuote
• getMarketActivity
• getQuote
• getSimpleQuote
• placeOrder

But utilizing the publishWSDL feature only Only some of the back-end features will be published through the Service Activator Proxy. browse Browse http://localhost:8280/services/ to view the services offered through the ServiceActivatorProxy the user will be able to notice that apart from , and note that services getMarketActivity and getSimpleQuote all the other services are not available. Others are available and active.  

...