This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, go to

Content Enricher

This section explains, through an example scenario, how the Content Enricher EIP can be implemented using the ESB profile of WSO2 EI. The following topics are covered:

Introduction to Content Enricher

The Content Enricher EIP facilitates communication with another system if the message originator does not have all the required data items available. It accesses an external data source to augment a message with missing information. For more information, refer to

Figure 1: Content Enricher EIP

Example scenario

This example scenario depicts a stock quote service. The client sends a stock quote request to the ESB with only an identity number. But in order to provide a stock quote, the sample Axis2 server at the back-end needs to map the identity number with a corresponding name, which is in an external source. The values are stored in the registry as a local entry. When the request arrives, the identity will be analyzed using the Switch mediator. Sequentially, the identity number will be replaced with the local entry using the Enrich mediator.

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

Figure 2: Example Scenario of the Content Enricher EIP

Before digging into implementation details, let's take a look at the relationship between the example scenario and the Content Enricher EIP by comparing their core components.


Content Enricher EIP (Figure 1)Content Enricher Example Scenario (Figure 2)
Basic MessageStock Quote Request from Stock Quote Client
EnricherEnrich Mediator
ResourceLocal Registry
Enriched MessageEnriched Stock Quote Request from the ESB profile of WSO2 EI

Environment setup

  1. Download and install WSO2 Enterprise Integrator. For a list of prerequisites and step-by-step installation instructions, see the the ESB profile of WSO2 EI Installation Guide.
  2. Start two Sample Axis2 server instances on ports 9000 and 9002. For instructions, see Setting Up the Service Bus Samples - Starting the Axis2 server.

Service bus configuration

Start the Integration Profile of the ESB profile of WSO2 EI and log into its management console UI (https: //localhost:9443/carbon). In the management console, navigate to the Main menu and click Source View in the Service Bus section . Next, copy and paste the following configuration, which helps you explore the example scenario, to the source view.   

<!-- Content Enricher -->
<definitions xmlns="">
     <proxy name="ContentEnrichProxy">
            <!-- Would Enrich the Value Based On the Number -->
                  <switch source="//m1:symbol" xmlns:m0="http://services.samples" xmlns:m1="http://services.samples/xsd">
                <case regex="1">
                     <log level="full" />
                        <source type="inline" key="Location1"/>
                        <target xmlns:m1="http://services.samples/xsd" xpath="//m1:symbol/text()"/>
                 <case regex="2">
                        <source type="inline" key="Location2"/>
                        <target xmlns:m1="http://services.samples/xsd" xpath="//m1:symbol/text()"/>
                  <!--Will Send the Enriched Message -->
                       <address uri="http://localhost:9000/services/SimpleStockQuoteService" />
                <!--  <drop />    -->                   
                <send />
    <publishWSDL uri="file:samples/service-bus/resources/proxy/sample_proxy_1.wsdl"/>
    <localEntry key="Location1">IBM</localEntry>
    <localEntry key="Location2">WSO2</localEntry>    

Simulating the sample scenario

Send the following request to the ESB profile of WSO2 EI using a SOAP client like SoapUI

<soapenv:Envelope xmlns:soapenv="" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">

Note that the Axis2 server log displays that the request is processed.

How the implementation works

Let's investigate the elements of the configuration in detail. The line numbers below are mapped with the configuration shown above.

  • enrich [line 10 in config] - Mediator used for message enrichment. 
  • source [line 11 in config] - The location in which you can find the source configuration. In this example, it is a simple inline text string located in the local registry entry with key Location1
  • target  [line 12 in config] - The location where the source configuration should be applied. This is specified using an XPath expression. 
  • localEntry [lines 36 and 37 in config] - Entries from the local registry