IBM Integration Bus Reviews

We use IBM Integration Bus with IBM DataPower for IT integration. It’s the most used and essential component. For data security and governance, we use it with HiSphere. It’s also integrated with Outlook for handling video files.

The Aspera feature for high-speed transfer is highly effective. For DataPower, we use it to export our servers and integrate with government sectors. It's also used internally to integrate isolated solutions and manage traffic overload.

IBM Integration Bus is a reliable solution that helps us handle performance challenges effectively. However, I believe there is room for improvement in the pricing structure to make it more accessible. As far as IBM Integration Bus is considered for other organizations, it has strong performance capabilities and integration features.

I have been using IBM Integration Bus for two years.

Integration Bus is quite stable, I would rate it at eight out of ten.

In terms of scalability, it's a solid ten. IBM's technical support is good, I'd rate it at an eight.    

The installation was manageable, although it required specific skills in the Open-Sec environment. It took us about two weeks to install and configure everything, depending on the environment complexity and the number of servers. Currently, around thirteen technical users are working with IBM Integration Bus in our organization.

Overall, I recommend IBM Integration Bus with a rating of nine out of ten.

I worked with Integration Bus for a UK-based insurance client and banking domain client. Our main use cases are for integrating different systems. We were involved in integrating their master data management domain.

The message queue connectors are the most valuable feature. They have built-in connectors for most of the systems, like SAP and Oracle Database.

The password settings need improvement. 

I have been using Integration Bus for five years. 

The solution is highly stable. 

The scalability is very high. 

The initial setup is straightforward. 

The pricing of the solution is high. 

Overall, I would rate the product a ten out of ten.

The solution is deployed on-premises.

The message queue feature is very valuable.

The product could be improved by including more resources on SQL and improving the simplicity of the resources available. Additionally, the price can be reduced.

We have been using this solution for approximately four years and are currently using the first version.

The solution is stable.

The solution is scalable, and there are currently many people using the solution in our organization. We have plans to increase the usage of the feature.

It is quite expensive and can be lowered.

I rate the solution an eight out of ten.

Our organization is a bank, so we use IBM Integration Bus for integration with core services and test applications.

IBM Integration Bus facilitates communication between parties and legacy systems. For example, the banking industry has a lot of legacy systems, so IBM Integration allows for communication between the legacy systems and new ones and allows us to develop solutions that can respond to the new ones.

We currently use version 10 of IBM Integration Bus. The most beneficial feature is the integration we have with legacy services. We can do the integration to expose other technology to stop, rest and manipulate the output of many legacy services.

We would like to separate the services into different containers, and we don't have this ability right now on IBM Integration Bus. We are currently doing this as an organization, and IBM is setting up the OpenShift.

The version of the technology and current knowledge is a bit outdated. There is also no DevOps, and the process of deploying that is the downside. Regarding additional features, we would like better integration with external solutions like Apache Kafka.

We have been using this solution for six years.

It is a stable solution. The downside is that sometimes it is easier to use another post, like a language outside of IBM Integration Bus, but overall it's a good solution.

It is not scalable.

We do not communicate much with IBM, only for initial setup and completing bootstrapping technology. However, we have IBM partners that work with us. I rate the technical support a four out of ten because they are sometimes a bit selective with the partners they pay attention to.

Our company has been using IBM technology from the beginning.

The initial setup is difficult to configure and set up the first time. I rate the setup a four out of ten.

I rate this solution a seven out of ten.

We use IBM Integration Bus for 600 applications that we're running.

The most valuable feature is the security.

Sometimes migration takes too long.

I have been using this solution for nine years.

It's a stable solution.

It's very scalable. When you deploy the solution, you have the option to create two different policies.

We haven't needed to use technical support very much. We reached out to IBM about a problem we had with HashMap.

I was the developer consultant.

I would rate this solution 9 out of 10.

IBM Integration Bus is mainly used to integrate banking systems.

IBM Integration Bus' most valuable features are its performance, fast and easy development, and easy support.

Some of the runtime properties need to be improved because if you want to load certificates as sales security, you have to restart the server. There are also some bugs with file transfer protocol.

I've been using IBM Integration Bus for three to four years.

IBM Integration Bus is very stable.

The initial setup was straightforward, and IBM has a great knowledge base to help. I would rate the setup experience as four out of five.

IBM Integration Bus is expensive.

I would give IBM Integration Bus a rating of nine out of ten.

A retail customer used it to connect with the backend Oracle retail system. There were some plugins that were available for that particular use case on top of the Integration Bus for message transformation, schemas, etc. It has also been widely used in banking.

It is mostly deployed on the hardware, but it is also available on the cloud.

It aligns well with containerized environments, which increases its scalability and high availability. 

Overall, it has good coverage of features.

Its licensing or subscription model should be improved for more flexible adoption. There should also be more ease of use.

I used this solution for five to six years in my previous company.

It is highly scalable. It is used in high-volume environments with thousands of users, such as retail banking. It is being used a lot for digital banking, and all the transactions are through the ESB layer. So, it is quite scalable and has good performance.

It has a moderate or medium-level complexity. The duration depends on the use case in terms of the number of services and workflows, but typically, doing installation and configuration is a matter of a few weeks.

It is not cheap. It has its cost. It is one of the high-cost solutions.

I would rate it an eight out of 10.

We use IBM Integration Bus as a bank middleware solution. 

The solution does omnichannel integration with the core banking and other systems, including core banking, ETC, and click systems. It does so for a host of systems. 

The solution addresses all of our middleware needs in respect of transformation, parsing, security and stability; everything really. 

