Knowledge Base

Profiling BizTalk applications

Category: How do I?
Date: 17 Jun 2009
Product: ANTS Profiler
Versions: 2,3,4
Platforms: BizTalk server 2006 R2

ANTS Profiler does not specifically offer an option to profile managed .NET code on a BizTalk server. How is it possible to profile components written for BizTalk?

BizTalk is implemented as a series of Windows services, therefore the proper option to choose for profiling a BizTalk component would be to use the ".NET Windows Service" option of ANTS Profiler. Because the BizTalk service is not pure managed .NET code, however, it may be necessary to manually enter the name of the service in the ".NET Windows service" textbox of the ANTS Profiler wizard.

To determine the name of the service to type into the ".NET Windows service" box, open the Services snap-in from the Windows Control Panel's Administrative Tools and locate the BizTalk service for the proper BizTalk group. Access the properties of this service and note the "Service name". This is the name that should be given to ANTS Profiler. Typically, the service name will be BTSSvc$BizTalkServerApplication. Once the service name has been entered, finish the ANTS Profiler wizard. ANTS Profiler will warn that the service is not managed code, however, because managed-code BizTalk components will execute in this process, managed code will be run and results should be obtained by ANTS Profiler.