IBM Integration Bus Reviews

Although my organization is not a bank, it does have communication needs throughout its different departments. 

While maintenance and support of the solution, like that of Dell Boomi, are very expensive, in the long run, though, say... six months to a year, it will be worthwhile for running one's business. The expense stems from the communication needs which necessitate the support of many preferences.

An issue which should be addressed concerns the difficulty of the product connecting to SAP.  In contrast, Mule has developed many connectors so that it can interact with multiple points. This allows us to write our own Java programming for, say, better database connectivity.

As the databases have different versions, we have different connectors for opening them. 

With Mule Force, we will write our own connector.  

While we do have different types of storage capacity, including that of hardware, RAM and transactions per minute, this is an area that should be addressed. There needs to be more storage capacity for logins and database file storage. Transactions per minute is a point that will need to be hammered out by senior management in its SLA. 

When it comes to the technical support of IBM Integration Bus, we are talking about a good product. As with Oracle and Microsoft, the problem with IBM revolves around maintenance, as well as integration. Owing to the expense, there will be insufficient resources. 

The initial setup of IBM Integration Bus was not complex. 

The product is usually very easy to deploy.

The product was only integrated with IBM servers. 

As mentioned, the maintenance and support are very expensive. 

Every bank has data available in the mainframe and there is a need to connect to this and extract it, which is where ELT loads come in.

While I would not say that IBM Integration Bus is not a good product, I would point out that it is limited to its own infrastructure. IBM Integration Bus lacks connectors for connecting with other technologies, even though it is not limited to its one cloud. These must be developed from other technologies, such as Azure. If I wish to interact with Azure in the cloud then I must develop a connector to do so. Moreover, IBM is large and we need to have smaller solutions. 

I would rate it a four out of ten. 

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 system integrator and this is one of the products that we propose for our clients.

Some of our clients for this product are banks.

IBM Integration Bus is flexible, easy to use, and easy to configure.

I would like to be able to build an Integration Bus cluster that is active-active.

This is a scalable product.

We have five or six customers who are using it.

I have seen no problems with respect to technical support.

We have experienced no trouble installing this product.

It takes a few days to deploy.

We have a team of 10 or 11 people for deployment and maintenance.

The pricing could be improved to make it more competitive.

This is a product that I can recommend.

I would rate this solution 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.

The interface is quite stable.

Licensing is too high. It is quite expensive. We don't have a lot of clients who apply for it because they cannot justify the price. They know it's a good product but it just is too expensive for them. So we have to send them to products that are cheaper. 

It's scalable. We don't have that concern for IBM products.

Expanding the product would depend on our client's needs. We don't have any restrictions. 

Our installation is quite fast, but the process or the competition of user testing is what takes a longer time. Normally the user has to do a Tableau test, so it's not just the deployment. After the installation, they have to spend time to test.

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

We are looking forward to the pricing packaging because we do like the product, but we are don't go for it because the price is too high and we not able to sell it to our customer.

I am a developer and this is one of the products that I use in that capacity.

What I like best are the monitoring features.

Technical support is something that should be better.

Lowering the price would be an improvement.

The deployment should be easier.

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

This is a stable product.

We have not needed to scale because we use multithreading in the flow.

The technical support for this product is not very good. Sometimes, examples we get when we ask support for help do not work.

It also does not have a large community.

We did not use a similar product before implementing IBM Integration Bus. In some instances, we have used microservice applications instead.

The deployment is complex and you need to have an experienced administrator.

The price of this product could be lower.

I would rate this solution a six out of ten.

The primary use case for the solution is infrastructure optimization. Most times the client wants to optimize their integration infrastructure and they want to simplify it. When they feel home-grown solutions are not scaling well for them in terms of complexity, in terms of speed to market, they look to this solution. Projects take long and they break down all the time. That's when the clients start thinking Integration Bus. It's a solution that offloads all the integrations of their system.

The solution offers pretty good pricing.

The technical support is great.

The solution is stable and can scale relatively easily.

The user interface is easy to navigate.

The performance is decent.

The solution offers good dashboards.

The management and monitoring on offer are very good.

IBM doesn't really have a very strong community surrounding the product. Most of its direct competitors are open source solutions, and those have an excellent and well-developed community around the tech to help users navigate the ins and outs of the product. IBM is lacking in this area. If they had more of a community, more people would know about the product. They should push to create a developer community around it and make the products more accessible to developers.

I've heard some clients are asking for autoscaling capabilities. It could improve DevOps. They might have something similar in other products, however, if they could introduce it within this product at some small level, it would make many clients happy.

We've been using the solution in the company for less than a year.

We've been pleased with the solution's reliability. It's stable. It doesn't crash or freeze. I don't recall facing any bugs or glitches. It just works well all the time.

The solution scales quite well. If a company needs to expand it out, they can do so easily.

Technical support has been good. They're responsive and knowledgeable. We've been satisfied with their support. It's been great.

The implementation is straightforward. It's not complex. What takes a long time, however, is implementing the workflows or projects. That's where the efforts is. In terms of implementation, the implementation is straightforward. However, building the integration of workflows can be a bit tricky. 

You have to pick the right project as the first project, due to the fact that you're introducing a new product inside an organization. The first project is important in terms of setting the stage for understanding the underlying functionality. It shouldn't be too complex. At the same time, it should be impactful enough that you get management support going forward. It should be a project that is big enough whereby you can see the impact of the Integration Bus. 

The pricing is pretty good. What they charge isn't unreasonable.

We're IBM partner-resellers.

The reason we've implemented the solution is driven more by our clients' demands. The clients want IBM Integration Bus, or they already have some investment in IBM Integration Bus. We want to build capability in it to support the clients. We don't have a level of experience with the solution.

My personal advice to others is to start small so that you give yourself a good preliminary base that's not too overwhelming. Most clients want to do everything with this solution, which is fine. However, it's always better to start small with a departmental project, as opposed to an enterprise-wide kind of thing. It is better to start small and tackle a practical project and get used to everything before going really big.

I'd rate the solution nine out of ten.

We use it for migration.

The most valuable feature is that it's robust and its time to market is very short.

In terms of improvement, the UI should be more user-friendly.

I have been using IBM Integration Bus for five years. 

It's very stable and very easy to scale. 

We have the VR application version of our support now but they have been very supportive. 

The deployment takes about a week or so, it's lengthy.

We're satisfied with the price, it's okay. The terms and everything are decided by the company. It's not a big deal for us.

I would rate it a seven out of ten. 

I would recommend it.