Host Instance category
The Nodinite BizTalk Server Monitoring Agent monitors BizTalk host instances on all servers part of the BizTalk group. New (and/or removed) Hosts and host instances are automatically detected and managed by the monitoring agent.
- Host instances in BizTalk are listed in Nodinite as resources where the name is its Host name and configured server name, for example 'SendHost32@SEBTPRD01'
- Host instances does not belong to any Application at all since these are shared across many BizTalk Server applications
- Host instances are grouped by the following Category Host Instance
- Cluster support - Verifies that your hosts are properly setup for a clustered environment
- Verify Tracking Host configuration - Alerts if there is not at least one dedicated Tracking host
- Host instances exists for host - Alerts if not all host instances are created on each BizTalk Server node
- Running host instances - Alerts if a host instances is stopped (and not configured as disabled and/or part of a cluster configuration)
- Remote Actions - Support the execution of remote actions
- State Evaluation - Monitors and evaluates the run-time state
- Metrics - There is a Widget with information about the BizTalk group available that can be used on the Dashboard
The different evaluated states for any host instance are provided in the table below:
|Unavailable||Resource not available||Evaluation of the 'BizTalk Host Instances' is not possible either due to network or security-related problems||Review prerequisites|
|Error||Stopped and not disabled||A Stopped host instance renders as state 'Error' (if not configured as disabled and/or part of a Windows fail-over cluster resource group)||Start|
|Error||Invalid tracking host configuration||There must be at least one host/host instance configured for Host Tracking per node in the BizTalk group|| Details
A BizTalk administrator must manually create dedicated tracking hosts to resolve this matter
|Warning||Is throttling||Throttling is above configured thresholds. This behaviour is built-in by BizTalk Server design, but may be an indication of exhausted resources, make sure to verify overall performance||Throttling Metrics|
|OK||Enabled and running||Host instance is operational and no other problems were detected||Stop|
TIP: The evaluated state may be reconfigured using the Expected State functionality that exists on every Resource within Nodinite.
Actions on resources can be called upon using the Nodinite Web Client tool or by programmatically calling the Web API.To execute remote actions some Prerequisites must be satisfied. The user must be logged on to Nodinite using a Windows Credential. The user must also be assigned a Monitor Views with BizTalk Resources where Remote Actions are allowed. See Add or manage Monitor View for more details.
The BizTalk Monitoring Agent has support to filter unwanted resources, see the Configuration page for additional details.