A profile is a set of characteristics that define a business-related process. A tracking profile is a file with a .btt extension. It contains the mapping between a specific orchestration and activity definition.
Tracking Profile Editor (TPE) is a graphical user interface to help developers create new tracking profiles or modify existing tracking profiles that map a specific view of internal business processes, as well as associated data, to an orchestration.
When you create a tracking profile using the TPE, you access the following files:
- A deployed assembly stored in the BizTalk Configuration database that contains one or more orchestrations.
- An XML-based activity definition file generated by the business analyst using the BAM Activity Wizard within the BAM Excel workbook template. It defines what activity and event data you need to collect independently from any orchestration.
You cannot use the Tracking Profile Editor to view the schema associated with a shape that has a message of type System.XML.XMLDocument, since there is no schema available for this type at design time.
You define the data extraction from an orchestration by dropping items from the message schemas and orchestration shapes into business milestone (event) and data item folders. Although each pane or view and each folder in the TPE has a unique function, all the views and folders have similar navigational features to help you find and manipulate information. This topic describes the layout of the TPE and the purpose of various views and folders.
Note TPE only supports messages that have schemas. If you have a message of type String (not a schema-based message), then you cannot track it from the TPE.
This section contains: