Share your experience using BizTalk Server

The primary use cases for BizTalk Server involve logistic warehouse management for one of the business units.

Boomi has advantages over BizTalk Server because it is more flexible, low-code, no-code, easy to implement, and has a fast go-to-market. The dependencies with other applications are low, and a lot of connectors and adapters are easily available. We are also evaluating Workato, but it has some gaps we are trying to negotiate with the OEM.

Currently, I am working mostly with WebMethods and BizTalk Server.

I am generally satisfied with BizTalk Server, but there are some gaps, as we have multiple integration tools. Thus, there is associated cost, operation cost, license cost, and CapEx, so we are trying to consolidate all the integration tools.

Regarding BizTalk Server and data mapping tools, we want to get rid of BizTalk Server, as there is unnecessary license cost, and there are some limitations, so we might go for Azure Integration Services.

BizTalk Server is completely ruled out; we will not be proceeding with it. We initially planned to move to Azure Integration Services, but there are challenges with AIS, so now we are evaluating WebMethods IO because WebMethods is now part of IBM, which is performing well in the market, although the IBM license cost is too high.

The initial investment is too high, and we want to reduce that cost.

I have used Boomi for probably two years of my complete career, and I have been using WebMethods for the last five or six years.

My last experience with Boomi was two to three years ago.

I have worked with BizTalk Server almost 10 to 15 years back, and now again for the last two years, I am working with BizTalk Server.

There is a strong push from the business to minimize the go-to-market time for customer onboarding and to expand both vertically and horizontally quickly, as we are evaluating multiple scenarios.

It is time for low-code, no-code, and a quick go-to-market should be faster. I want customer onboarding to be fast, and we require a skilled developer.

BizTalk Server's ROI is comparatively higher than Boomi and Workato, and we are currently discussing whether we will go for BizTalk Server, Boomi, or Workato.

We are evaluating Workato or Boomi now.

We might go for Azure Integration Services if we have to go for BizTalk Server.

We are now evaluating WebMethods IO because WebMethods is now part of IBM, which is performing well in the market.

I have not worked with Amazon API Gateway or Mule ESB; I am just testing them.

I am using Boomi iPaaS and WebMethods.

I did not purchase it on AWS Marketplace; those are product API systems, and in my current organization, we currently have WebMethods in our on-prem environment, and Boomi is again on AWS with an instance installed.

I am using Boomi in my previous organization, not my current one.

I did not buy it on AWS Marketplace; we directly approached the product vendor, OEM, took the license, and started using it.

I would rate BizTalk Server a five out of ten due to pricing, flexibility, and the lot of coding required.

I am not a partner of Microsoft; I am just a service provider to my business team, serving as a technical delivery manager, providing integration services.

Our usual use cases for BizTalk Server include mobile app integration with BizTalk Server, website integration with BizTalk Server, and other applications because we are from a utility company.

I utilize BizTalk Server's protocol and JDBC adapters for integrating legacy systems and modern cloud services. BizTalk Server doesn't have many cloud adapters, but IBM WebMethods has numerous adapters, such as Salesforce connector and Talend connector. This is why we are working on IBM WebMethods.

I have employed BizTalk Server's business rule engine in my operations. This feature has helped us make real-time data-driven decisions.

The BizTalk Server business rule engine was very useful for us and has helped us for the last 12 years. I definitely find the business rule engine a feature that is remotely useful.

Biztalk server doesn't have API management so that our exposed can be protected against the SQL injection, DOS attacks. However, this is available in IBM WebMethods.

The positive impact of BizTalk Server was initially limited because of scalability issues. That is the reason why management has decided to implement IBM WebMethods. We are going to decommission BizTalk Server next year.

I believe the API response could be improved in BizTalk Server. We need to increase the number of servers in BizTalk Server. We used to have two servers; later on, we increased to a third server, which has improved performance. We can make it more highly available and scale out to improve BizTalk Server. Scale out means we can increase the number of servers horizontally.

I have been working with BizTalk Server for more than 12 years.

BizTalk Server is good for small companies but not for big companies.

BizTalk Server is stable right now, however, we are working to migrate Biztalk services to IBM WebMethods platform.

We are currently using BizTalk Server on-premises.

We have not done any automation. For orchestration, we have accomplished many things. It is a good product, but we are moving to a new platform because it is an on-premise solution. We are moving to a hybrid integration cloud-based solution.

The first year for BizTalk Server is expensive. After renewal, it becomes 20%, making it cheaper.

Good

Neutral

I have experience with solutions, specifically using IBM WebMethods. At the moment, I'm happy with IBM WebMethods including API management, developer portal, Terracotta, Universal messaging server.

From an integration perspective, I have been working with other technical solutions for the last 12 months and could share my feedback with PeerSpot.

Through vendor. 

We are happy that BizTalk Server has served around 10 years, and that is acceptable. Now the direction is to move away from BizTalk Server to IBM WebMethods, which has more features compared to BizTalk Server. The company's return on investment is acceptable; we are on the positive side, but even then, we are moving away due to new features on IBM webMethods.

Biztalk server on-premise is a perpetual license and IBM WebMethods are subscription based like count of invocation of API calls, Integration calls. IBM WebMethods is expensive due to multiple solution components like API management, developer portal, Terracotta, Universal messaging server. These components provide more security and enhanced performance improvement.

Biztalk server came through bidding process for our utility website development.

We are still working on BizTalk Server. However, our direction is to move away from BizTalk Server.

For BizTalk Server's monitoring and alerting tools, we are using a BizTalk 360 monitoring tool. BizTalk 360 is a product that helps us in getting the insight of API response and number of API calls.

On a scale of one to ten, I rate BizTalk Server a six.