2019-09-25T05:10:00Z

What is your primary use case for IBM WebSphere Message Broker?


How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

Guest
55 Answers

author avatar
Top 10Real User

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.

2020-10-08T07:25:22Z
author avatar
Top 10Real User

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.

2020-10-04T06:40:25Z
author avatar
Top 5Real User

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

2020-08-09T07:19:47Z
author avatar
Real User

We are a 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. Some may use HTML whereas others might use JavaScript, for example.

2020-05-04T05:12:30Z
author avatar
Consultant

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.

2019-09-25T05:10:00Z
Find out what your peers are saying about IBM, MuleSoft, Software AG and others in ESB. Updated: June 2021.
509,570 professionals have used our research since 2012.