Avinash-Arepaka - PeerSpot reviewer
Technical Lead at a computer software company with 5,001-10,000 employees
Real User
Top 20
An excellent solution for transformation and routing with a responsive support team
Pros and Cons
  • "The features I have found most valuable in this solution are transformation and routing."
  • "The product does not provide API management."

What is our primary use case?

The product helps us develop integration applications. It also enables communication between applications from different environments.

What is most valuable?

The features I have found most valuable in this solution are transformation and routing.

What needs improvement?

IBM Integration Bus doesn’t provide some features that MuleSoft provides. These features should be added to the solution.

The product does not provide API management. We have to use a separate tool called API Connect for our needs. It would be good if IBM could combine these tools.

For how long have I used the solution?

I have been using the solution for the past nine years.

Buyer's Guide
IBM Integration Bus
March 2024
Learn what your peers think about IBM Integration Bus. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.

What do I think about the stability of the solution?

I rate the stability an eight out of ten.

What do I think about the scalability of the solution?

The people in our organization who faced scalability issues deployed the product on the cloud, where they could make it scalable. I rate the scalability an eight out of ten.

How are customer service and support?

I have spoken with the support team about a couple of issues. They were really helpful, and the response was very fast.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is straightforward. We did not face any challenges.

What about the implementation team?

It took us a couple of minutes to deploy the product. We deployed the solution with our in-house team. A team of two to three administrators usually monitors the product in the production environment.

What other advice do I have?

I am using the latest version of the solution. We use Jenkins to deploy the applications we build on IBM Integration Bus. My organization is one of the largest IT service providers, with hundreds of customers across the globe.

We depend on IBM for patches when there are some issues in the production environment. I am a developer, and I work in solution development. I have worked with multiple organizations for multiple accounts. I would recommend the solution to others. IBM Integration Bus is a leading product.

Overall, I rate the product 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.
PeerSpot user
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.
PeerSpot user
Ismail Aboulezz - PeerSpot reviewer
Ismail AboulezzMD at LeaseWeb
Top 5Real User

I strongly agree.

Buyer's Guide
IBM Integration Bus
March 2024
Learn what your peers think about IBM Integration Bus. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
Head Banking Application Customization and Reporting at a financial services firm with 10,001+ employees
Real User
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.

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 technical 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.
PeerSpot user
PeerSpot user
IBM Integration Bus Developer at Telecom Egypt
Real User
Top 10
Great stability, stream lined convergence of other products, and works well with critical projects, but the performance needs to be enhanced
Pros and Cons
  • "The most valuable thing is the loose coupling and making the change in only one stack of the ESB layer or the middleware layer."
  • "The performance needs to be enhanced when working with the Toolkit."

What is our primary use case?

It is used for the banking domain and telco. We use it for integration between vendors from core banking and the other channels, for example, buyers, CRM and codes.

What is most valuable?

The most valuable thing is the loose coupling and making the change in only one stack of the ESB layer or the middleware layer. This helps in big projects and when we have multiple channels calling back at the same time.

What needs improvement?

The Toolkit itself is based on Eclipse and Java, and it does not respond sometimes. When we are working on the Toolkit using or working on our PCs or remote desktop the program has issues with performance. The performance needs to be enhanced. More labs for developers who want to learn about this technology for trial. They may provide a trial version of App Connect or Toolkit to try it for themselves.

For how long have I used the solution?

I have been using IBM Integration Bus for the past five years.

What do I think about the stability of the solution?

It is very stable and used by very large companies and banking in EMEA, or in Egypt and the Middle East. It is used in very stable projects and critical ones that have payment transactions, like wallets or through transactions, and internet banking.

What do I think about the scalability of the solution?

It is very scalable.  We have twenty different developer and administrator teams working with it.

How are customer service and support?

If we have to fix an installation or other support needed, an administrator opens a ticket with IBM and they support it, especially if it is in the license agreement with them. But, I am a developer, not related to technical support. From the community side, I would rate technical support a seven out of ten because IBM documentation is available over the internet and on other websites.

How would you rate customer service and support?

Neutral

How was the initial setup?

The initial setup is straightforward and takes about one minute to deploy

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

We have the enterprise edition, and it is licensed yearly. I do not know what the cost is.

What other advice do I have?

They can converge other products, ESB, or SOAR architecture. I may recommend IBM as a solution tool for a business if they are looking for a stable environment. They will find support on the community forum. I would rate IBM Integration Bus a seven 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.
PeerSpot user
Solution Engineer at Capgemini
Real User
Top 20
Simple installation, beneficial for legacy systems, and good support
Pros and Cons
  • "I am into microservices using Java Spring Boot, but if we are using legacy systems, IBM Integration Bus is very good for them. They have their own computational logic called EC12, their own proprietary language. You can do any kind of complex logic and can implement other ESVs that I have seen."
  • "IBM Integration Bus can improve JSON Schema validations. We don't have any kind of nodes that can support that kind of validation. If we want to containerize it by means of the docker's containers in the clouds, we are not able to manage it very well."

