\
“Design and develop an integration..” The words seems so heavy ? But I’m going to show you the best way to get it done easier, from my experience! There is [WSO2 Integration Studio](https://wso2.com/integration/integration-studio/), a World Class Integration solution which is available as Open Source!

\
WSO2 Integration Studio is a development environment for designing, developing, debugging, and testing integration solutions. It has a graphical editor which facilitates with drag and drop design for integrations, and a source editor in addition for that. When you create REST APIs you can use the Swagger editor to make use of Swagger definitions. Also this has a Micro Integrator embedded in it, so that the developers can deploy and test the integrations as well.

\
Let’s see how to design and develop the integration of an Online Shopping Store using WSO2 Integration studio!

\
‘ShopMe’ is a large Online Food Store which sells the products from three manufacturers (‘BakeMe’ , ‘FoodX’ and ‘EatMore’) and allow the customers to compare the products regarding the product prices, reviews and buy the best product that suits for them.

 ![System in High Level— Image by Rusiri Illesinghe](https://miro.medium.com/max/1400/1\*iGOIKF3wJ8PoFy2ivaJL0A.png)

\
The manufacturers ‘BakeMe’ , ‘FoodX’ and ‘EatMore’ are exposing their own APIs to access the product related information. But the user has to put an extra effort to visit each website, compare the product prices, see the reviews and select the best product for them. So, the ‘ShopMe’ online store needs to create a single API, integrating all APIs of the product manufacturers.

# Step 1

Download and install the WSO2 Integration Studio. You can refer the following URLs for this process.

\
<https://wso2.com/integration/integration-studio/>

<https://apim.docs.wso2.com/en/latest/integrate/develop/installing-wso2-integration-studio/>

\
# Step 2 :

Now let’s create the integration!

a) First, open the WSO2 Integration Studio and click on “New Integration Project\*\*”\*\* as in the image shown below.

\
 ![](https://miro.medium.com/max/1400/1\*uy0I4LZmp6rV23-Pv15PgQ.png)

b) Let’s create our Integration project with the name ‘ShopMe’

 ![](https://miro.medium.com/max/1400/1\*ekuwEJgPxbV0HwJ9jtf6Gw.png)

c) Make sure it has checked the ‘Create ESB Configs’ and ‘Create Composite Exporter’ check boxes as above. Then click ‘Finish’ button.

Now our project should be visible in the Project Explorer as follows :

 ![](https://miro.medium.com/max/450/1\*z-fVSc9M8uvz40D29Z7B1A.png)

# Step 3:

Next we’ll create the endpoints.

Endpoints are corresponding to the services provided by ‘ShopMe’. Since ‘ShopMe’ is unifying the services provided by three food stores, we have to create three endpoint artifacts. Let’s create them!

a) Right click the ‘ShopMeConfigs’ and select New →Endpoint

 ![](https://miro.medium.com/max/1400/1\*Xodb6Z7qTITfKRuyGrK1hg.png)

b) In the following popup window, click ‘Next’.

 ![](https://miro.medium.com/max/1048/1\*LXfFoCJUpXW8KWpaaJM-Lw.png)

c) We’ll create the endpoint for ‘BakeMe’.

\
For URI We select the endpoint as a ‘Static Endpoint’ to save it in the current workspace. You can change the URI template in accordance with the manufacturer APIs you use.

Provide the following endpoint information and click ‘Finish’.

 ![](https://miro.medium.com/max/1032/1\*EC7B-ka26SHvqC9Xm-NrFg.png)

d) Create the endpoints for ‘FoodX’ and ‘EatMore’ as well, following the above steps a, b and c repeatedly.

\
You can use the following endpoint information when creating the endpoints :

\
> Endpoint Name : FoodXEndpoint
>
> Endpoint Type : HTTP
>
> Endpoint URI Template : http://localhost:9091/foodX/products/{uri.var.productType}
>
> Method : GET
>
> \
> Endpoint Name : EatMoreEndpoint
>
> Endpoint Type : HTTP
>
> Endpoint URI Template : http://localhost:9092/eatMore/products/{uri.var.productType}
>
> Method : GET

# Step 4:

Now let’s create the REST API for our ‘ShopMe’ platform! Our intention is to orchestrate the above three services and expose them as a single API to the userbase.

\
a) Right click on ‘ShopMeConfigs’ and select New →REST API as follows :

 ![](https://miro.medium.com/max/1400/1\*x4Iwoyh2xB-6EhcRT6P0EA.png)

b) Select ‘Create A New API Artifact’ in the appearing window and click ‘Next’.

