By default, manual recovery is always enabled. You can run Recover Operators even if you set the target-level Operator Auto Recovery option to True, False, or Inherit from Environment.
Create a process watch and create shortcuts to the targets you want to monitor, such as the Orchestrators, Touchpoints, and Proxy Touchpoints.
You can run Recover Operators from the process watch in the following circumstances:
Note: You cannot run Operators recovery on a target that is disabled.
Process watch enables you to view processes that are only in Blocked state or only in Running state. For example, expand the Orchestrator node and select Blocked Instances.
If you notice a number of blocked processes when the desired target is active, run Recover Operators on that target. Recovery affects blocked, running, waiting processes that have operators in system_error. Recover Operators resets affected operators and resumes the processes. The target can be an Orchestrator, a Touchpoint, a Proxy Touchpoint, or a Host Group.
Note: When you run Recover Operators through the process watch, recovery acts on targets that are blocked, running, or waiting on any Orchestrator in the Environment. Recovery is not limited to the Orchestrator of the current library. Recovery is performed only on processes for which Enable Operator Recovery is set.
Follow these steps:
The Process Watch displays the predefined groups of instances. Process Watch objects display predefined groups for selected objects.
The process instances in Blocked, Running, or Waiting state are listed.
The Recover Operators option is available when these two conditions exist.
Recovery is initiated on each failed Operator in SYSTEM_ERROR that is part of a blocked, running, or waiting process that is configured with Enable Operator Recovery. Recovery includes operators in process that is configured with Enable Operator Recovery set and on any Orchestrator within the Environment. Recovery is not limited to the current library Orchestrator.
The processes previously in Blocked state begin running when the recovery request completes execution.
|
Copyright © 2014 CA.
All rights reserved.
|
|