What is our primary use case?

We are using IBM Integration Bus as a messaging solution for our customers. They have legacy systems. Some are MQ systems, file-based systems, app-based systems, and ERP systems. We place it in the middle of integrations. One system sends messages or communicates to another system written by us.

What is most valuable?

I am into microservices using Java Spring Boot, but if we are using legacy systems, IBM Integration Bus is very good for them. They have their own computational logic called EC12, their own proprietary language. You can do any kind of complex logic and can implement other ESVs that I have seen.

What needs improvement?

IBM Integration Bus can improve JSON Schema validations. We don't have any kind of nodes that can support that kind of validation. If we want to containerize it by means of the docker's containers in the clouds, we are not able to manage it very well.

In a future update, IBM Integration Bus could add better API management. It only supports Swagger at this time.

For how long have I used the solution?

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

What do I think about the stability of the solution?

IBM Integration Bus sometimes hangs but the IBM App Connect Enterprise successor version is a lot better.

What do I think about the scalability of the solution?

IBM Integration Bus scalability depends. The scalable of the on-premise version is difficult to scale. For example, if you're using the file processing that can be locked on the files and there is an increase in the number of threads there is some limit. The cloud version is not the same, by using a container, we can scale up to any extreme level. That kind of scalable is not there in the on-premise version.

We have 10 to 15 people using the solution.

How are customer service and support?

I never interacted with IBM for technical support. However, my clients have and they have had a good experience.

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

I have not worked with other solutions similar to IBM Integration Bus.

How was the initial setup?

The initial setup of IBM Integration Bus version 7 was complex, but the 10 and 11 versions were not difficult. We are using IBM App Connect Enterprise, the successor version of the IBM Integration Bus. IBM Integration Bus no longer exists, but the installation was quite easy. This is a single-step installation. The installation can take approximately 15 to 20 minutes.

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

The price of the IBM Integration Bus is expensive. If you compare the price to the cloud version you can purchase what you need but the on-premise version price is flat.

Which other solutions did I evaluate?

We evaluated other solutions.

What other advice do I have?

In the modern integrations in the EPAs world, IBM Integration Bus is not well fitted, because if we have legacy systems, it is fine, but if you want to manage the EPA, govern the EPA to allow people to choose the different platforms, such as the cloud platform, Mule CloudHub I would not recommend it. For the legacy integrations, I can recommend this solution.

I rate IBM Integration Bus an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Mohamed Nagah - PeerSpot reviewer
Senior Software Engineer at Giza Systems
Real User
Top 10
A strong and scalable solution that can be deployed easily
Pros and Cons
  • "IBM Integration Bus is a very strong tool."
  • "We have to stop the integration server to start the debugging process."

What is our primary use case?

We used the solution for opening new accounts for a banking system. Our client used some old techniques and didn’t have an integration layer. I created an account opening application for our client.

What is most valuable?

IBM Integration Bus is a very strong tool. It helps in integrating the front-end and back-end systems.

What needs improvement?

We have to stop the integration server to start the debugging process. The debugging mechanism of other products is better than that of IBM.

For how long have I used the solution?

I have been using the solution for six months.

What do I think about the stability of the solution?

I did not face any issues with the solution’s stability.

What do I think about the scalability of the solution?

The solution is scalable.

How was the initial setup?

The initial setup is easy, but the database is quite heavy for the local DC. It was also a little bit complex to connect to some databases.

What about the implementation team?

The deployment of the solution is very easy. We just add the integration server and drag and drop the services to the integration server. We deployed the solution in-house. We do not face any trouble in the maintenance of the product.

What other advice do I have?

I am a system integrator. In Software AG, debugging does not intervene with any other process. I also use Software AG webMethods and TIBCO. Software AG webMethods is the best product because it is very easy to develop and flexible. Overall, I rate the solution an eight 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: Integrator
PeerSpot user
Mansoor Ivanovic Mohammed - PeerSpot reviewer
CDO - Data & AI at BDC
Real User
Top 20
Flexible integration, application scaling, and helpful support
Pros and Cons
  • "The most valuable features of the IBM Integration Bus are the flexibility to easily integrate with other solutions, such as SAP or any other vendors."
  • "The cloud deployment of the IBM Integration Bus should be made easier."

What is most valuable?

The most valuable features of the IBM Integration Bus are the flexibility to easily integrate with other solutions, such as SAP or any other vendors.

What needs improvement?

The cloud deployment of the IBM Integration Bus should be made easier.

For how long have I used the solution?

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

What do I think about the stability of the solution?

IBM Integration Bus is stable. We have a lot of infrastructure running on it, and it has worked well. We have many application integrations that we used it for, and we did not have that many issues.