\
c) Let’s give the API name as ‘ShopMeAPI’ and context as ‘shopme’ and click on the ‘Finish’ button.

 ![](https://miro.medium.com/max/1090/1\*7o1q-r7TCSicpLvvDWbK2Q.png)

# Step 5:

Let’s design the integration!

\
a) Open the ‘ShopMeAPI’ in Design view as follows :

 ![](https://miro.medium.com/max/1400/1\*AlzCQaPfWRl582tpIi6rCA.png)b) Let’s set the properties for ‘API Resource’. When you double click it in the design view, you may see the properties window in the screen. There you have to set the following values.

\
> *Url Style: URL_TEMPLATE*
>
> *Uri Template : /products/{productType}*
>
> *Methods : GET*

\
 ![](https://miro.medium.com/max/1400/1\*iEaeHWG2jWghKiv3sGe36Q.png)

In the right side palette you can find different types of mediators, which you can drag and drop into the design canvas.

\
For your knowledge about the Mediators, I’m quoting the following from WSO2 official documentation,

## "Mediators are individual processing units that perform a specific function on messages that pass through the Micro Integrator.”

Our requirement is to add the endpoint artifacts of ‘BakeMe’ , ‘FoodX’ and ‘EatMore’ into this integration sequence, in our design.

\
c) When our ‘ShopMeAPI’ receiving a GET request, it should call the endpoints of thee above three services. That means, when the ShopMe API receives a message, it should create three clones. For this we use the ‘Clone Mediator’. Drag and drop it into the design as follows :

 ![](https://miro.medium.com/max/1400/1\*ioIIt0c047ILMkQrnR99Sw.png)

By default we can see that, clone mediator has one branch, since it should be three branches in our case, right click on the call mediator and select ‘Add/Remove Target..’. Set the number of branches as 3 there and click ok.

 ![](https://miro.medium.com/max/450/1\*h0rnblEqYEXMNnzFDl_NuA.png)

Now you may see that the design also has been updated with three branches.

\
c) For sending a message to an endpoint outside of the Micro integrator we can use ‘Call Mediator’.

\
So let’s drag and drop the call mediator into the design like this:

 ![](https://miro.medium.com/max/1400/1\*ecrkRu5B_VAxNbeWvNW4fQ.png)

d) To which endpoint the message should go ? Yeah we are going to define that in our design!

Under the ‘Defined Endpoints’ on the right hand side pane of the window, you may see the three endpoints that you created previously. We’ll frag and drop the corresponding endpoint for each call mediator.

 ![](https://miro.medium.com/max/1400/1\*76JieZ_xx2jVk_jx-myKlw.png)

e) So far, we prepared our design as to clone the message and deliver to three different services. With that, we may receive three different responses from those three messages sent to three services. We know that the purpose of ShopMe API is to provide a single interface for all those 3 services.

\
For example when a user is interacting with ShopMe to get all the ‘Cake’ products, the ShopMeAPI will receive the corresponding API call (a message). Since it needs to get the cake products of ‘BakeMe’, ‘FoodX’ and ‘EatMore’, the particular message is cloned and sent to those three endpoints and those services will respond back to the ShopMeAPI individually. With that, ShopMe API will receive three responses (messages) and it should aggregate them and expose as a single response.

\
For this we can use the ‘Aggregate Mediator’. So let’s drag and drop it to our design, next to the call mediators.

 ![](https://miro.medium.com/max/1400/1\*A7wpZ7Xk9BI9V6Q8BR7NPw.png)

Double click on the aggregate mediator and set the following expression for ‘Aggregation Expression’ : json-eval($.products.product)

\
f) Now we need to send the aggregated response back to the client. For that, we use a Respond mediator, next to the Aggregate mediator.

\
This is the complete design for our integration.

 ![](https://miro.medium.com/max/1400/1\*NbfI3yd2LKL9_3H_CCL2RA.png)

Cool! We could comfortably prepare our integration design with several drag and drop rounds with this smart tool!

\
Let’s build and run the created artifacts!

# Step 6:

This step have two main alternatives!


1. [WSO2 Micro Integrator](https://wso2.com/integration/micro-integrator/) is another wonderful open source solution from WSO2, to deploy and run the integration artifacts. You can use it externally and deploy the integration. Will write on it soon!
2. You may remember that I initially mentioned that WSO2 Integration Studio has it’s own Micro Integrator embedded. Hence you can deploy and run the integration using the Integration Studio itself!

In this article, let’s go ahead with the second option I mentioned above.

\
First we have to build the artifacts. For that, right click on the ‘ShopMeCompositeExporter’ and select ‘Export Project Artifacts and Run’.

\
Select all the artifacts of ‘ShopMeConfigs’ and click on ‘Finish’.

 ![](https://miro.medium.com/max/1400/1\*bPC1WTmM624v10AYz1hXDw.png)

You may see the console results appearing as follows,

 ![](https://miro.medium.com/max/1264/1\*iibCnZnBzVH0wFIVj8_V8g.png)

Voila! Your ‘ShopMe’ API is up and running. You can open the Monitoring dashboard and see the information about the deployed artifacts. Now you can access the products of all the three Manufacturers via the ShopMeAPI you created!

\
See you again with more exciting stuff on Integration Solutions!

\
Happy Integration!


---

Related Links :

<https://wso2.com/integration/integration-studio/>

<https://wso2.com/integration/micro-integrator/>

<https://apim.docs.wso2.com/en/latest/integrate/integration-overview/>

\
***Also published [here](https://medium.com/@rusirij/design-and-develop-the-integration-for-your-online-shopping-store-894ec6d2c78e).***

\


Target

2022 - Android Advocate of the Year

2022 - HackerNoon Contributor of the Year - Backend

2022 - HackerNoon Contributor of the Year - Machine Learning

2022 - HackerNoon Contributor of the Year - Rest Api

2022 - Most Authentic Developer Advocate of the Year

Nominated for 2022 - Android Advocate of the Year

Nominated for 2022 - HackerNoon Contributor of the Year - Machine Learning

Nominated for 2022 - HackerNoon Contributor of the Year - Rest Api

Nominated for 2022 - HackerNoon Contributor of the Year - Backend

Nominated for 2022 - Most Authentic Developer Advocate of the Year

Too Long; Didn't Read

Cassandra Forward a free Cassandra-focused community event

Designing and Developing the Integration of Your Online Shopping Store

Designing and Developing the Integration of Your Online Shopping Store

Too Long; Didn't Read

People Mentioned

Company Mentioned

@rusirij

RELATED STORIES