IBM App Connect Reviews

We use it to transform data, route data, and validate data. So, App Connect is an enterprise service bus (ESB), like Mule, Fuse, or Appian. This means it's really an enterprise service bus, and we use it for integration. We interconnect applications and protocols with App Connect.

I like the adapters. The adapters help us achieve scalability. If you want to connect to SAP, there's an adapter. Salesforce? There's an adapter. You want to connect to another system? There's likely an adapter for that. 

You want to connect to various services like Gmail, email, FTP, SFTP, MQ, JMS – anything you want, it's likely included in App Connect through the adapters.

The main advantage is that it's a central point. If we compare it to a country, it's the post office.

Our company has a big project for delivery and e-commerce sites. We use IBM App Connect to deliver information to our end users after they buy our products. We get information from many places, such as enterprise solutions and other applications. We send information and gather information from them to use in our web applications. We give our end users updates on the status of the products they bought from us.

The solution is very fast-paced when it comes to making things right. We can quickly download what we need if we need any app migrations for our software business. We can download it plenty of times when we need to use it. It gives us very high speed for delivering any development. 

The tool's automation capabilities have given us great automation abilities, especially on the factory side. We have many integrations, creating value by using this capability. We're canceling many manual processes and migrating them to IBM App Connect automation. This is improving and helping our way of working and developing many integrations.

We can handle many complex integrations that were difficult with other solutions. In other tools, we often needed to do a lot of coding and write many things from scratch. But with the solution, many things are already ready in the platform. This gives us high confidence and saves time, especially for complex integrations.

For simple tasks, the difference between products might not be obvious. However, IBM App Connect makes it easy in complex environments where we take data from many different applications, send it to another app, and apply algorithms. It's useful for these more complicated integrations. The solution is also more mature than other products. 

App Connect works as a middleware tool. It connects the front and the back ends. I've used it for creating a service for generating net banking OTPs. We are partners with IBM and I'm a senior software engineer.

This latest version is very scalable, flexible and user-friendly. Another advantage of this version is that there's no dependency on the queue manager. I've seen this solution change over many years, and it's now compatible with many different kinds of software, different depositories, and many different testing tools. It's great in that it can be embedded with other kinds of technologies.

We use the solution to integrate IR adaptors in SAP systems and Microsoft Graph APIs in SharePoint systems. We also use it for SFTP, STP, HTTP and REST endpoint files. 

The solution is fast and supports Open UI 3.0 certification. 

I'm part of a significant communication company in Europe, and we primarily use IBM App Connect to integrate our CRM system.

One of the most beneficial features is the ability to handle multiple communication technologies, like integrating Kafka flows, which is helpful as other teams heavily use it. Regarding error handling, I initially wrote most of the handling myself. While built-in features for error handling are built-in, it largely depends on the developer. We use a custom solution that catches all exceptions, logs them in a database, and replays them as needed. It has been effective for us for over twenty years.

Our primary use cases mostly revolve around orchestrating information between different data stores and I would say different applications as well. So we would be storing it in the operational data stores or we will be sending the information as files in one of the nodes or we will be sending it for monitoring. So basically it is just moving information from one place to another or doing some validations on the information and then putting them into a database.

I would say that we have a lot of modules in our applications. IBM App Connect has made it easier for us to segment the modules and deploy them separately on the integration server so that we can individually access them. At the same time, we also had a common module where we had a common function. We can utilize that for all the operations. So it gave us that independent isolation as well as the benefits of a shared common platform as well.

IBM App Connect is a mature product because it's been there since the mainframe time, and it's evolving.

We use IBM App Connect for the integration between the applications. You can unify the integration layer into one layer, where you manage the whole integration process. You can simplify the management, operation, and maintenance of the integration layer.

If you want to fix any of your APIs or integration connections, you don't need to do it on all tenants. You need to do it only once in one place, and it will reflect on only one channel. It works with multiple languages and protocols. So, you need to create it once and use it on any different applications that you have.

IBM needs to enhance and have a stronger offering for the event streaming part because this is the future needed for the containerization and the new integration requirement.

Currently, we are using the product as our central middleware. We are using it to eliminate all point connections and expose data centralized service hub for consumers.

It has optimized the service consumption of the consumers and improved the performance since it has a limited point-to-point connection between systems.