Configuration of the BizTalk Server Log Agent
Enable centralized logging from all your BizTalk Server groups (even from different BizTalk Server versions)
The Nodinite BizTalk Server Logging Agent has support for logging from one or more BizTalk Server Groups like PROD and TEST (or from 2 or more PROD groups and so on).
Each BizTalk Server group is managed by a unique Log Agent Instance with the following properties:
- Name - the user-friendly name of the Log Agent (Mandatory)
- Log Agent Value Id - The unique id for the Log Agent (Mandatory)
Note
You should never change the id once set since this may seriously disrupt log view settings and more
Description - the user-friendly description of the Log Agent (Optional)
Web Site - A link to an external web site with additional information about the Log Agent (optional)
For each BizTalk Server group, information about the Configuration (BizTalkMgmtDB) database and the Tracking (BizTalkDTADb) database must be configured. Nodinite uses Linked Servers and the SQL instance with the Configuration Database must have a configuration for the BizTalk Management (BizTalkMGMTDb) and tracking database (BizTalkDTADb).
SQL Server Connection details are listed in the BizTalk databases tab, example image below:
Important
You must restart the Logging Service if you change this configuration
The amount of events and messages being transferred on each run and the polling interval is displayed in the Tracking tab, example image below:
Ports are automatically being synchronized as Endpoints, the interval is displayed in the Endpoints tab, example image below:
Log Status Codes
Error codes from any Integration Broker is unique and with Nodinite you can add user-friendly descriptions for these. Each Log Agent has its own unique set of Log Status Codes.
The list of Log Status Codes are listed in the Log Status Codes section:
