Skip to main content

How to build a CI/CD pipeline for WSO2 ESB (WSO2 EI)

Continuous Integration and Continuous Deployment (CI/CD) has become a core requirement within the enterprise IT ecosystem. It does not matter what type of software you develop (e.g. back-end services, UI/UX, APIs, middleware), you should be able to automate your development, test and deployment process. WSO2 ESB is one of the popular open source integration solutions available for implementing middleware services. The below mentioned medium post discusses how to implement a CI/CD pipeline with WSO2 ESB.



Labels:

Comments

  1. rmouniakOctober 3, 2018 at 10:56 PM

    I like your blog, I read this blog please update more content on hacking, further check it once at AWS Online Training

    ReplyDelete
  2. moshrabbi121November 4, 2018 at 11:20 AM

    The subsequent time I learn a weblog, I hope that it doesnt disappoint me as much as this one. I mean, I know it was my choice to learn, however I really thought youd have one thing interesting to say. All I hear is a bunch of whining about one thing that you may fix should you werent too busy looking for attention. casino play

    ReplyDelete
  3. Augurs Technologies Pvt Ltd.November 30, 2018 at 3:50 AM

    Award Winning Mobile App Development Agency. Have a Great Mobile App Idea? Let's build it together.

    ReplyDelete
  4. Top Software CompaniesDecember 12, 2023 at 5:10 AM

    Thank you for this information and Read our blog post to learn about the CI/CD pipeline.

    ReplyDelete
  5. venkatakrishnaJune 16, 2024 at 9:39 PM

    Wonderful Article. Thanks for sharing this post

    Site Reliability Engineering Training
    SRE Training in Hyderabad
    Site Reliability Engineering Training in Hyderabad
    Site Reliability Engineering Online Training
    Site Reliability Engineering Training Institute in Hyderabad
    SRE Training Course in Hyderabad
    SRE Online Training in Hyderabad

    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