What do I think about the scalability of the solution?

The scalability of the IBM Integration Bus is good because it can scale within the application. The whole application installation has some scalability, not only the server. It's easy to scale.

We have approximately 20 developers using this solution and we do not plan to increase the usage.

How are customer service and support?

I have used the support from IBM and they have a ticket priority system. For example, they assign priority to the ticket, such as P1, P2, and P3. P1 is the highest priority and P3 is the lowest. When we are assigned a P1 priority we have someone contact us directly from IBM.

I rate the support from IBM Integration Bus four out of five.

How was the initial setup?

IBM Integration Bus's initial setup is straightforward. They made it really simple to install everything. The process only took a few minutes.

What about the implementation team?

We did the implementation of the IBM Integration Bus in-house. We have two people for the maintenance and support of the solution.

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

IBM Integration Bus solution is expensive and this is one of the reasons we are looking for an alternative, such as MuleSoft.

There are some additional pieces of software we need to purchase to do certain kinds of integrations, this should be included and we should not have to pay extra.

What other advice do I have?

My advice to others is this is a great solution if you can afford it.

I rate IBM Integration Bus an eight out of ten.

We are currently looking at other vendors, such as MuleSoft, to see what their offerings are.

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.
PeerSpot user
Developer at a outsourcing company with 501-1,000 employees
MSP
Top 20
Built-in nodes significantly simplified our integration tasks, easy to scale and setup
Pros and Cons
  • "IBM Integration Bus has been effective in facilitating our messaging and service-oriented architecture (SOA) or bus architecture. So, we're already utilizing it to transform the data from the source it's sending. It converts the data from the format the source sends it into the format the destination system requires. So we are transforming the messages, which are required by the destination system; that's the one way."
  • "Performance can be an issue sometimes. The tool occasionally crashes due to memory-related problems. We've reported these issues to IBM, and they are actively working on improving the tooling experience."

What is our primary use case?

We use IBM Integration Bus to communicate with existing systems like COBOL. We utilize COBOL copybooks, which we need to transform for downstream systems. We create schemas and leverage the COBOL capabilities to convert messages to the target systems. This is one example of our integration use case.

How has it helped my organization?

IBM Integration Bus integrates with various applications and systems.

We have many external customers who call our Integration Bus using the SOA WSDL. We expose WSDL to external systems, allowing them to share inputs with the Integration Bus. 

In turn, the Integration Bus integrates with additional third-party and external systems. So, it acts as a middle layer between source and target systems.

IBM Integration Bus has been effective in facilitating our messaging and service-oriented architecture (SOA) or bus architecture. 

So, we're already utilizing it to transform the data from the source it's sending. It converts the data from the format the source sends it into the format the destination system requires. So we are transforming the messages, which are required by the destination system; that's the one way. 

Another way we are routing the messages to the different destinations is based on the source and the payloads they are giving. So we are reading that payload and, based on that, targeting the task. So, we are transforming the same message to the different destinations. That's another way.

IBM Integration Bus's built-in nodes significantly simplified our integration tasks. Almost all of our solutions have benefited from the built-in nodes. Each node has its own specific functions, making them incredibly valuable for various development tasks.

What is most valuable?

Transforming the messages is a valuable feature for me. 

All the message transformations, conditional routing, and simple data movements are already built-in. 

Additionally, there are some powerful conditional processing capabilities. These features, especially conditional routing and complex data mapping, are crucial for handling multiple complex integrations.

The graphical mapper makes transformations much easier. For simple one-to-one mappings, the source and target can be directly connected, saving developers time.

What needs improvement?

Performance can be an issue sometimes. The tool occasionally crashes due to memory-related problems. We've reported these issues to IBM, and they are actively working on improving the tooling experience.

It would be great to see better memory management to avoid these crashes.

For how long have I used the solution?

I have been using this solution for five years now. I use v10. 

What do I think about the stability of the solution?

I had no issues with stability. I would rate the stability a ten out of ten. 

What do I think about the scalability of the solution?

We haven't encountered any issues with volume or performance based on our testing. While we are still developing these applications, we are confident in the solution's ability to handle high volumes.

I would rate the scalability a nine out of ten.  

How was the initial setup?

I would rate my experience with the initial setup a nine out of ten, with ten being easy. 

It's very easy to set up. It typically takes less than an hour.

What about the implementation team?

Two people were involved. One is the administrator, who has the necessary permissions and installs the product. 

The other is the integration developer, who defines the integration flows, steps, and profiles. 

One person could be from IBM support, while the other would be from the Windows or Linux administration team.

The product requires ongoing maintenance. However, the people required for the maintenance depend on the project. In my organization, we have five to ten based on our projects.

What other advice do I have?

Overall, I would rate the solution a nine 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.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free IBM Integration Bus Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Buyer's Guide
Download our free IBM Integration Bus Report and get advice and tips from experienced pros sharing their opinions.