Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m trying to find out if it’s simple / easy to create a Biztalk adapter for an arbitrary XML source, (ie. not a WSDL/SOAP/RPC etc.)
Are there any factors that will make this simpler, for example, DTD/XSD for the XML service.
Ideally, I’d like to be able to route the consumed data to a MSSQL database, and I’d like to know how much Biztalk is likely to simplify this process, vs, consuming the XML via a custom C#/.Net solution.
Sorry if the question is vague, but I’m inexperienced with BizTalk.
The main benefit you will get from BizTalk is the platform for reliability of message processing and tracking. Another point is message routing: As soon as you want to deliver your data to more than one endpoint you will begin to gain over a custom C#/.Net solution.
The most common use case would be a Publish-Subscribe scenario where BizTalk separates “upstream” and “downstream” systems.
Furthermore BizTalk is a good place to handle specific business rules around your data streams (hence the “Biz”).
If however your goal is a mere transforming data pump into a database BizTalk would be an expensive overhead.
As specific to your central question “Is it simple to create a BizTalk adapter?” the answer is definitly “yes”. Developing, deploying and running BizTalk applications is pretty straightforward … today. Versions prior to BizTalk 2009 did show their lack of a seamless integration into the MS stack. Compared to products like Exchange or SQL Server 2008, BizTalk 2009 is still a step behind – for example PowerShell is not integrated like in these other products.
A well defined DTD/XSD for the messages you are going to exchange with your source and target systems is big plus because it enables you to track and monitor message variables.