Are we there yet? - 4 ESB implementation tips

Posted by Ruben van der Zwan on 27 Jun, 2017

You buy an ESB because you need one. You implement it because otherwise it doesn’t work. But this doesn’t mean you and your integration tool will live happily ever after. During the implementation period, there are still many things that can weaken the powers of the ESB that you so carefully selected. This stage is exciting too, though, as you get to finetune all the ESB elements and adapt them to your specific needs. In this article, we get you on your way with four ESB implementation tips.

Read More

Topics: WSO2, WSO2 ESB, ESB

WSO2 and Ansible, how to setup an automated installation?

Posted by Thomas Zielinski on 8 Jun, 2017

Usually the installation of a WSO2 product is simple. Just unzip the package and that's all. This is, of course, in theory. Usually it is needed to customize the product. In the production environment, we have to use RDBMS database, what causes the changes in product configuration. If customers want to use the WSO2 product as distributed or clustered setup, the changes in configuration are needed too. Mostly, the customization is made once. In this case, it can be nice to have a tool which install the customized product on the servers. This blog is about WSO2 and Ansible and how you can setup an automated installation.

Read More

Topics: WSO2, Ansible

Vagrant and WSO2, making it work - WSO2Tutorial

Posted by Rob Blaauboer on 18 May, 2017

In a previous Vagrant and WSO2 blog we created a simple and rather quick and dirty setup to show you how easy it is to spawn a WSO2 ESB running CentOS using Vagrant scripting.

The drawback  is however that our setup starts from scratch everytime we do a ‘vagrant up’. Since we always need Java and a number of other tools when running WSO2 products, it makes sense to create our own ‘box’ (vagrant’s term for an operating system that it uses).

Read More


WSO2TORIAL: WSO2 ports of call

Posted by Rob Blaauboer on 27 Apr, 2017

When you deploy any of the WSO2 products on your local machine you really do not have to think about enabling ports for communication (WSO2 ports of call). However, when you move to more of a real world setup this changes.

The reason, of course, is that servers that are connected to the internet or even internal networks often have restrictions as to the traffic and ports. In other words, you might be able to install the software but with port restrictions the software does not work.

Read More

Topics: WSO2, WSO2 ESB, API

Looking at your WSO2 logs using rtail / NodeJS

Posted by Rob Blaauboer on 20 Apr, 2017

In some cases you will run a WSO2 product on a machine somewhere in the cloud or on a server somewhere in the organization. Our use case is porting our training environment to a Amazon AWS environment running on a minimal install of CENTOS.

Read More

Topics: WSO2