Although BizTalk itself enables you to observe which BizTalk artifacts are executing and to review the execution path of an orchestration, it doesn't provide the type of developer-level tracing usually expected to aid with debugging of a solution.
BAM provides highly scalable and high-performing instrumentation for your solution. BAM enables you to record milestones, data, timings, and even messages related to the execution of your business processes. Indeed, it enables you to record any aspect of your entire solution, including .NET components and Web services. See Chapter 6 for more information about how you can use BAM and for an example of a tracking portal, which can provide a friendlier view inside your BizTalk solution.
BAM is ill-suited for developer-level instrumentation, which typically logs information such as method parameters, method timings, and thread identifiers to help developers understand how the solution is executing at a code level. However, BAM can be used for the timing element to enable quick identification of components or methods with long execution times.
In these cases, consider using the much improved .NET 2.0 System.Diagnostics namespace to provide tracing to a variety of listeners, including the debug console, files, and the event log. You can also develop custom listeners with ease. Another option is the Enterprise Library provided by the Patterns and Practices team at Microsoft. The Enterprise Library provides ...