Dehydrated Orchestration Instance(s) Category
The Nodinite BizTalk Server Monitoring Agent monitors BizTalk Server Dehydrated Orchestration Instances for all BizTalk Applications with Orchestrations in your group.
- Dehydrated Orchestration Instances in BizTalk list with Nodinite as Resources where the Resource name is 'Dehydrated Orchestration Instance(s)'.
- Nodinite has the same notion of an Application where there is a 1:1 mapping with its BizTalk Application.
- Dehydrated Orchestration Instances are grouped by the Category Dehydrated Orchestration Instance(s).
Tip
All User operations within Nodinite are Log Audited, which helps you with your security policies and corporate governance compliance policies.
What are the key features for Monitoring BizTalk Server Dehydrated Orchestration Instances?
- Remote Actions - Support the execution of remote actions, which means you can manage the Dehydrated Orchestration Instance(s).
- State Evaluation - Monitors Dehydrated Orchestration Instance(s) and evaluates as Warning or Error if there are too many or too old.
What is evaluated for BizTalk Dehydrated Orchestration Instances?
The different evaluated state for any Dehydrated Orchestration Instance is provided in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available | Evaluation of the 'BizTalk Dehydrated Orchestration Instances' is not possible either due to network or security-related problems | Review prerequisites | |
Error | Error threshold is breached | More Dehydrated Orchestration Instances exist than is allowed by the Error thresholds level | Edit thresholds Manage Dehydrated Instances Suspend all | |
Warning | Warning threshold is breached | More Dehydrated Orchestration Instances exist than is allowed by the Warning thresholds level | Edit thresholds Manage Dehydrated Instances Suspend all | |
OK | Within user-defined thresholds | Number of Dehydrated Orchestration Instances are within user-defined thresholds | Edit thresholds Manage Dehydrated Instances Suspend all |
Tip
The evaluated state may be reconfigured using the Expected State functionality on every Resource within Nodinite.
Remote Actions
The following Remote Actions are available for the Dehydrated Orchestration Instance(s) Category:
List of Remote Actions.
Manage Dehydrated Orchestration Instances
To manage the Dehydrated Orchestration Instances threshold for the selected BizTalk Server Application, click the Action button and select the Manage Dehydrated Orchestration Instances button menu item:
Action button menu with the 'Manage Dehydrated Orchestration Instances' menu item.
Next, the Modal where you can view details for current Dehydrated Orchestration is displayed:
List of Dehydrated Orchestration Instances.
List of Actions that the end-user can apply on selected Dehydrated Orchestration Instances.
The following methods can be applied to single or multiple instances using the Actions available in the Actions and the With selected buttons.
List of Actions that the end-user can apply on selected Dehydrated Orchestration Instances.
Suspend
The Nodinite end-user can Suspend Dehydrated Orchestration Instances.
Click on the Suspend menu item in the Actions button for single instances, or check multiple rows and make use of the 'With selected' dropdown button:
The end-user must confirm intent to Suspend the instance.
Terminate
The Nodinite end-user can Terminate Dehydrated Orchestration Instances.
Click on the Terminate menu item in the Actions button for single instances, or check multiple rows and make use of the 'With selected' dropdown button:
The end-user must confirm intent to Terminate the instance.
Edit thresholds
To manage the Dehydrated Orchestration Instance(s) threshold for the selected BizTalk Server Application, press the Action button and select the Edit thresholds button menu item:
Action button menu with the Edit thresholds option.
Next, the Modal where you can manage the alert threshold for Dehydrated Orchestration Instances is displayed:
Time-based evaluation
Time-based evaluation is always evaluated. If you do not want to perform the evaluation based on time then simply provide long enough thresholds.
State | Name | Data Type | Description |
---|---|---|---|
Warning TimeSpan | Timespan 00:13:37 (13 minutes 37 seconds) | If the time of Dehydrated Orchestration Instance(s) exceeded The specified time, a Warning alert is raised. Format (days.hours:minutes:seconds, e.g. 7.12:30:59) | |
Error TimeSpan | Timespan 01:10:00 (1 hour 10 minutes) | If the time of Dehydrated Orchestration Instance(s) exceeded The specified time, an Error alert is raised. Format (days.hours:minutes:seconds, e.g. 7.12:30:59) |
Count based evaluation
Provide a positive integer value for the number of allowed Dehydrated Orchestration Instances.
State | Name | Data Type | Description |
---|---|---|---|
Warning Count | integer | If the number of Dehydrated Orchestration Instances is higher than the specified value, a Warning alert is raised | |
Error Count | integer | If the number of Dehydrated Orchestration Instances is higher than the specified value, an Error alert is raised |
Suspend all
The end-user can Suspend all the Active Instances by clicking the 'Suppress all' menu item in the Actions button.
The Suspend All Action Button menu item.
The end-user must confirm the intent to Suspend all the Active Instances.
Here's an example of modal to confirm intent to Suspend all Active Instances.
Next Step
Related
Administration
Monitoring Agents
Add or manage a Monitoring Agent Configuration