I'm using this tool for my application. We configure it according to my application. For any new applications that are being onboarded, we engage this tool so that they interconnect and the datas are flowing as required.

For the last engagement, I had the latest version. I keep updating them for the bank standards, which should be the current version minus two. We look at the IBM website and use the versions for our application. We update frequently.

For my previous engagement, the initial project, it was almost 40-plus people who were using this application. For the current engagement, more than eight people are using it.

We use IBM WebSphere Message Broker as an Enterprise Service Bus, integrating with different applications.

We primarily use the solution as an integration platform to integrate disparate systems at the bank.

IBM WebSphere Message Broker can be used for routing, data transformation, and enrichment. It can be used for routing and data.

We have a large number of use cases for this product. It is built into the underlying infrastructure for most of our applications.

We had different use cases such as point-to-point, and public subscribers. We have some APIs building business Message Broker and we have divisions such as the legacy mainframe. 

We pretty much use everything. Most of the integration is done with Message Broker.

We integrate messaging from the core banking systems to other systems via MQ.

We use this solution to assist our customers with their core business challenges. The main purpose of this tool is to connect several applications together. My experience is based on two medium-sized projects that I have completed using this solution.

We have an on-premises deployment, as do many SMB in the Middle East.

My primary use case of this solution is as an application server as well as everything else related to the whole suite from IBM.

We are system integrator and solution provider and this is one of the products that we implement for our clients.

It comes with a development tool and we use it to develop integration flows. I am normally working with financial companies when using this solution. They use it for communication between heterogeneous applications at the backend. 

I'm part of the company middleware, and we are managing things with Spheres, IHS, and also HU and EAZ. I've just become involved in trying to sort out a roadmap to migrate the EAZ from IAB to ACS Enterprise App Connect, that's the latest IBM technology. I'm a solution designer and we are partners of IBM.