- 3 minutes to read

BizTalk Tab

The BizTalk tab of the Remote Configuration tells the Nodinite Microsoft BizTalk Server Monitoring Agent which BizTalk Server Group to monitor, and which artifacts to leave out.

Animation: the BizTalk tab with Enabled, the connection string, and a new BizTalk Application filter with the expression ^Test
The BizTalk tab: Enabled, the Connection String, then BizTalk Application(s) filter › Add with the expression ^Test. After Save and close, the agent stops monitoring the BizTalk Applications whose name starts with "Test".

Enable monitoring

To enable monitoring, configure the agent with the BizTalk management database connection string for the group you wish to monitor.

  • Connection String — Enter the connection string for the BizTalk management database (typically BizTalkMgmtDb)

The agent connects to BizTalkMgmtDb using Microsoft.Data.SqlClient with modern TLS defaults—older connection strings may need updates when upgrading the agent.

The BizTalk tab with Enabled checked and a BizTalkMgmtDb connection string with Integrated Security and Encrypt=True
The BizTalk tab: Enabled and the BizTalk management database Connection String.

Quick Start Examples

Dev/test with self-signed certificate:

Data Source=localhost;Initial Catalog=BizTalkMgmtDb;Integrated Security=True;Encrypt=True;TrustServerCertificate=True;

Production with trusted CA:

Data Source=SQL01\BIZTALK;Initial Catalog=BizTalkMgmtDb;Integrated Security=True;Encrypt=True;TrustServerCertificate=False;

Tip

Need help with connection strings? See the comprehensive SQL Server Connection Strings guide for:

  • Certificate validation and encryption settings
  • Always On Availability Groups (AOAG) configuration
  • Troubleshooting common errors
  • Security best practices

Important

If you see "The certificate chain was issued by an authority that is not trusted", add TrustServerCertificate=True to your connection string OR install the SQL Server certificate's CA on the agent host. See SQL Server Connection Strings for details.

Connection string reference

Important

Restart the monitoring agent after changing the connection string.

Important

If you run multiple agent instances for a single BizTalk Server Group:

  • Update the connection strings (BizTalk Management Database and Agent Database) in the Settings.json file on all servers
  • The two connection strings have different syntax—BizTalkMgmtDb uses standard SQL connection format, Agent Database uses application-specific format

Always On Availability Groups (AOAG)

When BizTalk Server runs on SQL Server Always On Availability Groups, the agent connects through the AG listener for automatic failover.

AOAG Connection String Example 

Data Source=AG-Listener;Initial Catalog=BizTalkMgmtDb;Integrated Security=True;Encrypt=True;TrustServerCertificate=True;MultiSubnetFailover=True;

Tip

Use MultiSubnetFailover=True for faster failover (2-3s vs 10-20s). See SQL Connection Strings for AOAG configuration details.

Filters

Exclude Applications and Resources by their Name with regular expressions. The tab has two filter lists:

List Matches
BizTalk Application(s) filter BizTalk Application names
BizTalk Resources(s) filter BizTalk artifact names (ports, orchestrations, and other Resources); "Resources(s)" is the product's own spelling

Click Add in a list to add a filter. Each filter has a Filter expression (a RegEx) and an Enabled box; a new filter starts empty and enabled. Clear Enabled to keep a filter without using it. Both lists are empty until you add a filter, so by default the agent monitors everything in the Group.
A BizTalk Application filter with the expression ^Test, enabled
A BizTalk Application(s) filter with the expression ^Test.

^[_].*

This RegEx removes all Resources starting with an underscore (_).

Tip

Test filters individually to avoid accidentally hiding important Resources.

Click Save or Save and close to apply the changes; see Save on the configuration overview.

Next Steps