IBM Integration Bus could have better REST API, which could be more powerful,  and this accounts for why we are looking for alternative solutions concerning this and open banking. 

The initial setup was complex. 

Technical support is below what I would consider to be very good. It's good, but not too much or very much so.

The solution is complex and there is a need for more resources and greatly improved quality. 

The solution addresses our stability needs. 

Thus far, we have been making maximum use of the solution. 

Technical support is below what I would consider to be very good. It's good, but not too much or very much so.

We previously used a local solution and replaced this with a new enterprise solution. 

The initial setup was complex. 

Including preparation time, addressing the environment and building the POC, deployment took around one month. We are talking about active, on-premises deployment. 

There are nearly five people required for deployment and maintenance. 

Management would be in a position to address whether we have seen a return on our investment. This said, we have witnessed some returns on our business so far. 

I prefer not to address the licensing costs, or any other for that matter, as this is confidential. 

We did evaluate other products before going with IBM Integration Bus. 

We are customers of the vendor.

From a development perspective, there are nearly 40 people using this solution in our organization, although we have thousands of customers who do so indirectly. 

The solution probably covers more than 95 percent of the integration requirements. 

I rate IBM Integration Bus as a seven out of ten. 

My primary use case of IBM Integration Bus is for designing and developing solutions. We use App Connect Enterprise as a micro ESB and, in cases where we need rapid development, as a microservices platform as well. I'm currently dealing with an on-premises version, but it's deployed on an internal cloud. 

One of the most valuable features is how seamless and easy to use this solution is. This is a fantastic solution and a very measured product. 

There are a couple of things I want improved, but I think they have already touched upon all those things in the most recent version. I'm not using the most recent version—I use a version older than the most recent—but I'm sure that if I looked into and explored it, I would see more support on the CI/CD and more support for unit testing automation. I've read that they released all these things in the new version of App Connect. Once I explore the new version of this tool, I'll probably have a better idea of suggested improvements. 

I have been working in IBM for almost 17 years now. 

This solution is stable. It's a fantastic solution and a very measured product. We only need one person to maintain the DevOps pipeline, but we do have a team of 10 developers to deliver the work.

IBM's technical support is fantastic. Their support process is very good. 

This solution is cloud-based. We are using it in a container image, so the one time CI/CD setup is there, in the pipeline setup, and after that the process is very seamless. We just check in our code, and then the pipeline creates an image of it and deploys it onto our private cloud platform. So it's very seamless and there's no hassle involved. 

Initially, we needed about three people for deployment: one for administrative activities, one with DevOps knowledge, and one developer. 

We implemented through an in-house team. I work as an architect, but we have a DevOps team that takes care of maintaining the pipelines and as-needed administration activities. 

I generally do not get involved in the licensing or pricing because I'm a hardcore technical guy, but I'm aware of the fact that IBM is highly expensive, so not everybody can afford it. All the products are licensed. 

I have heard of MuleSoft, a platform that provides a solution for API management, ESB, everything. When it comes to ESB, they have a package or facility feature for unit testing as well, called MUnit or something. From an ESB development point of view, this is the complete package. I was lacking these features in App Connect, but I heard that the latest version includes things like unit testing, automation features, all those things. I also heard that they added AI—I'm not sure where, but IBM is pretty big on that, as well as on adding more and more features in that area. 

I rate this solution a nine out of ten. This is a very measured tool and IBM has been doing a splendid job with this particular platform. Earlier, it was only possible to have an on-premises installation, but now that it's compatible with the cloud, it's a very seamless and fantastic tool. Especially with the current release, I really like this product. 

In terms of advice I would give to those considering implementation, I would say that there could be a problem with integration. Nothing to do with the tools, but from a resourcing point of view. I've seen that a lot of people with Java expertise can face problems when being introduced to this technology without proper training. When a Java developer gets into this particular technology and starts developing stuff, they may be unaware of certain best practices, certain standards, certain conventions that should be used. In my team, when we hire new resources, Java is an advantage for us and a person with Java knowledge is highly welcome, but when we look at their knowledge in the technology itself, there may be issues. This platform is complex and only a person with the right knowledge will be able to deliver. So my suggestion to those who are considering implementation: while resourcing, ensure that you've got the right knowledge on the architect side as well as the developer side. 

We are a software development company and we use IBM Integration Bus for integrating different internal systems for the customer side and to integrate the internal systems with external systems for different kinds of flows.

There are three elements that make IBM Integration Bus very important for our organization's payroll systems which are the solution's high scalability, performance, and reliability.

The current version of IBM Integration Bus, now called App Connect Enterprise, provides operators for deployment in the OpenShift cluster, which makes deployment much easier and significantly increases the scalability and reliability of the integration solutions.

I have been using IBM Integration Bus for approximately two years.

IBM Integration Bus is very reliable and stable. If the right configuration is done, in operation everything is runs very well. If you have not configured everything well then you most likely will have some stability or performance issues.

IBM Integration Bus is scalable. If you are using OpenShift then the solution's scalability becomes even better.

We have approximately 12 people who have the experience to use this solution.

I would rate the support from IBM Integration Bus a seven out of ten. They are very helpful but sometimes it takes too long for them to respond.

The implementation of the solution at the beginning phase can be complicated. The time it takes for the implementation depends on the environment a lot of other factors.

The development toolkit that is provided is very good. It helps to configure all the message flows and data transformation. They also provide Extended SQL language (ESQL) for different types of data transformation.

The solution does not require much maintenance.

IBM provides a quite complicated licensing model.

We have evaluated other solutions and we have found that IBM solutions to be highly stable and scalable.

I would recommend this solution to others.

I rate IBM Integration Bus an eight out of ten.