IT Central Station is now PeerSpot: Here's why

IBM Integration Bus OverviewUNIXBusinessApplication

IBM Integration Bus is #3 ranked solution in top ESB (Enterprise Service Bus) tools. PeerSpot users give IBM Integration Bus an average rating of 8 out of 10. IBM Integration Bus is most commonly compared to Mule ESB: IBM Integration Bus vs Mule ESB. IBM Integration Bus is popular among the large enterprise segment, accounting for 72% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 28% of all views.
IBM Integration Bus Buyer's Guide

Download the IBM Integration Bus Buyer's Guide including reviews and more. Updated: June 2022

What is IBM Integration Bus?
IBM Integration Bus is an enterprise integration engine that offers a fast, simple way for systems and applications to communicate with each other. As a result, it can help you achieve business value, reduce IT complexity and save money.

IBM Integration Bus was previously known as IBM WebSphere ESB.

IBM Integration Bus Customers
Salesbox, €sterreichische Bundesbahnen (€BB), Road Buddy, Swiss Federal Railways, Electricity Supply Board, The Hartree Centre, ESB Networks
IBM Integration Bus Video

IBM Integration Bus Pricing Advice

What users are saying about IBM Integration Bus pricing:
  • "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."
  • "The solution requires a license and is very expensive here in India."
  • IBM Integration Bus Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    PRINCEWILL OPARA - PeerSpot reviewer
    Head Banking Application Customization and Reporting at a financial services firm with 10,001+ employees
    Real User
    Top 5Leaderboard
    Good integration capabilities with an easy-to-learn language but is very expensive
    Pros and Cons
    • "The stability is mostly pretty good."
    • "Today, the IBM business rule engine, the DataPower is outside the Enterprise Service Bus. It's sold as a different feature or application. If it could be integrated, then it's able to handle a lot more of what we are doing now rather than just have a stateless ESB that you can't do much on, and a set of normal business rules."

    What is our primary use case?

    We primarily use the solution for integrations of traffic between internal applications, communications, and transactions between various internal applications. We also use it for integration with various external parties.

    How has it helped my organization?

    Before we implemented IBM to integrate with other external parties, we had buckets of applications to build, and maintenance was difficult, as was support. On top of that, integration wasn't well controlled and managed. Right now, post-implementation of IBM ESB, we have a better structure. We have better teams in development and response to customers. We have an application that is centrally managed and monitored. We have better SOA experience in our development process.

    What is most valuable?

    The feature we find most useful is the ease of development. It provides a variable within our application it can easily be used across various applications.  ESQ is very robust and easy to learn. That's the language the solution is based on.  The solution can scale. The stability is mostly pretty good.

    What needs improvement?

    There are experiences we have on the application, such as latency issues. There are no inherent components for you to throttle and measure the velocity of transactions. For that, you have to get a separate application and set up more robust rules. Then, you can handle API throttling and a number of business logic and rules. You need to implement DataPower, in order to have this. It should have been integrated into a single application rather than having to deal with various applications and components. It would be nice if everything could be packaged under one solution. Today, the IBM business rule engine, the DataPower is outside the Enterprise Service Bus. It's sold as a different feature or application. If it could be integrated, then it's able to handle a lot more of what we are doing now rather than just have a stateless ESB that you can't do much on, and a set of normal business rules.If you have the business rule engine that can help us measure velocity, throttle, monetization, et cetera, within the ESB, it would be better than it is now. There won't be any need for one to start looking out for any possible change in the near future. The initial setup is a bit complex.  This is a very expensive product.
    Buyer's Guide
    IBM Integration Bus
    June 2022
    Learn what your peers think about IBM Integration Bus. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,336 professionals have used our research since 2012.

    For how long have I used the solution?

    We've been using the solution for more than five years at this point. 

    What do I think about the stability of the solution?

    There is some latency and slowness in the application. At times, we have to restart the server, and there are some errors we can't handle. We send those to IBM. It's relatively stable, however, periodically, we have problems, which is why we have to get IBM to help us resolve them. That said, I would describe the product as stable.

    What do I think about the scalability of the solution?

    In terms of extensibility to other applications after development, it's highly extensible. The solution can scale.  We have developers, who develop various integration requirements, and we have support. Outside that, we don't have physical users using it. There are about 10 developers in all, that handle various requirements that come along. The support unit is about five people and they are handling the support.

    How are customer service and support?

    We don't deal with IBM directly. There's a local partner of IBM that assists us. We only have a direct relationship with IBM, when the local partner cannot handle a problem. Our contract is designed with IBM in such a way that we have to go through their local partner. In terms of responsiveness, the local partner is good. I wouldn't say excellent, however, they are good in response time. In terms of timeline for issue resolution, TAT for issue resolution, they are fair.

    Which solution did I use previously and why did I switch?

    Before we went to IBM, we didn't use a different solution, however, we checked in our industry and we checked how people felt about Microsoft middleware, and they didn't have a good experience. It's not robust, the support wasn't strong, et cetera. Therefore, we chose IBM. We were swayed by how other organizations, including banks in Nigeria, were mostly seeing success with IBM. We are using WSO2 for some applications, however, we do not rely on it completely as it is open-source and if we run into issues we cannot rely on help from any support.

    How was the initial setup?

    Setting up the solution is not straightforward. It's difficult and complex. We needed assistance in order to manage the process properly. It's not something you can just pick up, and then, run on your own. You need help from a partner, which involves additional costs.

    What about the implementation team?

    We didn't do it alone. We worked with IBM, and then, IBM nominated a local partner in Nigeria that worked with us to set this up.

    What's my experience with pricing, setup cost, and licensing?

    The solution is very expensive. 

    Which other solutions did I evaluate?

    We looked at another solution called WSO2. It is a lot easier to set up. It's easier to use, and it's less expensive. However, the challenge we have with that, is that the support is lacking as it is an open-source application. The support is not so strong. That's the only reservation we had for that. Outside that, we are also using it for some other applications as well. The prominent other contenders were WebLogic from Oracle, and whatever was provided by Microsoft. Among the three then, IBM came out on top in our assessment and rating. However, with the benefit of the insights we now have, if we were to do the same process again, over five years, WSO2 has done so well, and some other middleware is also doing well. Likely we would not choose IBM if we had to choose again.

    What other advice do I have?

    We are customers and end-users. I'd rate the solution around a seven out of ten. I would advise companies to evaluate and consider the options and whether they make sense vis-a-vis the benefit they hope to derive is worth the while. IBM is not cheap. They need to consider costs and make sure they have internal resources available to them. Those using the solution need to be well trained. Otherwise, the company will end up depending on third parties for everything, and that will drive up the costs further. I'd also suggest companies implement such a solution early. Load balancing is very critical in our experience. We didn't implement load balancing immediately, and that affected us. As a company is implementing, it should consider load balancing. Rather than invest on the on-prem, a company should consider the cloud. We did on IBM Unix servers on-prem, and that's pretty expensive.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Richard Whyte - PeerSpot reviewer
    Chief Executive Officer at Responsiv
    User
    Offers secure and consistent data access with resilient communication management
    Pros and Cons
    • "It allows us to avoid the need for consumers to understand multiple API protocols and security arrangements, and in some circumstances can reduce the impact of systems being unavailable."
    • "The next versions are moving toward container use. It would be a shame to make the product highly complex just to support one pattern of deployment. It is my hope that IBM continues to focus on practical functionality that is simple and cost-effective."

    What is our primary use case?

    We use the solution for synchronizing data across the enterprise and opening data to extend its use by simplifying and making it consistent regardless of its source. 

    It's for installing a line of indirection between data source and consumer to reduce contention at the source, and to add security, audit, and combine data from multiple places.

    With it, we are implementing GDPR rules on data use, compensating for systems being unavailable, and delivering low latency for website users.

    I have designed solutions for payment processing, Service-Oriented Architectures, micro-service architectures, data sharing and synchronization, and point to point data sharing using this product across banking, retail, and many other industries.

    How has it helped my organization?

    Many projects absorb a great deal of time and budget to find data and understand how to access it. This product allows data to be found and cataloged, allowing multiple projects to create a full directory of data in the enterprise over time.

    The introduction of a mediation component allows data to be combined from multiple sources and for those sources to change or expand without impacting the consumers. In some settings, the number of consumers can be significant (100+) making adapter patterns rather expensive to maintain.

    Having a single (logical) place to go for information reduces the responsibilities of the consumer for navigation - in turn allowing systems to move, update, and be replaced with reduced risk and cost. 

    The cost reductions are significant but rely on proper architecture and design.

    What is most valuable?

    The solution's most valuable aspects include:

    Data enrichment and consistent access. It reduces the need for programmers of consumer applications to understand where data is sourced, or how it is combined. It allows us to avoid the need for consumers to understand multiple API protocols and security arrangements, and in some circumstances can reduce the impact of systems being unavailable.

    Data mediation and secure access. It reduces programmer error and hides the underlying systems, making it simpler to change them. It imposes a line of control between consumer and source, reducing the scope of testing needed for new consumers, and avoiding tests on consumers when the source changes.

    High-performance data management for data in motion. The product supports clustering and can be tightly integrated into IBM MQ, making it a perfect platform for payment processing and high-performance data processing (50,000 tx/sec and above). For those that do not need the performance, this translates to cloud consumption savings.

    Resilient communication management. The product can use transactional integrity to assure consistent data and non-loss communications (especially when combined with IBM MQ). This means that when processing large numbers of transactions no time is lost trying to discover what was lost.

    What needs improvement?

    The product has been well managed and continually improved throughout the time I have used it. 

    There is very little that can be improved. It already contains adapters for MS-Dynamics and other enterprise packages and supports many protocols and transmission structures. 

    The next versions are moving toward container use. It would be a shame to make the product highly complex just to support one pattern of deployment. It is my hope that IBM continues to focus on practical functionality that is simple and cost-effective.

    For how long have I used the solution?

    We've used the solution for 20 years - since it was previously named MQ System Integrator.

    What do I think about the stability of the solution?

    IBM ACE is very well engineered and very stable. We have several customers running old versions that have been 100% reliable for their operational lives.

    If an installation does encounter a failure, for example power failure, the product is good at reporting useful messages, and in combination with IBM MQ to protect data running through the system. The product can be installed in a clustered configuration to remove single points of failure, and to scale to accommodate higher loads.

    It's very stable.

    What do I think about the scalability of the solution?

    This solution is highly scalable and resilient. It's combined with MQ or load balancers for fault tolerance and highly parallel processing.

    It's highly scalable.

    How are customer service and support?

    In my experience, support has always been very good for this product. 

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    I have previously used databases to store and forward and C-programs to manipulate data. When this could no longer cope (sometime in the 1990s), I discovered IBM MQ and other messaging products, which are designed to do what we were building. The MQSI product of the time was simply magic and the latest incarnations (App Connect Enterprise) are far beyond anything that could be done with a database. 

    I have reviewed other technologies, including Microsoft, open-source, and others. It remains my opinion and experience that this product delivers quicker development and more reliable outcomes.

    What about the implementation team?

    A was working as part of the vendor team, as part of the implementation consulting organization.

    What was our ROI?

    Very much depends on the industry and project.

    What's my experience with pricing, setup cost, and licensing?

    Installation of the base product has been simplified over the last five years or so, and is now fairly straight forward. 

    You need an infrastructure design for the product deployment and an integration architecture and design documented and agreed to get the best from this software. It is relatively easy to program (Extended SQL, Java, and other options are available), however, it's important to think and take advice before you start.

    The product is generally priced per processor core.

    Which deployment model are you using for this solution?

    On-premises

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Other
    Disclosure: My company has a business relationship with this vendor other than being a customer: I am the CEO of Responsiv Solutions (responsiv.co.uk), an IBM business partner. We choose to use this product because it does what it says on the package. Our services include integration architectures and design, as well as business automation.
    Flag as inappropriate
    Buyer's Guide
    IBM Integration Bus
    June 2022
    Learn what your peers think about IBM Integration Bus. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,336 professionals have used our research since 2012.
    Qudrat Khan - PeerSpot reviewer
    Sr. Manager Software Quality Assurance at UBL
    Real User
    Top 20
    A platform to seamlessly integrate applications. Regretfully it may have session management issues
    Pros and Cons
    • "Promotes the reuse of developed resources to more efficiently consume resources."
    • "Seamlessly integrates your different applications."
    • "Session management can sometimes hand forcing server reboots."
    • "The product lacks an integrated testing module."

    What is our primary use case?

    We are using Integration Bus for SOA (Service-Oriented Architecture) services. We are using it to connect APIs to servers, we are using it as an integration bus for hosting, and we are hosting our web services over it. I am using and testing this from the QA (Quality Assurance) perspective.  

    What is most valuable?

    The Integration Bus has provided us with a certain level of security. For instance, before we used this solution, we were directly connecting to databases through a DB link. We were able to stop that practice and make it more secure using Integration Bus. It has also provided us with the capability to reuse developed services. Services we developed can now be used with multiple systems and we are able to remove duplicate applications due to this advantage.  

    What needs improvement?

    Surely something that can be improved is session management. Sometimes sessions hang. Practically every day we hear about session congestion and this kind of thing. Troubleshooting the issue has become a long-standing problem. Where the true problem lies is a challenge for our support team.  

    The session management issue may be a bigger problem for us because our support team is not so highly trained. Also, sometimes our developers are not able to dig down to locate the actual problem. To resolve the issue when it occurs, we have to at least restart the server. It is not really solving the problem, it just relieves the symptoms. These session management problems are the basic issues we are having, but otherwise, our services have become better after bringing in the Integration Bus.  

    One thing I would like to have added to Integration Bus is a plugin — or some other software, — to enable testing the performance of our services from the application hosted on the IBM service. I think that the users of the system should be able to get something like that and somehow do performance testing on their own. Currently, I have used some studio or some plugin to find these results. Another option is using services that are available that I have also tried. If IBM could provide this same type of testing capability in its application, that that would be great. It would enable us to report to our business on the facts about how much we have improved from the earlier architecture.  

    For how long have I used the solution?

    We have been using IBM Integration Bus for the last three years.  

    What do I think about the stability of the solution?

    It is a stable product especially with the release of version 10. We had problems with version 9. But now, version 10 was really a lot more stable and a lot of things have improved. We are much more satisfied with the product and stability of the performance. It is fairly rare that we are unable to troubleshoot something. But I think that most of the problems that we have, from my point of view, is because we are not better trained on the product as a whole. Maybe training could resolve some of our troubleshooting issues. Everything may not be the fault of the product.   

    What do I think about the scalability of the solution?

    We had scaled up the product usage, so I know it is scalable. We were only using it with a few systems in the beginning and now we are using it with a whole bank of systems and all of the systems are integrated tools.  

    How are customer service and technical support?

    The IBM partner that we are working with here is System Limited. IBM was not directly supporting us during the installation and if we have issues we work with the IBM partner.  

    Which solution did I use previously and why did I switch?

    We did previously have another solution called BixTalk which we were using four to five years ago. One major problem with BizTalk was that we had very few people available who were actually trained on it. Secondly, there were some sever issues as well. We had a synchronization problem on top of that. Because it was so long ago I do not remember all the issues. Maybe we did have some other problems also. But we had a problem with the product support as well.  

    How was the initial setup?

    From an installation point of view and just initially setting up this product, it required a lot of configuration. The configuration is the harder part of the installation. Otherwise, the installation was done in a few days by our team. I do not remember exactly whether we had any major problems in doing that, but it could be there were problems and I just did not hear about them.  

    There were a lot of things to configure, but that was taken care of by a different department. Our operations department would be the group that handled this. So I do not have actual first-hand information because I did not participate in the process.  

    What other advice do I have?

    It is a little hard to suggest a product for someone else without knowing anything about their situation. I would surely recommend it for companies that have lots of applications that they want to integrate. This is mostly what I would recommend it for. If you want a platform that seamlessly integrates your different applications, IBM Integration Bus for you.  

    On a scale from one to ten where one is the worst and ten is the best, I would rate IBM Integration Bus as something like seven to eight. For the time being, I will give it a seven. I am pretty much satisfied with the product, but there are certainly ways I have mentioned in which it could improve.  

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Integration Engineer at a financial services firm with 1,001-5,000 employees
    Real User
    Simple to use in the data stage and good for moving a file from one location to another
    Pros and Cons
    • "I use the integration of Kafka and the message flow, which is really good. It is also good for moving any file from one location to another. Using IBM Integration Bus in the data stage is pretty simple. You can see the preview and other things. The MQ server integrated with IBM Integration Bus is really great. I don't have to do a lot of configuration from that side. It is really good."
    • "It needs improvement in terms of technical support as well as in terms of integration of data mining. I am not convinced about many things in this solution, such as the conversion of the DFDL or copybook file, which is the conversion from a text file to XML. It is very complex. They should also provide more information about this solution in the IBM Knowledge Center. I can get a lot of information from the IBM Knowledge Center about DataStage, but I don't get that much information about IBM Integration Bus. There is hardly any information even on the internet and various channels such as YouTube. They can provide good step-by-step documentation based on a company's requirements. It would be really helpful. My company is mainly looking for data mining and communicating with multiple servers. IBM Integration Bus is good for communicating with multiple servers, but it needs improvement for XML conversion and data mining. We have a lot of old systems that use XML."

    What is our primary use case?

    We are trying to use IBM Integration Bus in our organization. We have multiple things to do. Like DataStage, we also have SAP BODS as another ETL. We are also using JAM Server and Java. 

    Instead of separately writing the Java code and restful web service and then using the ETL and JAM Server to call on a file basis, I am thinking of using IBM Integration Bus. I have a message flow. Once I drop a file, IBM Integration Bus will pick up all the functions, do everything on the MQ Server, and finally fit it with the web service, which is also created in IBM Integration Bus. I would have the complete message flow in one architecture site. I can apply it by using ETL, Java, and the JAM Server. However, it is failing at the data mining stage itself. It could be because of my lack of knowledge of IBM Integration Bus.

    What is most valuable?

    I use the integration of Kafka and the message flow, which is really good. It is also good for moving any file from one location to another. 

    Using IBM Integration Bus in the data stage is pretty simple. You can see the preview and other things.

    The MQ server integrated with IBM Integration Bus is really great. I don't have to do a lot of configuration from that side. It is really good.

    What needs improvement?

    It needs improvement in terms of technical support as well as in terms of integration of data mining. I am not convinced about many things in this solution, such as the conversion of the DFDL or copybook file, which is the conversion from a text file to XML. It is very complex.

    They should also provide more information about this solution in the IBM Knowledge Center. I can get a lot of information from the IBM Knowledge Center about DataStage, but I don't get that much information about IBM Integration Bus. There is hardly any information even on the internet and various channels such as YouTube. They can provide good step-by-step documentation based on a company's requirements. It would be really helpful.

    My company is mainly looking for data mining and communicating with multiple servers. IBM Integration Bus is good for communicating with multiple servers, but it needs improvement for XML conversion and data mining. We have a lot of old systems that use XML.

    For how long have I used the solution?

    I have been using IBM Integration Bus for two to four months.

    How are customer service and technical support?

    I contacted technical support, but I wasn't able to get the correct answer. I feel I wasn't given a good response. I was communicating with a person from technical support, and he took two to three months to help me with the support. Finally, he delegated that ticket to some other person, and he resolved my issue in one week, but the solution was not convincing. 

    I wanted to know how DataStage does one-to-many and many-to-one mapping because it was failing in IBM Integration Bus. I have a DFPL file, and I have an XML Schema. I want to map the added element from the DFPL file to the XML Schema. The technical support person was saying that you have to write the ESQL code for mapping, but I don't know how many elements are there. Suppose I have 100 elements for one area at present, but next time, I might have 90 elements. He was saying that you should know somehow where IBM Integration Bus is failing, but there was no way to find that out. The mapping for that element was not there in the dynamic run-time query.

    How was the initial setup?

    The initial setup is complex. It is not user friendly. When you have a file in the MQ Server, it moves to the next directory, which is the output. It is very complex to call a web service. It should just give the setup of the endpoint and do some basic stuff so that it can be consumed by the web service. It might be complex because of my less experience in using IBM Integration Bus.

    What other advice do I have?

    I would recommend this solution if you are not doing any XML conversion or data mining and just want to use a message flow, such as reading a file and transporting to another location and then calling some message and integrating it with an existing system such as Salesforce.

    If you have a lot of integration, I would recommend hiring some experienced people for it. IBM Integration Bus is a very big product, and people don't know even 20% of this product. If people have good knowledge of it, they can really do a lot of stuff. Based on my understanding, its complexity is the reason why people don't have good expertise in this product. I am an experienced Java professional, but I am facing a lot of difficulties in understanding IBM Integration Bus.

    I would rate IBM Integration Bus an eight out of ten. It needs improvement for data mining, DFDL, and schema converter. There should also be more documentation and information in the IBM Knowledge Center.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Integration Architect at a tech services company with 201-500 employees
    Real User
    Top 5
    Seamless and easy to use
    Pros and Cons
    • "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."

    What is our primary use case?

    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. 

    What is most valuable?

    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. 

    What needs improvement?

    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. 

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    How are customer service and support?

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

    How was the initial setup?

    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. 

    What about the implementation team?

    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. 

    What's my experience with pricing, setup cost, and licensing?

    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. 

    Which other solutions did I evaluate?

    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. 

    What other advice do I have?

    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. 

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    IBM
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    Enterprise Architect, Mars Global Services at Mars Inc.
    Real User
    Top 10
    Good pricing and great features, but not easy to use
    Pros and Cons
    • "The cost is pretty cheap, compared to what else is available in the market."
    • "The solution needs to improve it's security and its proactive notification of security issues."

    What is our primary use case?

    We use the solution for supply chain management between ERP systems and warehouse management systems. We use it with multiple external partners.

    How has it helped my organization?

    The solution has improved our organization in the sense that it offers new graphical user interfaces and protocols. The fact that they have been made available has helped out business.

    What is most valuable?

    The solution has a variety of valuable features.

    The ESB characteristics are great. The transformation, protocol bridging and routing are great.

    The list of features on offer are both useful and actionable.

    The cost is pretty cheap, compared to what else is available in the market.

    The solution has been on the market for ten to 15 years, so it's had a lot of time to develop.

    What needs improvement?

    The monolithic architecture is an issue.  Due to the fact that it's a built on monolithic architecture, the solution is not very lightweight. It's not highly productive, so, in that sense, it's not so user friendly.

    The solution needs to be a little bit more business-friendly in its API management capability.

    The solution needs to improve its security and its proactive notification of security issues.

    The expiry of the passwords, certificates, and things like that need to be powered by alerts so that it's more obvious that it's something we need to update (before everything actually expires).

    For how long have I used the solution?

    I've been using the solution for ten or more years. It's been over a decade since I originally started using the product. I've been working at this particular company as an enterprise architect for the last three years.

    What do I think about the stability of the solution?

    The solution is very stable. It's reliable.

    I don't recall experiencing any bugs or glitches recently. It doesn't crash.

    What do I think about the scalability of the solution?

    The solution is scalable. When we need to expand the solution, we can do so easily.

    We have about 5,000 integrations on the product. 

    It is an integration platform, so everybody related to supply chain management uses it, and eCommerce as well.

    How are customer service and technical support?

    We've dealth with technical support in the past and have been more than satisfied with their level of service. They are knowledgable. They respond quickly. I'd rate it nine out of ten overall.

    Which solution did I use previously and why did I switch?

    Although we didn't use another solution per se, we do use MuleSoft. 

    MuleSoft is more lightweight. It's not as monolithic. We use MuleSoft and another IBM solution. However, we've been using IBM Integration Bus for such a long time at this point. It's been ten to 15 years or so. We've only used MuleSoft for the last three years. It has high productivity and a good number of integrations and the API exchange capabilities.

    We run the solutions in parallel.

    MuleSoft is a pretty good solution, however, we've noticed that the pricing over the last few years has gone up and it's become quite costly.

    How was the initial setup?

    The solution has been on the market for over a decade, so the initial setup is pretty straightforward. They've had time to perfect the process. There's also a lot of people who understand how to install it, as it's a mature product with lots of history. Many people have worked with it.

    What's my experience with pricing, setup cost, and licensing?

    The pricing is pretty good. We've noticed that it's quite reasonable, whereas, for example, solutions like MuleSoft are rising. Salesforce recently acquired MuleSoft and has grown its market share, however, the pricing is turning people off. IBM is much more reasonable.

    What other advice do I have?

    We're IBM customers. We don't have a business relationship with IBM.

    The solution is deployed on an underlying platform in the traditional MQ.

    I'd rate the solution seven out of ten. I'd rate it higher, however, it's not user friendly. That said, it works really well.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    CTO at a tech vendor with 11-50 employees
    Real User
    Top 20
    Great user interface, good technical support, and very stable
    Pros and Cons
    • "The solution is stable and can scale relatively easily."
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

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

    How are customer service and technical support?

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

    How was the initial setup?

    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. 

    What's my experience with pricing, setup cost, and licensing?

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

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: partner
    Assistant Vice President at a financial services firm with 501-1,000 employees
    Real User
    Top 10
    Quality components, good service, and exceptionally stable
    Pros and Cons
    • "Having the solution come from IBM you know you are receiving a product of quality in components and in the services, it is very good."
    • "We used a third-party vendor, who help us install the solution and it was not easy."

    What is our primary use case?

    We are using the solution as an outer layer for all of our API calls we are making outside of our own devices. All APIs integrations are routing through the ESB only. We are using it for IIB server components and the DataPower, which is an API gateway. It is providing us with a security layer because all the outside calls do not have direct communication with our own server, this middle layer is called the ESB. 

    How has it helped my organization?

    The solution has helped my organization because any new integration coming to my backend system, we can easily implement it in a shorter time. This is because the middle layer takes care of all API language conversions or the code conversion, and also does the maintaining of the logs.

    What is most valuable?

    Having the solution come from IBM you know you are receiving a product of quality in components and in the services, it is very good.

    What needs improvement?

    I do not think there are any improvement areas because it depends on what exactly the use case for this ESB is. Some organizations are having a lot of integration and they will choose a regular ESB. While others will choose the security purpose route, making an extra layer. It depends from organization to organization, to determine how this solution can be improved from their specific use cases. Otherwise, I think that there are not any relevant improvement areas to give.

    For how long have I used the solution?

    I used the solution in my last company for a long while.

    What do I think about the stability of the solution?

    The solution came to the market a long while ago, it has had time to mature. It is really stable and large organizations can rely on it. Smaller companies could too but it is too expensive.

    What do I think about the scalability of the solution?

    It is a scalable solution. You can have any number of integration, it depends on the server and how much space you are providing to the IIB servers. We plan to have more than 50 wired integration by the end of the year.

    How was the initial setup?

    The installation is not easy. You need experts who know how to install this IIB. The common technician will not have the knowledge to do it. You will need assistance installing the solution even though on IBM's website you can download the complete user manual explaining how to install the IIB servers. 

    What about the implementation team?

    We used a third-party vendor, who help us install the solution and it was not easy. If you have most things in place at the site the whole installation process can take approximately three days. 

    To do the complete deployment you will need at least one architecture that understands this IIB solution. It all depends on what kind of IP division architecture you have. Based on the project's scope, you then can define your team. There is no certain number of how many team members is required. It depends on your project, how large it is, and based on that you can decide how much manpower is required.

    What's my experience with pricing, setup cost, and licensing?

    The solution requires a license and is very expensive here in India. Large organizations will be able to afford it but smaller companies will have a difficult time paying for the solution at the current price.

    What other advice do I have?

    I am going to continue to use this solution, when you purchase this solution you have spent a lot of money, you have to continue to use it to make a return on investment.

    I would recommend this solution if they have a large budget.

    I rate IBM Integration Bus an eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Buyer's Guide
    Download our free IBM Integration Bus Report and get advice and tips from experienced pros sharing their opinions.
    Updated: June 2022
    Buyer's Guide
    Download our free IBM Integration Bus Report and get advice and tips from experienced pros sharing their opinions.