- 3 minutes to read

Configure Microsoft BizTalk Server Logging Agent

With Nodinite, you can replace BAM. Enable logging from multiple concurrent BizTalk Server groups (even running in different versions) to get centralized Logging.

Add or remove logging for your BizTalk Server environments (for example, the old BizTalk and the new BizTalk)

Prerequisites

Before configuring the Microsoft BizTalk Server Logging Agent, ensure all the BizTalk logging Prerequisites are satisfied.

Configuration

Follow the steps below to manage logging from one or more BizTalk Server Groups.

First, select an environment to manage using the Nodinite Update tool:
Manage BizTalk Log Agents
Example with the manage BizTalk Log Agents button.

Click the Add Log Agent Configuration button to add the new Microsoft BizTalk Server Logging Agent.
AddBizTalkLogAgentButton

Log Agent Configuration

  1. Name - Give the Log Agent a user-friendly name (TIP: Include the name and version of the target environment, for example, BizTalk 2016 PROD)
  2. Log Agent Value Id - A unique ID for this Log Agent Configuration. This value should never change once set!
  3. Description - A user-friendly description of this Log Agent Configuration
  4. Log Agent - BizTalk settings - Check to mark this Log Agent Configuration as a BizTalk on-premise Log Agent Configuration

LogAgentSourcePart1

BizTalk Databases

  1. BizTalkMgmtDb Server - Enter the name of the SQL instance hosting the BizTalk management database (this is the linked server information from the Nodinite SQL instance against the BizTalk SQL Instance)
  2. BizTalkMgmtDb Name - Enter the name of the BizTalk management database
  3. BizTalkDTADb Server - Enter the name of the SQL instance hosting the BizTalk tracking database (this is the linked server information from the Nodinite SQL instance against the BizTalk SQL Instance)
  4. BizTalkDTADb Name - Enter the name of the BizTalk tracking database

LogAgentSourcePart2

Tracking

  1. Polling Interval - Set the polling interval for the Logging Service. This value is the time between attempts to ask for new logged data. The default is 30 seconds.
  2. Max number of Events to copy - Set the maximum number of events to fetch on each run. A large number may impact performance. The default is 5000.
  3. Max number of Message/Context data rows to copy - Set the maximum number of payloads and context rows to fetch on each run. The default is 500.

LogAgentSourcePart3

EndPoints

Nodinite, if the feature is enabled, synchronizes all ports in BizTalk as Endpoints available within the Repository Model model.
Sync End Points Polling Interval - Set the poll period in seconds between synchronisation attempts.
Include Endpoints Tracking status - Check this option if you use Microsoft BizTalk Server.

LogAgentSourcpoePart4

Remove

You can remove the Nodinite BizTalk Server Log Agent (configuration) by clicking the Remove BizTalk Logging button.

Save

Click the Save button to save changes to the configuration.

NOTE: You must restart the Nodinite Logging Service after making changes.

Next Step

Replace BAM with Nodinite
Add or manage Log Agents
Administer Nodinite
Install the Nodinite Install and Update Tool

BizTalk Prerequisites
Logging Service
Endpoints
Repository Model