IBM Integration Bus Reviews

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. 

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.

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.

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.

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

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.

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.

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.

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.

We use this product as an integration point between systems. We use it for logging and transformation of data between backend and frontend.

Our use case involves the communications industry.

The most valuable feature is that it is clear and easy to learn.

There is a community available where I can find a solution if I am facing a problem.

The interface could be more user-friendly.

I have been using IBM Integration Bus for about one year.

IBM Integration Bus is stable, although it depends on the efficiency of our code, the network stability, and the infrastructure. It will be stable if all of the applications are running efficiently.

We have a support agreement that is included with our license and whenever we have a problem, we contact them. In my experience, they provide good support. They also provide good material and documents.

I have not used another similar solution by another vendor, although I have been part of projects where other systems had been implemented.

The initial setup is straightforward, especially with Java and EasyCODE.

We make use of tools like bash scripting when we deploy files. When we deploy a single file, it takes about five minutes.

In summary, I can recommend this product because it is easy and straightforward to learn and use. It is also stable and has a good market share. All of the features that I have needed already exist.

If a developer would like to shift and try becoming an integration developer, then this is a good product to work with.

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