Page History
...
Disabling of Agents can be used for example to manage maintenance windows on server nodes.
| Anchor |
|---|
...
|
...
|
Agents can be hidden to prevent them
...
Independently from an Agent being visible or hidden it can be enabled/disabled with a Controller, see above.
| Anchor |
|---|
...
|
...
|
Agents can be reset in case of problems during initial operation or to re-assign Agents to a different Controller.
- Reset: Any running tasks in an Agent can continue. The Agent does not accept new tasks. With running tasks being completed the Agent will restart. After re
- Reset Forced: Any running task in an Agent are killed. The Agent does not accept new tasks. The Agent drops its journal and restarts with a new journal.
- Dropping the Agent's journal means that it looses its memory. This operation can be used to seize an Agent, i.e. to assign it a different Controller.
- This operation should be used with care, for example if an Agent that is assigned a Controller in a production environment is taken over by a Controller of some different environment.
- After restart of a reset Agent the Controller will deploy scheduling objects such as workflows and will submit orders as assigned the Agent.
...
Overview
Content Tools