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

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
4 comments
Read more

How puppet works in your IT infrstructure

What is Puppet? Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to orchestration and reporting. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud. How the puppet works? It works like this..Puppet agent is a daemon that runs on all the client servers(the servers where you require some configuration, or the servers which are going to be managed using puppet.) All the clients which are to be managed will have puppet agent installed on them, and are called nodes in puppet. Puppet Master: This machine contains all the configuration for different hosts. Puppet master will run as a daemon on this master server. Puppet Agent: This is the daemon that will run on all the servers, which are to be managed using p
7 comments
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte
3 comments
Read more