IBM Integration Bus Reviews

We use the solution for data integration. We have different kinds of information such as file feeds, messages, and inbound software that need to be confirmed and delivered to the platform of our clients as a message.

We have benefited by using this solution from the IAB, we have been able to use different delivery types.

I have found the inbound and outbound adapter confirmations valuable.

The tracing and debugging features are not up to date with more modern technology available.

I have been using the solution for 15 years.

The solution has been stable.

The scalability has been excellent.

The initial setup is straightforward.

We did the implementation through our in-house team and it took approximately one day to complete.

The price of the license could be cheaper.

I rate IBM Integration Bus a seven out of ten.

We are a financial institution and we are using this solution for the APIs that we provide.

The biggest advantage of this solution is that it is very easy to learn, and very easy to build applications. The learning curve is not steep and it is something that you can pick up within about two weeks.

There are a lot of inbuilt interfaces like ISO and SAP. Having all of these interfaces already built makes integration very easy and straightforward.

One drawback that I have found is that there are issues with using the Java connector. I was running out of heap space.

I have been working with IBM Integration Bus for three years.

The stability is fantastic.

With respect to scalability, IBM Integration Bus is very good.

I have been in contact with technical support and I found that they were very good.

I have not really used any other ESB solutions.

I was not part of the original deployment.

I like to view comparisons to see what people have to say about similar products because I have just recently changed jobs and my new company is trying to purchase an ESB. Although I fully recommend IBM Integration Bus, I think it is important to look and see if other solutions may be better.

Generally speaking, this is a very good product. It is easy to learn and use, and it is robust as well.

I would rate this solution a nine out of ten

IBM Integration Bus integrates various systems by receiving, transforming, and routing messages in different formats, such as XML or JSON. It supports integration between different applications and services within the organization, enabling effective communication.

The solution has enhanced data processing capabilities by allowing efficient data integration and transformation. It has improved operational efficiency by handling various protocols and integrating different services.

The most valuable features are its support for various protocols (like HTTP) and its integration capabilities, which facilitate communication between different systems and services within the organization.

They could integrate AI technologies with the product. Additionally, ongoing developments and enhancements in integration technologies could be beneficial.

I have been using IBM Integration Bus for 11 years.

The product is stable. 

The solution is scalable with OpenShift, allowing adjustments based on customer requirements.

The initial setup was straightforward, taking approximately 15 to 30 minutes to complete.

Overall, I rate IBM Integration Bus an eight out of ten. 

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.

Our primary use case is a content-based tool for system messaging. IIB comes with IBM MQ as its messaging backbone. With respect to our requirements, IIB fits well, and it does its job.

It has improved our company a lot. We have added a lot of adapters. The microservice has provided an advantage for us, so we have a lot of adapters with REST Node.js, which have been added.

IBM used to provide multiple adapters. For example, we also have an adaptor for MQTT (Message Queuing Telemetry Transport). 

With respect to our enterprise and SOA compliance (this product fits within the SOA compliance category), we want to talk about microsolution architecture, as enterprises generally enable SOA first before going to microsolutions. It will have to have a long-term approach on the SOA category, as IIB fits with a lot of other IBM products, like the WSRR, IBM DataPower, and MQ. It has a lot of advantages when we are using it or enforcing SOA as an architecture for our enterprises.

IBM does not support orchestration, which is how they designed it, and other BPM tools in the market support orchestration. IIB wasn't designed for short and small transitions which are preferred to be stateless. If they merged the BPM capability into this product, then it would be a better solution.

It is one of the most stable products which I have seen in the market. 

It scalability is seamless. There should not be any issues as long as we integrate fully with our use cases and restrict scenarios that we have tested on different operating systems. We have tested for the high availability and OTS availability. It has worked well so far.

Under certain situations, when what we were expecting is not right, then we contact support, and technical support from IBM is really good. However, IBM support is mostly for the small time stuff, like product releases. In a few years, they will end up the support unless we pay them. The difference is in the cost. Support costs are high compared to their competition. Otherwise, the support is good.

