IBM App Connect Enterprise (Software)
Cloud workflows have accelerated integrations and now demand better debugging and DevOps support
What is our primary use case?
IBM App Connect serves as our integration platform, allowing us to connect application systems and data without heavy load or heavy coding. In my current organization, we use the AWS cloud, and IBM App Connect enables us to easily integrate with that AWS cloud. We also have Salesforce and Slack alerts, so we can handle Slack channels, pop-ups, and file uploads using the platform.
Everything is on the cloud right now, so we need cloud-to-cloud support. IBM App Connect makes it very easy to integrate from cloud to cloud. The platform also supports cloud, on-premises, and hybrid integration. We are using the cloud integration for all our requirements.
Since everything is on the cloud, we have to integrate everything on the cloud for whatever we require. We use IBM App Connect for anything we need to build, any Slack-related work, and ServiceNow automation. We have ServiceNow trigger new incidents, and we have to alert those things via mail and Teams. This kind of automation is easily handled through the platform.
What is most valuable?
With minimal code, we can easily integrate with other systems. IBM App Connect offers a low-code, no-code approach. Sometimes we don't need any code, and sometimes we need a little bit of code. There are hundreds of connectors available, which reduces custom API work. The data mapping UI provides visual mapping, auto-suggest, and field mapping. Transmission between JSON, XML, and CSV formats is also possible. IBM App Connect provides hybrid integration support, which I really appreciate. Built-in error handling and security features are included, such as OAuth 2.0, TLS, secret management, and role-based access. One main feature is that IBM App Connect is Kubernetes-friendly, running well on the OpenShift container in my runtime environment.
The low-code approach significantly reduces the time of our resources. We can even reduce the number of resources because the integration doesn't require heavy coding. This saves both time and money.
I don't have an exact number, but for traditional coding that would take one day, IBM App Connect can finish the work in about four hours. Authorization and authentication API setup, which would typically require one to two days, can be finished within one to two hours maximum. Data mapping that would take around six to eight hours can be done within one hour using IBM App Connect. The same applies to error handling, testing, and fixing. Overall, 50 to 60% of the time is saved when using IBM App Connect.
IBM App Connect definitely saves a lot of time, approximately 50 to 60%. Based on the time savings, we can reduce the number of employees needed. For resource utilization, we can use fewer resources. With the time saved, we need fewer employees, and based on that, we save money on reduced resources.
What needs improvement?
IBM App Connect provides many features, but there are several areas for improvement. Better debugging and observability would help us track any single transaction end-to-end across steps and connectors. Features such as a step-by-step line view and one-click download for flow execution would be beneficial. Improved CI/CD pipeline and GitOps experience would be valuable. The team wants flows as code and predictable promotion across development, test, and production environments. Stronger native Git integration, export-import functionalities, and first-class pipeline templates like Jenkins, GitHub, and Azure DevOps would be beneficial. More cloud-native, lightweight runtime options would be very helpful. Connector reliability and consistency need improvement because some connectors feel more mature than others, and version changes can break mapping. Pricing and licensing clarity is important because the licensing is complex and can slow down adoption and planning.
Some improvement areas include handling very complex structures that the platform currently does not support. Improvements on the DevOps side, particularly providing templates, would be beneficial. The platform is somewhat expensive and hard to predict in terms of cost. Debugging features need to be provided. For CI/CD, the flows are not truly accurate and need improvement.
For how long have I used the solution?
I have used IBM App Connect since 2021, when I was at my previous company.
What do I think about the stability of the solution?
IBM App Connect is stable.
What do I think about the scalability of the solution?
IBM App Connect is very scalable and a flexible tool. We can easily scale between any connector or anything.
How are customer service and support?
The customer support is available 24/7. Anytime we need any help, support is accessible.
How would you rate customer service and support?
Negative
Which solution did I use previously and why did I switch?
Before IBM App Connect, I used a few solutions, including custom point-to-point integration. There were problems with tight coupling, central bottlenecks everywhere, and long release cycles. IBM App Connect overcomes these issues.
How was the initial setup?
The pricing is somewhat high. The setup looks very simple, but the licensing takes more time to obtain.
What was our ROI?
IBM App Connect's low-code approach allows us to reduce the time required from our resources. We can even reduce the number of resources because integration doesn't require heavy coding, saving both time and money.
IBM App Connect definitely saves significant time, approximately 50 to 60%. Based on the time savings, we can reduce the number of employees needed. For resource utilization, we can use fewer resources. With the time saved, we need fewer employees, and based on that, we save money on reduced resources.
What other advice do I have?
We are using the private cloud deployment on AWS. My company purchased IBM App Connect through the AWS Marketplace. IBM App Connect is a very user-friendly tool, and we can very easily integrate with other applications. I would definitely recommend it. The overall review rating for IBM App Connect is 7.5 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Decade-Long Perspective: The evolution and modernization of IBM ACE
Moving away from the heavy, centralized architecture of "brokers and execution groups," IBM completely re-architected the platform around lightweight, independent "integration servers." This fundamental shift is arguably the most significant upgrade for me.
Review of IBM ACE
Over the years ACE keeps getting better and more exciting to use!
Streamlined our integrations with zero hassle - IBM App Connect is a true enabler
10+ years ACE experience and still enjoying the product
Easy to use and understand
Cloud migration and versatile features facilitate seamless application integration
What is our primary use case?
I have been using IBM App Connect for application integration.
What is most valuable?
The features I find most valuable are message routing, message transformation, and protocol translation. IBM App Connect is a market leader and has been migrated to the cloud, allowing it to run efficiently in that environment.
What needs improvement?
I don't see any necessary improvements as IBM App Connect has been a market leader for many years. I find it particularly good for on-premises and now cloud use. Any major improvements have been addressed with App Connect Enterprise. Perhaps more tutorials for the training of new people who want to learn IBM App Connect would be beneficial.
For how long have I used the solution?
I have been working with IBM App Connect for eleven years.
What do I think about the stability of the solution?
I would rate the stability of IBM App Connect as nine out of ten.
What do I think about the scalability of the solution?
I would rate the scalability of IBM App Connect as nine out of ten. It has options to scale up integrations as required, especially when the traffic to the application is higher.
How are customer service and support?
The technical support from IBM is good. I have worked with the IBM team on several products, and overall, it is satisfactory.
How was the initial setup?
The initial setup of IBM App Connect is not tough. It's relatively easy and just requires installing the software.
Which other solutions did I evaluate?
Competitors to IBM App Connect include MuleSoft. However, I have never worked on Mule ESB, so I can't offer a comparison.
What other advice do I have?
I recommend IBM App Connect Enterprise to everyone. It is suitable for all company sizes, from small domestic banks to large corporations in various industries such as banking, insurance, and airlines. I would rate the overall solution as eight or nine.
Transforms data efficiently and navigates licensing challenges with ease
What is our primary use case?
I am a developer specializing in IBM App Connect. We have a customer interested in comparing ESB tools, such as webMethods, which was previously owned by Software AG company before IBM acquired the product.
We work with the on-premises version because in Turkiye, our customers cannot use cloud platforms due to data privacy policies. They must use on-premises solutions.
We primarily work with banking and insurance company solutions. At the bank where I work, our company provides support to other companies. Their developers are not highly experienced, so they contact our company for assistance. We help with direct connection to their services and solve problems when IBM App Connect encounters issues.
What is most valuable?
The transformation capabilities in IBM App Connect are particularly beneficial. When consuming SAP data, converting data fields is straightforward. File operations are simple to execute, and converting between XML to JSON formats is effortless with IBM App Connect.
The mapping node functionality for data transformation enhances the integration workflow significantly. Users can utilize mapping nodes or SQL, though the mapping node provides a more streamlined approach for transformations. Additionally, containerizing applications is very straightforward with this solution.
What needs improvement?
The transition between version 12 and version 13 presents some challenges. While version 12 had approximately 10 features, version 13 includes around 200 features with cloud platform compatibility. The learning curve for developers moving from version 12 to 13 could be smoother.
When using new components, better context explanations would be beneficial. In version 13, accessing new features requires connecting through a web browser, which can be challenging to understand. The explanation of new features could be more user-friendly.
For how long have I used the solution?
I have been using IBM App Connect for nearly five years.
What was my experience with deployment of the solution?
The deployment process is straightforward, but there is one significant challenge: the license cost is very expensive compared to other tools.
What do I think about the stability of the solution?
Configuration time varies depending on the implementation. For insurance companies requiring JDBC connections, the setup is relatively simple when deploying bar files to the server. However, some companies require multiple configurations, including ODBC connections, JDBC connections, different BI databases, main databases, and replication servers. IBM App Connect occasionally crashes for various reasons, requiring problem-solving intervention.
What do I think about the scalability of the solution?
IBM App Connect demonstrates good scalability. With version 11, services can be developed and prepared as Docker zip files for use with Kubernetes platform. The product, formerly known as Integration bus, evolved through versions 10, 11, 12, and 13 to become IBM App Connect Enterprise.
How are customer service and support?
Global IBM support is excellent. When we encounter problems in Turkiye with banking customers, the local IBM partner sometimes struggles to resolve issues. However, when opening a ticket with the global team, problems are resolved promptly and effectively.
The official IBM support in Turkiye, while functional, is not as experienced as the global team in problem-solving capabilities.
Which solution did I use previously and why did I switch?
I have compared IBM App Connect to webMethods. The system occasionally crashes for various reasons, requiring resolution.
How was the initial setup?
The basic installation process takes approximately 5 minutes, involving a download and setup wizard. However, additional configuration time is required for implementing IBM MQ, ODBC, JDBC, and other tools. The complete setup process, including all configurations, typically takes around two weeks.
What about the implementation team?
We provide integration services to other companies, particularly in the banking and insurance sectors. These companies often require assistance with deploying and configuring IBM App Connect due to their lack of expertise. We support them by addressing issues and facilitating direct connections to their services.
Moreover, in cases involving IBM App Connect crashes or technical challenges, I liaise with the global IBM support for effective solutions, as local support in Turkiye occasionally lacks the necessary experience. Our team serves as a reliable resource, sharing expertise to enhance their capabilities and ensure smooth operations with IBM App Connect.
What was our ROI?
The system has demonstrated its value by efficiently handling the transfer of services to ESB IBM App Connect, managing large service volumes effectively.
What's my experience with pricing, setup cost, and licensing?
Configuration time varies by implementation. For insurance companies with simple JDBC connections, the process is straightforward. However, companies requiring multiple configurations for ODBC, JDBC connections, BI databases, main databases, and replication servers require more extensive setup time. The exact duration depends on specific requirements and cannot be precisely specified.
Which other solutions did I evaluate?
As an IBM App Connect developer, we have customers interested in comparing other ESB tools, particularly webMethods, which was previously owned by Software AG company before IBM acquired the product.
What other advice do I have?
The global technical support rates a nine out of ten, while the Turkiye support receives a seven out of ten. The product itself is good, rating an eight out of ten for pricing, though this is influenced by country-specific exchange rates. Overall, I would rate IBM App Connect as nine out of ten.