- 4 minutes to read

Managing Tracking for Microsoft BizTalk Server

Info

Nodinite replaces BAM! With Nodinite, it is also dead easy to review and change all tracking related settings for your BizTalk Server environment! Since you are reading this page, you may also be interested in the Nodinite BizTalk Server Logging Agent user guide.

The BizTalk Server Monitoring Agent for Nodinite has built-in support for remotely managing Tracking Settings for Ports, Pipelines and Orchestrations. This feature gives you both an overview as well as easier administration that saves your time (and thereby money).

Since the number of artifacts can grow rather large (many thousands are common) we have grouped the different artifacts by the following Tracking related Categories:

Category Comment
Receive Ports (One-Way) Messages are received by one or more Receive Locations, tracking settings are managed on port level
Receive Ports (Request/Response) Messages are received by one or more Receive Locations, tracking settings are managed on port level
Send Ports (One-Way)
Send Ports (Solicit/Response)
Orchestrations
Pipelines Make sure to follow our very recommended 'Recommended tracking settings for default pipelines' user guide

Tracking Resources
Example list of Tracking Resources as filtered in a Monitor View

By using the Nodinite Tracking feature there is NO need to log on to any of the BizTalk Server nodes or use the BizTak Server Management Console (also requiring membership in either the BizTalk Administrators group and/or BizTalk Server Operators). E.g. A non BizTalk Administrator may change these settings remotely simply using the Nodinite Web Client.

Tip

Using Nodinite means all actions are log audited

Features

The following features exist for the Tracking feature:


What remote Actions can I perform

Since the different tracking-related artifacts in Microsoft BizTalk Server have different properties you will have different options in the different administrative pages depending on the Resource (Receive Ports, Send port, ...). All Resources of the Category Tracking has the following Action(s):

  • List - Open a specific administrative page with additional lists and options

Remote Actions
Here's an example of Remote Actions for the Tracking category

Additional Actions within the administrative pages

Within the administrative pages, you can perform the following actions:

  • Reload - Reloads the page (discarding pending changes and refresh content)
  • Save - Persists pending changes
  • Show Applications - When checked the artifacts are grouped by BizTalk Application name

Reload

Click the Reload button to refresh settings from BizTalk.
Reload button

Note

Pending Changes will be lost.

Save

Save pending changes to BizTalk and reload the modal.
Save button to persist new configuration

Show Applications

When checked, the artifacts are grouped by BizTalk Application name otherwise list by artifact name:
ShowApplications

Example 1: Send Ports grouped by BizTalk Application Example 2: Send Ports grouped by name

Receive Ports (One-Way)

Manage tracking settings for Receive Ports (One-Way):
ReceivePorts
Example image for Receive Ports (One-Way)

Receive Ports (Request/Response)

Manage tracking settings for Receive Ports (Request/Response).
Example image for Receive Ports (Request Response)

Send Ports (One-Way)

Manage tracking settings for Send Ports (One-Way).
SendPorts
Example image for Send Ports (One-Way)

Send Ports (Solicit/Response)

Manage tracking settings for Send Ports (Solicit/Response).
Send Ports Solicit Response

Orchestrations

Manage tracking settings for Orchestrations.
Remote Actions
Example image for Orchestrations

Tip

We recommend that you disable all tracking options for Orchestrations at all times with the only exception of short-term debugging sessions.

Large dta_DebugTrace table

Enabling Orchestration logging may yield a large amount of data in the dta_DebugTrace table. The DTA Purge and Archive (BizTalkDTADb) SQL Agent job removes data according to its settings.

You can truncate this table if you want to instantly remove all records. TRUNCATE TABLE dta_DebugTrace. The truncate operation is not logged by SQL Server so you need to know what you are doing.

Pipelines

Manage tracking settings for Pipelines.

You can override port settings by configuring tracking on the pipeline level. This is something we at Nodinite discourage you from doing.
All Pipelines

Note

Make sure to review the 'Recommended tracking settings for default pipelines' user guide

Tip

Make sure to let the ports decide what to track and what not to. Review our 'Recommended tracking settings for default pipelines' user guide

Metrics chart: Metrics

Not yet implemented, please send a feature request if you need this feature detailing what you would like to see.


Next Step

Add or manage a Monitoring Agent Configuration
Recommended tracking settings for default pipelines
Configuration

Administration
Monitoring Agents
Monitor Views