Microsoft BizTalk

Biztalk is best suited for use in hospitals that have multiple systems such as an EMR like Meditech and Computation for the kitchen software that handles patient data. Biztalk is not suited for environments with just one EMR system and no downstream software systems.

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.

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.

Great for moving data into Dynamics from multiple systems. If you don't have the staff it is difficult and time consuming to implement. Since implementing our failures have decreased dramatically and we have gotten positive feedback from end users.

BizTalk fits perfectly in our environment. While the quantity of work is rising, the tech-department is not growing :(

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.