IBM Integration Bus Reviews

Typically, when engaging in application integration, especially when receiving data through an integration gateway, the common practice involves routing or transforming the message. This process aims to enrich the data before forwarding it to other downstream systems, and we utilize IBM Integration Bus for it.

It offers easy adaptability, allowing for seamless modifications. With versatile nodes, it facilitates effortless connections with other integration components. The platform supports diverse functionalities such as making web service calls, conducting file transfers, and interacting with databases. Additionally, it accommodates synchronous communication, addressing a variety of technical implementation needs. It effectively replaces the effort involved in such coding tasks.

It can be implemented as an enterprise service bus to seamlessly connect all applications within your enterprise. This tool serves as a bridge, ensuring a smooth flow of data across all applications, regardless of their formats or communication protocols. By leveraging its features, you can efficiently manage and facilitate communication between various applications in your enterprise ecosystem.

It would be beneficial for it to function more as an iPaaS, with the runtime available in the cloud, potentially on platforms like AWS, Azure, or Google Cloud. This approach enables broader accessibility, allowing more users to leverage the service.

I have been using it for more than nine years.

It exhibits high stability, consistently performing well in the majority of environments. Any disruptions typically arise only when there are issues with the underlying infrastructure supporting the Integration Bus.

While I can't provide specific user numbers, we have numerous clients across the globe who rely on IBM Integration Bus to meet their business needs. If you aim to enhance the scalability of your integration application developed in IBM Integration Bus, there are specific options and features you can utilize. This enables you to scale up your applications effectively, allowing them to handle a higher volume of requests from various sources.

I am confident that we would receive a prompt response from IBM whenever we encounter any technical issues or require technical support.

The initial setup was relatively straightforward and not overly challenging. Establishing the required environment to run the IBM Integration Bus was a simple process. All that was needed was some server space to install and bring up the runtime environment.

A common practice is the implementation of CI, CD, and DevOps tools. These tools automate the deployment process seamlessly. Whenever code changes are made and pushed, the configured DevOps tools take over, ensuring an automated deployment without the need for manual intervention. This streamlined approach enhances efficiency and minimizes manual efforts during the deployment phase. Maintenance for IBM Integration Bus is well-established. As part of routine maintenance, regular fixes are provided for the product, contributing to the overall stability. Daily monitoring of IBM Integration Bus objects is a crucial aspect of maintenance. We maintain a dedicated team that monitors these objects 24/7, both on-site and offshore. This continuous vigilance ensures that any potential issues are promptly identified and addressed, minimizing any impact on business operations.

I find it to be a highly regarded solution. If you are considering the implementation of an Enterprise Service Bus, this product emerges as a robust and effective solution for your business needs. Overall, I would rate it eight out of ten.

Whenever we want to secure our data, we connect to IBM Integration Bus, and they use that for security.

One very good feature is the UI, and it's easy to understand how to implement the tool.

The configuration could be improved. If you build an option in the toolkit, such as a health configuration, we should load the command and configure it. We should then just run checks, and the configuration should be completed.

I've been working with the solution for almost five years.

The solution is stable. I rate the solution's stability a five to six out of ten. 

The solution is scalable. I rate the scalability a five to six out of ten.

The initial setup is easy. If the customer requires any API on any server, it should take a maximum of five to six seconds to deploy.

The solution is easy to understand, and it's a good tool for development and security. I rate IBM Integration Bus a nine out of ten.

We are a solution provider and this is one of the products that we implement for our clients. Usually, they want to use this for consolidating the services. It is used to integrate their core insurance systems with the rest of the environment.

We try to enable this kind of service-oriented architecture (SOA) to assist our clients with consolidating all of their services.

The most valuable feature is the API integration.

The integration is difficult to manage.

Migrating to this solution is complex and it would be helpful if they had a way to convert existing integrations.

We have been using IBM Integration Bus for more than three years.

From a scalability point of view, I think that this product is good.

I would say that it is good for an enterprise-level customer.

We receive our technical support through an IBM partner in Taiwan. However, developing this kind of project required asking for assistance from the IBM Lab Services. Without Lab Services, our support would not have been as strong.

Migrating to this solution is complicated and not simple to do if they already have API integration between systems.

We also work with TIBCO and Oracle ESB solutions. We find that our customers have had a good experience with them and there is always a lot of interest in these two products.

IBM Integration Bus is a good product and I would recommend it for enterprise customers.

I would rate this solution a six out of ten.

We use the solution for a digital payment system.

The Cloud Pak for Integration is a useful feature.

The solution’s pricing could be improved.

I have been using IBM Integration Bus for five years. We are the solution provider.

The solution is stable.

The product is scalable. There are four customers using this solution.

The initial setup is not complex, but you should have a good understanding of programming. Installation depends on the project. For some projects with a limited interface, it takes two to three months, but for a bigger and complex one, installation can take up to six months.

In banks, it is deployed on both Cloud and On-premise.

The solution is expensive.

Overall, I rate the solution an eight out of ten.

IBM Integration Bus can be deployed in many ways, such as on-premise, cloud, and hybrid. 

The current customer that we have wants to have a hybrid deployment. We're investigating how they can manage to do it. For the hybrid deployment, they will have an instance running in a docker image, or in an Amazon AWS. The heavy operations will be done by the on-premise version. Which is what we currently have.

The most valuable features of the IBM Integration Bus are flexibility. It's also an alternative for integrating it with other projects, which we are not ready at this time to do, such as switching to tunnels. The tunnels would be used with other partners to make sure everything is secured.

IBM Integration Bus could improve by having a more lightweight installation. Additionally, automation could improve.

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

IBM Integration Bus is highly stable.

We have approximately four clients using this solution.

The technical support is very good, they have a fast response.

The installation of the IBM Integration Bus was straightforward. The time frame that it takes for the deployment depends on the environment the customer has. 

The licensing model of IBM Integration Bus is good. It's a yearly subscription. However, the price is depending on the model that you choose. If it's a Cloud version, then you can pay per month or you can pay it annually upfront. There are three-year options available, but it depends on what deployment you have.

As more people are moving operations toward the Cloud. The Clouds are offering subscriptions. They will charge you based on what they're processing. Whereas the on-premise version, the vendors offer a perpetual license. It doesn't have those limitations that the subscriptions models have for the number of transactions. What most of the vendors are doing is they will more or less charge you for a small, medium, or large package based on the number of transactions and they will bill your account.

IBM Integration Bus is a very good solution and they have come a long way with improvements over the years.

I rate IBM Integration Bus a 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.

We use IBM Integration Bus within a finance domain.

The product helps efficiently work with different connectors from different back-end systems.

IBM Integration Bus needs to be more compatible with stable connectors for specific domains. For instance, it has two protocols: ISO 8583, a legacy protocol, and ISO 2022, which works on XML for the finance sector. Similarly, they should add connectors to banking applications and other specific industries.

We have been using IBM Integration Bus for ten years.

Being in the market for quite some years, IBM is a very stable and mature product. I rate its stability a seven out of ten.

The technical support services are good.

Primarily, our customers have the product deployed on-premises to follow protocols. Some customers deploy on private clouds as well. The product’s installation and configuration process is straightforward. It takes six months to two years, depending on the complexity of specific requirements.

I rate IBM Integration Bus 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.