Managing Artifacts

This section describes how to manage artifacts, including how to add and remove them from a BizTalk application and how to configure their properties.

Artifacts are the items contained in a BizTalk application that are required for it to run. For background information about how artifacts are used in a BizTalk application, see What Is a BizTalk Application? For background information about artifacts, see Runtime Architecture. For information about how you manipulate artifacts when you create and modify a BizTalk application, see Creating and Modifying BizTalk Applications.

Tracking artifacts

A big part of managing the artifacts you create is tracking. You can configure various tracking options during run time for orchestrations, send ports, receive ports, and pipelines using the BizTalk Server Administration console. You can change the tracking options for an item at any time, without interrupting the business process.

The tracking configuration settings allow you to track the following types of data:

  • Inbound and/or outbound event data. For example, message ID, start and stop times for the artifact.

  • Inbound and/or outbound message properties. For example, general and promoted properties for each message that the artifact processes.

  • Inbound and/or outbound message bodies and parts. For example, body and parts for each message that the artifact processes.

  • Orchestrations. Execution data for orchestration shapes.

Viewing Tracked Message and Instance Data provides some good info.


If you set tracking options on a pipeline, then the tracking options are set globally for every port that uses the pipeline. This results in far more data being tracked than you may intend, and may impact system performance. During development, this may be normal. In production scenarios, we recommend you enable any tracking options on the send ports and receive ports, instead of the pipelines.

In this section