Skip to main content
TrustRadius
Microsoft BizTalk

Microsoft BizTalk

Overview

Recent Reviews

BizTalk Saves the Day

8 out of 10
July 13, 2018
Incentivized
BizTalk is being used to move data between different systems of our company. Prior to BizTalk our old system were very unreliable but …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing
N/A
Unavailable

Sorry, this product's description is unavailable

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

6 people also want pricing

Alternatives Pricing

What is elastic.io Integration Platform?

The elastic.io Integration Platform is a hybrid integration system that users can deploy on-premise or in the cloud. It is highly scalable, with over 100 prebuilt application connectors for out-of-the-box use and a flexible data structure.

What is Cin7?

Cin7, headqduartered in Auckland, aims to make complex retail and wholesale simple with all-in-one cloud inventory, POS, EDI and 3PL. Cin7 allows users to manage sales channels, inventory, point of sale and supply chain in one central, cloud-based software. Cin7 offers integrations using third…

Return to navigation

Product Demos

BizTalk Server - The Road ahead & What's Next

YouTube

Microsoft BizTalk Server Course Part 1

YouTube
Return to navigation

Product Details

Microsoft BizTalk Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(37)

Attribute Ratings

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Viral Patel | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We were required to develop a synchronizing tool for uploading, downloading and management for a huge set of documents. This synchronization should happen on daily basis. There should not be any downtime. Users should be able to change business rules dynamically. So we did a POC for using Microsoft BizTalk server for message queueing and using business rule engineering for dynamic rule changes.
  • It is very user friendly. Users can change rules during run time and change workflow.
  • Huge capacity for queueing messages. It supports all types of adapters like Oracle, Salesforce, SMTP, FTP, etc. Also users can built custom adaptors.
  • If users want to dynamically deploy their solution without any downtime, this is a perfect solution. BizTalk will be a good fit, especially for public-facing websites.
  • Well-proven in the market. I used it when developing a website for Virgin Trains, catering more than 800K user requests per day.
  • Helps in load balancing.
  • It still could add more cloud features.
  • Need performance improvements.
  • It is expensive. Cost should be reduced.
  • Very few BizTalk experts. Usage is very low.
  • Simplifying the mappers and pipeline configurations.
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.
  • We had a positive impact by using BizTalk Server. We were able to deliver a scalable solution which was a huge challenge to cater more than 800K users with a dynamic application.
  • Users can run the server in clustered mode and increase capacity with much less cost.
  • No need to keep adding web servers. It reduces the need for more web servers.
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 proven in the market compared to TIBCO and Kafka. Feature-wise, BizTalk Server is far ahead compared to other tools.
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.
Kyle Kochtan | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Incentivized
Microsoft BizTalk is being used in a number of places as an integration hub. Years ago it was chosen as the integration hub for the organization. As of late we have started moving some things off of this hub as it no longer meets our needs for an agile development platform.
  • Microsoft BizTalk is extremely powerful
  • Microsoft BizTalk can connect to a number of different enterprise applications
  • Microsoft BizTalk utilities a GUI environment for development
  • Microsoft BizTalk is over engineered for some situtations
  • Microsoft BizTalk can be frustrating to use as it forces you to use the GUI as opposed to code
  • Microsoft BizTalk is very resource intensive to create integrations
Microsoft BizTalk does what it sets out to do and does it very well. However many times the solution is far more complex than it needs to be. This also creates a lot of overhead for development and testing. Deployment is very difficult and requires the server to be recycled thus making all the users not able to use it.
  • Microsoft BizTalk is more of a neutral ground as its [pricey] but it does do what it says
  • Microsoft BizTalk requires a much larger team of developers and server ops to run
  • Microsoft BizTalk can be pricey depending on your agreement
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.
Microsoft BizTalk support is very good as it is a Microsoft product. There are many resources available to find online and 3rd party website that can assist you. In addition to these you can always purchase support from Microsoft either virtually or onsite. The Microsoft support is great but is also very pricey.
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 right choice we go there.
October 10, 2016

Biztalk's to me :)

Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use BizTalk in combination with TOPdesk. Each time a network device enters the network it's checked ito make sure this use is valid. If not: the device is disabled from the network. This is a small example of how easy it is to use BizTalk. If users want to see which hardware is registered to their name they click a button on the intranet page, next BizTalk provides the data for the answer.
  • The frequently used capabilities are very strong. It's quite simple to create basic tasks or connections to other systems.
  • I would like to see a better error messaging system.
BizTalk fits perfectly in our environment. While the quantity of work is rising, the tech-department is not growing :(
  • There is absolutely a positive impact on our investments.
  • Try not to solve all your issues with BizTalk.
  • Cordis
Cordis is a Dutch product but it is too expensive.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
BizTalk is used as middleware to interface various engineering applications with SAP. It's used primarily by engineering and material governance users. Their applications create materials and bill of materials, and BizTalk interfaces with those applications to create and update those materials and bills of materials in SAP.
  • BizTalk is great at mapping input files to output file (or input schemas to output schemas). It uses a pretty well designed mapping screen, and you drag arrows from one input field to the output field. You can also put all sorts of conditionals on the input to output fields mappings. That lets you change the output value based on more one input value, or if the input value has a certain value, or the absence of a value, you can set the output value to something else.
  • BizTalk is good at connecting to SAP, and allows you to download SAP Idoc schemas to use in Orchestrations which allow you to send and receive SAP Idocs.
  • BizTalk is pretty good at notifying you with email. In particular, you can have your Orchestrations send email based on a status. You can send email at the beginning, middle and end if you so desire. That is particularly useful developing and debugging orchestrations.
  • 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.
BizTalk is well suited as middleware. Where you wish to translate an input file into an output file and send it to some endpoint. In our case, we used it to convert and send files to SAP. In many ways, it very flexible, and you can do almost anything you want with it. In many ways, it's a better solution than your SAP XI or PI as middleware, since it's much less expensive, and allows you do interface with non-SAP systems.
  • A positive impact has been the quicker turnaround time of a part request and that part showing up in SAP using Biztalk as middleware.
  • A somewhat negative impact has been the somewhat insufficient error logging/message capture settings that Biztalk provide. This has caused occasional delays when attempted to create parts for the business.
  • A somewhat negative impact has been the need to have a specialized developer who understands Biztalk to troubleshoot issues with the Biztalk and SAP interaction when creating parts, and when adding new fields to the parts.
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.
Visual Studio.NET, Microsoft IIS
Score 7 out of 10
Vetted Review
Verified User
Incentivized

Microsoft BizTalk is used in my organization as an integration tool across the whole organization to connect different LOB (line of business) applications, like CRM (customer relationship management) application, billing application, campaign management application and transaction management application.

The main purpose of using the tool here is to play the message broker role and let different systems exchange data in a real time manner.

  • 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 mainly used in a publish-subscribe pattern, it has toolkits from ESB (Enterprise Services Bus), but it's not as good as other native ESB systems.
  • BizTalk didn't provide many native adapters and it needs to be made by a developer or bought from a third party, like Amazon S3 adapter or SMS adapter.
  • BizTalk only supports JSON in the latest version 2013 R2, and it needs to transform JSON to XML for internal mail box use and then transform from XML back to JSON.

Microsoft BizTalk is good to use as a message broker tool to process long run business process across multiple applications, but may not be very good when the requirement is for a heavy real-time message queue or topic process or to distribute across multiple applications.

BizTalk is easy to integrate with .net family applications, but it may take more time for it to be integrated with other family applications like Java.

  • If the Microsoft SQL Server database is used as well as other Microsoft applications, then BizTalk will be a good tool to add.
  • Many .NET developers are available in the market if there is a requirement to use it to develop a BizTalk Server rapidly.
  • If the organization is focused on open source tools or Java family, BizTalk may be not a good choice.
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 with other .NET application monitoring jobs.
Return to navigation