When you start developing with the ESB Toolkit it can be difficult to debug an error in an itinerary. When an exception occurs, you can see the error in the Event Viewer, in the BizTalk Administration Console (if you don't use the ESB Exception Management Framework) ore in the Management Portal but sometimes this information is not enough because you want to see which steps are already done in the itinerary and want to trace exactly when and where the error occurs.
Fortunately you can enable tracing in the ESB Toolkit and trace the steps inside the Itinerary.

The following information can be traced in the ESB Toolkit:

  • If the Itinerary could be resolved
  • Which Itineray is attached to the message
  • What the Document Message Type is
  • If a Resolver or Adapter Provider is stored in the Cache
  • Activities inside an Itinerary Service
    • Initializing
    • Resolver information
    • Adapter information
      • Endpoint information

 

Use a tool like DebugView to see the trace output. DebugView is an application that lets you monitor debug output on your local system, or any computer on the network that you can reach via TCP/IP.

DebugView

 

How to configure diagnostics and trace information

To enable the Microsoft BizTalk ESB Toolkit trace switch, add the following <switches> element to the system.diagnostics section of the machine.config file.

<system.diagnostics>
      <switches>
          <add name="BizTalkESBToolkit" value="4"/>
      </switches>
 </system.diagnostics>

Note
In every version of the ESB Toolkit is the switch name a little different. In previous versions it was "BizTalkESBToolkit" with the version number appended to it but in BizTalk 2013 it is only "BizTalkESBToolkit". Unfortunately, the documentation of the ESB Toolkit is not updated every version so beware that if you copy and paste the switches element from the documentation you have to change the switch name.

 

See Also

For more information on configuring diagnostics and trace information see: