Skip to main content

Enterprise integration with WSO2 ESB + WSO2 MB and WSO2 DSS in a production environment with guaranteed delivery


Requirement
Customer has a SAP system from which he wants to send IDOCs to their respective endpoints and at the end of the day endpoints will send reports to the SAP system back. Here is the architecture of the deployment which customer is going to deploy in his production environment.
architecture
Basically customer want to send the information in the SAP system to the BE databases in a reliable and efficient manner without interacting in between.
Solution
In this solution we have used the following resources to achieve the requirement.
02 WSO2 Enterprise Service Bus
01 WSO2 Data Services Server
01 WSO2 Message Broker
Functionality
ESB01 – This ESB receives the IDOC message from the SAP server and save those documents in the WSO2 MB using message queues. Here we handle the high load of messages by saving them to the Cassandra data base  which is installed in a separate server. This will ensure that the high load of incoming messages are saved in the message queues without loosing any of the message.
ESB02 – This ESB consumes the saved messages from the message queues and apply the required transformation like changes and save the messages in a different set of queues. This will guarantee that the server is performing the transformations without bothering about receiving and saving the messages in the queues.
Message Broker – This will save the messages when they are receiving as a high load and guarantee that every message is successfully saved within the Cassandra database.
Data Services Server – This will push the messages from the message queues and load them back to the databases in the BE servers of the user. This will ensure that the every message saved in the message queues are automatically picked up by the data service and load them back to the databases in the BE.
Advantages
This setup will ensure that the messages are delivered without loosing any data in any kind of high load scenario (Guaranteed Delivery)
Isolation of the operation to different servers make it easy to maintain different parts of the operation.

Labels:

Comments

  1. 常樸July 24, 2013 at 1:04 AM

    Have the detail setting and scripts?

    ReplyDelete
  2. chanakaudayaSeptember 14, 2013 at 8:48 PM

    You can find the settings and scripts from here http://soatutorials.blogspot.com/2013/09/building-in-order-reliable-messaging.html

    ReplyDelete

Post a Comment

Popular posts from this blog

How to setup an WSO2 API manager distributed setup with a clustered gateway with WSO2 ELB

In this blog post I am going to describe about how to configure a WSO2 API Manager in a distributed setup with a clustered gateway with WSO2 ELB and the WSO2 G-REG for a distributed deployment in your production environment. Before continuing with this post, you need to download the above mentioned products from the WSO2 website. WSO2 APIM - http://wso2.com/products/api-manager/ WSO2 ELB - http://wso2.com/products/elastic-load-balancer/ Understanding the API Manager architecture API Manager uses the following four main components: Publisher Creates and publishes APIs Store Provides a user interface to search, select, and subscribe to APIs Key Manager Used for authentication, security, and key-related operations Gateway Responsible for securing, protecting, managing, and scaling API calls Here is the deployment diagram that we are going to configure. In this setup, you have 5 APIM nodes with 2 gateway...
2 comments
Read more

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr...
5 comments
Read more

Performance Tuning WSO2 ESB with a practical example

WSO2 ESB is arguably the highest performing open source ESB available in the industry. With the default settings, it will provide a really good performance OOTB. You can find the official performance tuning guide in the below link. https://docs.wso2.com/display/ESB481/Performance+Tuning Above document includes lot of parameters and how to change them for best performance. Even though it provides some recommended values for the performance tuning, that is not straightforward. The values you put in the configuration files will highly reliant on your use case. Idea of this blog post is to provide a practical example of tuning these parameters with a sample use case. For the performance testing, I am using a simple proxy service which iterate through set of xml elements and send request to a sample server and aggregate the responses back to the client. <?xml version="1.0" encoding="UTF-8"?> <proxy xmlns="http://ws.apache.org/ns/synapse"     ...
3 comments
Read more