Operations Basics / Version 2010
Table Of Contents
An edge connects two actions within a component, depending on the result code of the first action. The edges
and actions form a graph. The watchdog process walks through the actions and edges in the graph. Edges are
defined with <Edge> elements in <Component> elements after action
elements.
Edges are configured with the following attributes:
| Attribute | Optional | Description |
|---|---|---|
from
| The name of the action from which the edge starts. | |
to
| The name of the action which follows. | |
code
| Result code (numerical entry or symbolic name). If this value equals the
result code of the action named in the from attribute, then the action
named in the to attribute is executed. Edges may not start from the
same action with the same error code to different target actions. To avoid
defining an Edge tag for all error codes, the edge with the
error code "Error" or "12" serves as the default edge. If an error occurs for
which no edge is defined, the watchdog process will follow the edge with result
code "Error". | |
delay
| x | This attribute specifies the delay in seconds until the subsequent action is executed. The default value is 10 seconds. |
Table 4.23. Attributes of the Edge element
Example:
If the watchdog process has to execute an action "B" in case an action "A" returns with result code "0", you have to configure:
<Edge from="A" to="B" code="0"/ >
Caution
Component definitions should not contain cycles in which every edge has a delay of 0. Such cycles can cause high CPU loads and excessive usage of system processes and open files.