BizTalk 2004 earns a special place in our servces as implementing a BizTalk solution contains elements of all of the other sections.

To implement a BizTalk application a thorough understanding of the architecture into which it will fit is required. One of the key issues is how best to model the boundaries where it interfaces with other systems and processes.

The design of a BizTalk system is fundemental in positioning code in the most suitable place within the myriad alternatives that BizTalk presents. Should a map be places in an orchestration or against a port? Should a piece of processing occur in a pipeline or within an orchestration? Do we need to write a custom pipeline component or can we construct what we need from a combination of the existing pipeline components? Do we need a single large orchestration or a number of smaller ones? There are many alternatives and we can help you decide the best ones for your application.

Writing the code for a BizTalk application can be relatively simple or can be very complex. What if you need to create a custom pipeline component or functoid? Maybe you have a complex piece of logic that needs to be performed within an expression. Maybe, even, you need to create a custom adapter. These can all be non-trivial and we can help you construct well architected and efficient code.

When a BizTalk application doesn't do what you were expecting, finding out exactly what has gone wrong and why can sometimes seem like some kind of arcane art. We can help lift the veil of mystery from debugging a BizTalk application showing you a number of powerful techniques.

We can also supply mentoring for a team writing a BizTalk application helping establish best practice and making sure they become self-sufficient as they become more skilled in BizTalk development.

Copyright © Dotnet Consulting Ltd 2004