IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.
N/A
Microsoft BizTalk
Score 6.3 out of 10
N/A
N/A
N/A
Pricing
IBM App Connect
Microsoft BizTalk Server
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM App Connect
Microsoft BizTalk
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM App Connect
Microsoft BizTalk Server
Considered Both Products
IBM App Connect
Verified User
Anonymous
Chose IBM App Connect
IBM App Connect started as MQSeries Integrator (MQSI) more than 20 years ago. In the IT environment, this is like an eternity. And this allowed a lot of customer experience and needs to be embedded in the product. Without it becoming a legacy application. The changes done in …
I used the IBM WebSphere DataStage tool which is an ETL tool where we extract transform and load. This tool is a little tougher to understand than App Connect. For example, to build a job in App Connect is easier than DataStage. We can schedule the job to run in the same …
IBM API Connect is positioned ahead of Apigee in the Gartner report. But in my opinion the development experience and the data transformation capability is way better in Apigee and it’s a proved solution and has a huge client list. (I have worked on an American Express …
We did not select Cast Iron as our iPaaS solution, it was the weakest competitor in the field that we evaluated. Our experience was that it was not nearly as easy to learn, without in-depth training and guidance, and the developer UI was extremely buggy. We subjected each of …
WebSphereCast Iron is preferred for our sales and delivery teams over Informatica. We find the products and teams for WebSphere Cast Iron easier to work with here and find WebSphere Cast Iron better when integrating with non-Salesforce systems. WebSphere Cast Iron struggles to …
We selected IBM App Connect Enterprise due to our confidence in IBM as a long-term partner and our history with their integration technology (Message Broker/Bus). IBM App Connect provides the robustness and high reliability needed for our core on-premises systems, with proven …
The choice of IBM App Connect was a strategic decision driven by the urgent need for agile, user-friendly, and cost-effective application and data integration. While DataPower, webMethods, and API Connect are powerful tools in their own rights, their primary focuses as security …
We used BizTalk Server as we had all other integrating applications developed on .Net and using Microsoft development environment. Kafka is best if integration is between non-Microsoft applications. We had few adapters developed using Microsoft .Net framework. BizTalk is well …
Microsoft BizTalk was chosen as the integration hub many years ago. It is still in use in a number of places in the organization however we are no longer developing specifically for this product in mind. We now develop in a number of places and if Microsoft BizTalk is the …
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution …
BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize …
IBM App Connect is well-suited to serve as a central integration hub, particularly for scenarios involving data transformation, complex routing logic, and dynamic backend routing. It excels at enabling legacy system modernization and supports real-time, event-driven architectures effectively. However, it is less appropriate for simple point-to-point integrations or for use cases requiring workflow process management and human task orchestration, where BPM or lightweight automation tools may be more suitable.
It is perfectly suited if some heavy operation needs to be automated where jobs can be queued up. Scalable app which is required to develop in a lesser time frame. Good for when users should be able to change rules more frequently without any downtime, like promotions. The server is well proven in the market. BizTalk server is the best fit if all other integration adapters are developed using Microsoft applications and if all applications are meant to be processed on a Windows environment.
BizTalk uses Microsoft Visual Studio as the IDE (integrated development environment) tool, and it's very easy to use.
The orchestration engine of BizTalk addresses resource issue very well for long-running business processes by dehydrating and rehydrating orchestration instances.
BizTalk is very easy to integrate if the development is mainly on the Microsoft software family.
BizTalk needs to be better at tracking down errors after the fact. Input files by default get deleted after processing successfully, unless you specifically specify that they don't. This can be an issue where you need to see what the input file contained, since you may have errors showing up in your target platform, in our case this was SAP.
BizTalk logging needs improved. It needs to be able to log the content of the messages it sends and receives. It would be good if the log had a link to the input and output files.
BizTalk needs to allow a simple way to preserve the input and output files for debugging purposes. A master setting on the orchestration would be helpful for this.
It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.
You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.
Microsoft BizTalk is not an intuitive product. It requires many hours of looking through the settings to achieve what you need. Using 3rd party DLLs is a nightmare as you are forced to register them in the GAC of the server and this process is quite cumbersome just to use a DLL.
BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
We selected IBM App Connect Enterprise due to our confidence in IBM as a long-term partner and our history with their integration technology (Message Broker/Bus). IBM App Connect provides the robustness and high reliability needed for our core on-premises systems, with proven scalability to the cloud. Its key strength is enabling deep integration by combining low-code with the power of complex, custom logic, ensuring the platform's capabilities exactly matched our need to handle complex flows.
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution you wish, whereas Jitterbit is much more limited.