SQL Servers

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 trying 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 SQL servers directly from the BizTalk360 user interface.

Follow the below steps to view the BizTalk Server information in BizTalk360:

• Log in to the BizTalk360 application
• Select an environment name on the landing page
• Click to expand the Manage Infrastructure option and select the SQL Servers.
• Add the SQL server type to perform operations.

Once after adding the SQL server user can view the Server details and Nt services. The SQL Server page displays the below information:

1. Memory - This section provides information about the SQL Server RAM memory
2. CPU - CPU usage information is displayed in this section
3. Windows edition - This section provides information about the Windows edition installed on the server
4. Hardware - Hardware details of the server is displayed in this section

By clicking the arrow in the upper-right corner of the server tile, more information about the server can be viewed. For an example, see the below screenshot.

By clicking on the NT Service tab in BizTalk360, users can manage NT services across standalone servers, clustered servers, and Always On Availability Group (AG) configurations.

• Standalone server - In a standalone, when the SQL Server is reachable, all NT services associated with the BizTalk environment are listed, allowing users to view their status and perform operations such as start, stop, and restart directly from the BizTalk360. However, if the SQL Server becomes unreachable, BizTalk360 cannot retrieve or display the NT services, preventing users from viewing their status or managing them through the application. 
• Clustered SQL Server -, BizTalk360 connects to the active SQL node to retrieve and display NT services associated with the BizTalk environment. Users can monitor their status in real-time and perform operations such as start, stop, or restart directly from the application. BizTalk360 continuously communicates with the active node to ensure smooth monitoring and management. When a SQL Server failover occurs, the passive node takes over as the active node, and BizTalk360 automatically detects this switch. It then re-establishes the connection to the new active node, ensuring uninterrupted access to NT services and maintaining operational continuity.   
• when the Cluster SQL server is completely un-reachable then couldn't able to retrive the NT services and user cannot view or manage them.

• Always-On Availability Group lists all available nodes within the group, enabling users to monitor and manage NT services across each node. A Primary Group indication clearly identifies the current primary replica, ensuring users know which node is actively handling operations. The primary replica allows BizTalk360 to continuously retrieve and sync NT service statuses, providing real-time monitoring and management capabilities. Users can start, stop, and restart NT services on any node. During a failover, if the primary replica fails, the secondary replica automatically takes over, and BizTalk360 seamlessly reconnects without requiring user intervention.