Chandana Napagoda's Blog

With WSO2 Enterprise Integrator or Enterprise Service Bus servers, if you want to change the backend server response code, you can set custom status status code as below:  <property name="HTTP_SC" scope="axis2" type="STRING" value="403"/> If you are getting 'HTTP/1.1 202 Accepted' response from your backend, you need to set "SC_ACCEPTED" as false by setting a custom SC_ACCEPTED Ex:  Receiving 202 from backend and change it to 200 <filter regex="202" source="$axis2:HTTP_SC">         <then>             <property action="remove" name="HTTP_SC" scope="axis2"/>             <property name="SC_ACCEPTED" scope="axis2" value="false"/>             <property name="HTTP_SC" scope="axis2" type="STRING" value="200"/>         </then>         <else/>

Local Entry is one of the data storage points in the WSO2 Enterprise Service Bus, where you can store text strings, XML content, and File URLs.  I have been asked a question that, how can we read the content of the local entry if it as an XML file. Below is an example to read the content of the local entry(Name: NameOfLocalEntry) and assign the value of XML elements as properties.  Content of Local Entry: <?xml version="1.0"?> <Server> <userName>chandana</userName> <URL>blog.napagoda.com</URL> </Server> Synapse Configuration:  <property name="localEntry" expression="get-property('NameOfLocalEntry')" scope="default" type="OM"/> <property name="userName" expression="$ctx:localEntry//*[local-name()='userName']"/> <property name="URL" expression="$ctx:localEntry//*[local-name()='URL']&q

WSO2 ESB/EI PayloadFactory mediator can be used to replace the contents of a message. As an example, if the backend is accepting a different message structure than what you are receiving, you can use PayloadFactory mediator to change the message structure. Other than that, if you want to transform XML payload into JSON or JSON to XML with different message structure you can use this mediator. Recently, I faced an issue while transforming a message into JSON which is originally read from a CSV file(using Smooks Mediator ). This message can have empty values in the content sometimes and such messages look like below: <Users> <User> <FirstName>Chandana</FirstName> <MiddleName/> </Users> </User> I initially wrote a payload factory mediator like below: <payloadFactory media-type="json">         <format>    {   "UserInfo": {     "fName": "$1",     "mName": "$2&qu

WSO2 ESB's Iterate mediator plays a very powerful role in the Splitter Enterprise Integration Pattern. Splitter Enterprise Integration Pattern is used when messages contain multiple elements that might have to be processed in different ways. The Splitter breaks out the composite message into a series of individual messages, each containing data related to one item. WSO2 ESB Iterate mediator split the message based on a given expression and process them separately. So think about a use case like you are getting multiple order items and you want to enrich each order item, by calling another endpoint and finally we need to aggregate all the enriched items. There you can use the Iterate mediator and after that aggregate mediator to aggregate all the enriched items. Example: ESB Proxy Service: <?xml version="1.0" encoding="UTF-8"?> <proxy xmlns= "http://ws.apache.org/ns/synapse" name= "IteService" transpor