The initial setup was straightforward.

We also evaluated Oracle.

I would rate this solution a nine out of 10, because of: 

1. The community. 
2. They provide freeware.
3. The support that IBM provides. 
4. It fits its purpose.
   

IIB is one of the top-rated solution in this category. If looking for a tool which is SOA compliance, you can blindly go for this particular tool. 

The most important criteria when selecting a vendor is support. We are looking for the 24/7 support in respect to that particular product. It should be compliant within our business requirements. Technology is evolving day-by-day and should have an additional features added-on as long as we are required to implement those features, e.g. product security. We are using different encrypted algorithms on encryption screens, and these functionalities are widely adopted by IBM.

In general, we are using IBM Integration Bus for integration purposes only because we have multiple applications to integrate.

I have found IBM Integration Bus is very useful because it can integrate multiple backend applications.

The solution could improve by having built-in implementation and secure monitoring without the need for API Connect.

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

We have not had any issue with the stability of the solution. However, there are times when we have policies in place and after the installation, the data wizard does not work.

The technical from IBM has been very good.

The installation was straightforward.

IBM Integration Bus itself is prices fair but App-Connect is a bit expensive which we use in conjunction with it.

I have evaluated MuleSoft.

I would recommend this solution to developers.

I rate IBM Integration Bus a seven out of ten.

We are working on MQ, soap and rest based services. Some clients are accessing our services and vice versa.

Yes IIB help us to shape up our organization in service oriented architecture. Usability has increased and integration has become easier.

Multiple protocols support,  development environment is user friendly.

Documentation is not easy to understand.

There should be inclusion of more and more adapters that make this product more usable.

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

IBM Integration Bus is a stable solution. As far as the technical side is concerned, we don't have an issue. 

IBM Integration Bus is easy to scale.

IBM technical support is fine, and we have a good relationship with them.

The installation is very simple. I've been working with the Oracle platform as well, and the Oracle platform installation is quite difficult compared to IBM Integration Bus.

We are working in the bank, and we implement everything internally ourselves. We are maintaining it, and we don't have to do too much. We have a separate team for maintenance. We have administrators as well on the operations side. They are looking after it.

When I compare it to other products that are available in the marketplace, I rate it better than others because it's easy to develop things, and it's easy to handle. I also use Oracle, and I prefer IBM Integration Bus to Oracle.

On a scale from one to ten, I would give IBM Integration Bus an eight.

I'm responsible for Strategy and Architecture for an IT consulting company they are partners with IBM. 

I like that this solution is suitable for any size company. It's simple to use from a development perspective because the content is easily infiltrated in the eclipse infrastructure. It's also credible in all the application aspects and easy to integrate into the enterprise application landscape. Finally, there is also a good relationship with IBM itself that assists us in implementing. You can really use this architecture but you have to understand the technology itself. It means you can do everything with this technology on condition that implementation is carried out correctly but this is a general term and valid for all solutions on the market. IBM is offering with the Integration Bus a very robust and stable solution.

The solution itself is quite expensive for smaller companies because of a complex architecture setup if you just start. Easier and a more plug and playable solution which make an MVP easier in being able to show the value faster to the customer.

I've been using this solution for about 10 years in different projects and for different customers.

This is a very stable solution.

Scalability depends on the money that you have in your pockets. Technologically speaking, it's a scalable solution. 

I get good support from the IBM technical people. It also depends on your philosophy, how you implement this. I have a lot of very experienced people, but also a good relationship with the laboratories, which is also sometimes necessary when you're doing something new and a highly sophisticated implementation is required. You need to have a support team for the product development. 

The initial setup is straightforward, it's a simple solution. 

Evaluate and define a clear architecture, and set up a governance framework that includes a competence center that will take care of the usage, the licenses which will be needed, and do guarantee the reuse of interfaces and components.

I always suggest carrying out a proof of concept each time. People who are able to set this up and also monitor it, will discover how easy it is to customize and to integrate the architecture. The POC creates familiarity and also an understanding of the skill set required. 

I would rate this solution an eight out of 10.