The solution is a beneficial tool for integration purposes. It allows the integration of multiple systems irrespective of their format and type of connectors. Using it, we don't have to convert systems into different platforms such as JSON, XML, CSV, Excel, etc.

I really like SQL integration nodes, HTTP nodes, event handling, event monitoring, the performance of the solution. 

We use IBM Integration Bus for document conversions.

What IBM brings to the party is its whole support infrastructure. I'm scaling the product with a granular approach. If I apply it in a corporate environment, what can I do with it? And if I decide to take IBM Integration Bus, can I fulfill everything I know needs to be done, including what will come up? For example, if we've got a new feature we've never heard about, will we be able to use it? The answer is yes. The multi-approach and the multi-capabilities are 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.

We can have multiple endpoints, and we can integrate different applications from different platforms. In a large-scale enterprise setup, it becomes so easy to establish communication between applications. You can connect an application to other applications, other legacy applications, and databases. You can also connect with those applications that are in the cloud.  You can connect with other well-known applications, such as Salesforce, SAP, and Workday, by using IBM Integration Bus.

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

I like the API lead integration, which is more focused, and I also like real-time integration.

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.

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.

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.

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 is a very strong tool. It helps in integrating the front-end and back-end systems.

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.

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.

IBM Integration Bus's best feature is integration.

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

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

The most valuable feature is the API integration.

The Cloud Pak for Integration is a useful feature.

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

The message queue connectors are the most valuable feature. They have built-in connectors for most of the systems, like SAP and Oracle Database.

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

The most valuable feature is the security.

I found all features valuable. There are a lot of connectors. 

It makes the communication between multiple and heterogeneous applications so easy. We can bring together different messages and applications from different platforms and connect them through IBM Integration Bus.

My favorite feature is the XML-based DFDL mapping, which is a tool that allows you to graphically map legacy data formats to modern data formats. I like it because there is less programming involved. On the internet I do not see many users who are aware of this capability or its importance. Since I have a theoretical background in this area I was able to quickly understand its value. In the past, we had to do a lot of programming in Java, whereas now, it is just linking one node in one format to another node in another format. The linking is done in a very smart way, and behind the scenes, the solution knows what to do. For different types of inputs and outputs, the interface already knows how to do the translation or conversion. All you have to do is draw a line and make simple additions. It has reduced the programming from one hundred percent down to ten or twenty percent.

In this solution, you can design the workflow too, graphically. There are two graphical tools in this solution. One of them is for the format conversion and it is called mapping. The other one is actually developing the application itself. It is a good GUI that I really like.

The solution's features are all quite useful. We use all of them.

1. REST API design and development support are useful. Building and exposing APIs using GUI API designer with editor makes implementation a breeze.
   
2. Pub/Sub support (using IBM MQ) and MQTT broker support bring complex patterns (CQRS, etc) and services to life real quickly.
3. Web interface, REST API for viewing services, admin, stats, and deployment are premium features, which makes IIB stand among its competition.
4. Several connectors for various different protocols.

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

We currently use version 10 of IBM Integration Bus. The most beneficial feature is the integration we have with legacy services. We can do the integration to expose other technology to stop, rest and manipulate the output of many legacy services.

IBM Integration Bus' most valuable features are its performance, fast and easy development, and easy support.

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.  

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.

This product provides a relatively easy way to develop integration solutions.

This solution has very good, high-availability features.

From a performance point of view, it's very good and it doesn't need very much in terms of CPU resources.

I have found the inbound and outbound adapter confirmations 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.

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.

This solution is very reliable and it is easy to learn.

There are many connectors to different sources and it's easy to scale.

Also, it is easy to parametrize the integration of bus applications during building or deployment. For instance, set up names of the queues, set up binded services URL, set up or change user-defined parameters.

The message queue feature is very valuable.

The solution addresses all of our middleware needs in respect of transformation, parsing, security and stability; everything really. 

The solution offers good performance and it's stable. The message enrichment and message transformations are great features and the solution also has great security.

The biggest advantage of this solution is that it is very easy to learn, and very easy to build applications. The learning curve is not steep and it is something that you can pick up within about two weeks.

There are a lot of inbuilt interfaces like ISO and SAP. Having all of these interfaces already built makes integration very easy and straightforward.

The current version of IBM Integration Bus, now called App Connect Enterprise, provides operators for deployment in the OpenShift cluster, which makes deployment much easier and significantly increases the scalability and reliability of the integration solutions.

With respect to our enterprise and SOA compliance (this product fits within the SOA compliance category), we want to talk about microsolution architecture, as enterprises generally enable SOA first before going to microsolutions. It will have to have a long-term approach on the SOA category, as IIB fits with a lot of other IBM products, like the WSRR, IBM DataPower, and MQ. It has a lot of advantages when we are using it or enforcing SOA as an architecture for our enterprises.

I have found IBM Integration Bus is very useful because it can integrate multiple backend applications.

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

Multiple protocols support,  development environment is user friendly.

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.

• WebSphere MQ Connectivity: MQInput node and MQOutput node
• Load Management: We can configure more than one instance of an application
• High Availability (multi-instance broker)
• ESQ
• Microsoft .NET Support/.NETCompute node: This has helped us to reuse our existing .NET code
• Web Standards connectivity: HTTPInput node and HTTPReply node

The IBM Integration Bus is a very strong, very easy-to-use product. 

We prefer it due to the fact that we can get support from IBM when we need to, as opposed to using open-source tools that do not have support.

Sometimes companies have systems from IBM, Oracle, HP, et cetera. IIB is a good candidate to enable all heterogeneous systems to exchange data smoothly without any effort.

The product is a user-customized tool so that you can adjust it to your specific needs pretty well with little trouble. 

The initial setup is easy.

IIB is feature rich product it is hard to point to a single feature , but most important is IIB supports most communication protocols out the box (SOAP/REST/HTTP/MQ/JMS/TCP/Files) 

Native support of Asynchronous calls .  support of multiple message formats (XML/JSON/ CWF/CSF/SWIFT/HL7....)

Global Transaction Co-ordination

Horizontal and Vertical Scalability .

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. 

The solution is similar to Adobe X Pro. We can intersect with any of those items.

The scalability is very good.

The integration with other tools is excellent. It integrates well with batch issues.

Overall, the solution works very well.

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.

It has the ability to be deployed without rewriting the code. 

The interface is quite stable.

What I like best are the monitoring features.

It aligns well with containerized environments, which increases its scalability and high availability. 

Overall, it has good coverage of features.