One of the most common problems that administration teams encounter in a BizTalk environment is while monitoring/diagnosing any issues. If an error or failure happens on different servers, the administration team has to manually log in to each server to view server information or try to find the root cause of the issue. This is a time-consuming process and it poses severe security risks since team members will have full access permissions to log in to the server and perform any operations to fix the issues. BizTalk360 addresses this problem by providing you the capability to access BizTalk and SQL servers directly from the BizTalk360 UI.
The below instructions explain how to access a BizTalk server.
Follow the below steps to view the BizTalk Server information in BizTalk360:
- Log into the BizTalk360 application
- Click on the Environment name on the landing page
- Click to expand the 'Manage Infrastructure' option and select 'BizTalk Servers' link
- The BizTalk Server page displays the below information
- Memory - This section provides information about the BizTalk Server RAM
- CPU - CPU usage information is displayed in this section
- Windows edition - This section provides information about the Windows edition installed on the server
- BizTalk/IIS edition - This section provides information about the BizTalk/IIS edition installed on the server
- Hardware - Hardware details of the server is displayed in this section
- Host Instances - Information about the number of host instances that are started/stopped is displayed here
- Server Usage - Server usage operations are listed in this section
BizTalk Logs
BizTalk server logs play a vital role in auditing and troubleshooting BizTalk server operations. In a production environment, multiple BizTalk servers are responsible for processing critical business transactions and it's your team's responsibility to monitor them for any errors. Instead of switching between various servers, users can conveniently access these logs through the user-friendly interface of BizTalk360.
Within BizTalk360, there is a sub-service known as "Server Logs" responsible for gathering logs from the designated paths.
To set up log configuration, follow these steps:
- Navigate to "Manage Infrastructure"-> "BizTalk Server" and select the respective server.
- Click on "Log Configuration," which opens the configuration panel.
- In the configuration panel, enable the "Logging Status" and specify the log4net directory path for BizTalk log files. you can add multiple file paths here.
- Once logging is enabled, all logs will be displayed, including their log category, file name, and the timestamp of the latest log entry.
- To view a log file in detail, click on the eye icon, which opens the log file details panel. Within this panel, you can:
- Access the complete log information contained in that specific log file.
- Use the "Goto Latest" button to scroll down and highlight the latest log data.
- Download the logs as a file, and you can also email the log file to the respective recipient.
- Enable "Word Wrap" for easier readability.
Logs are scheduled to be purged every 15 days to prevent any performance impact caused by an accumulation of a large number of logs.
With robust filtering capabilities, you can filter logs based on specific criteria, including category name and collection date/time. This functionality enables you to precisely pinpoint and access the logs that are most relevant to your troubleshooting needs.
Server Permissions (BizTalk Servers)
The Server Permissions feature in BizTalk360 provides administrators with a detailed view of each BizTalk Server’s access configuration and permission settings.
It helps validate that all required accounts, permissions, and services are properly configured for smooth BizTalk360 operations.
When you select a BizTalk Server and click Server Permissions, a blade opens displaying information about the server’s logon access, prerequisites, and feature accessibility.
This centralized view simplifies troubleshooting, improves configuration validation, and enhances environment readiness for BizTalk360 monitoring and analytics.
Accessing Server Permissions
- Navigate to Administration → Manage Infrastructure → BizTalk Servers.
- Select a BizTalk Server from the list.
- Click the Server Permissions button to open the permission details blade.
Details Displayed in the Server Permissions Blade
1. Service Logon Access & Permissions
This section shows the access levels and permissions associated with the BizTalk360 Service and IIS AppPool logon accounts.
Item | Description |
Service Logon | The account used by the BizTalk360 Monitoring Service to connect to the BizTalk Server. |
IIS App Pool Logon | The account configured for the BizTalk360 web application’s application pool. |
Local Admin | Indicates if the BizTalk360 service account has local administrator rights on the BizTalk Server. If not, BizTalk360 will check whether the account belongs to other required security groups in Active Directory (AD), such as Distributed COM Users, Performance Log Users, or Performance Monitor Users. |
Distributed COM Users / Performance Log Users / Performance Monitor Users | Verifies whether the service account is part of these system groups to support remote access and performance data collection. |
WMI Namespace Access | Confirms that the BizTalk360 service account has WMI permissions to fetch system and BizTalk-related data. |
Use Case:
This section helps with Permission Validation and Group Access Verification.
You can quickly verify whether the BizTalk360 service and IIS accounts have the required access for BizTalk Server connectivity and confirm if group-level permissions in AD compensate for missing local admin rights. This saves time during configuration checks and minimizes connectivity issues due to insufficient access rights.
2. Pre-requisites
This section validates that essential Windows services and network ports required for BizTalk360 to function correctly are available and running.
Pre-requisite | Description |
MSDTC | Checks if the Microsoft Distributed Transaction Coordinator (MSDTC) service is running for distributed transactions. |
RPC | Verifies the Remote Procedure Call (RPC) service is active and accessible. |
WMI Service | Ensures the Windows Management Instrumentation (WMI) service is running. |
TCP 135 | Validates that TCP port 135 (used by RPC) is open for communication. |
Use Case:
If a BizTalk Server appears not reachable, this section helps identify the cause — such as inactive MSDTC/RPC services, blocked TCP ports, or disabled WMI access.
This assist in Server Reachability Troubleshooting before deeper analysis. This enables quick identification of service or connectivity issues, ensuring your BizTalk environment is ready for monitoring.
3. Feature Accessibility
Displays system-level data collection features and their accessibility via WMI or PerfMon.
Feature | Service Accessibility |
Disks, NT Service, Event Logs Data Collection | Uses WMI to collect information on disks, NT services, and event logs. |
System Resource | Uses WMI and PerfMon to monitor system metrics such as CPU, memory, and disk usage. |
Analytics Data Collection | Relies on PerfMon for collecting BizTalk performance counter data. |
Use Case:
Supports Troubleshooting Data Collection Issues by identifying whether missing permissions or stopped services prevent monitoring or analytics data from being retrieved.
Also helps in Configuration Validation before enabling BizTalk360 features. It improves data collection reliability and ensures accurate performance reporting within BizTalk360.
Notes:
Green Indication – Access, service, or permission is correctly configured and available.
Red Indication – Access, service, or permission is missing, not granted, or the component is not reachable.