User's Guide

Controlling the Heartbeat

The heartbeat function is controlled by issuing one of the following commands from the Tivoli Console:

wdmheartbeat

Stops or starts the 'heartbeat' monitoring of endpoints, changes its frequency and queries the status of the heartbeat processor (see wdmheartbeat, for more details).

wdmmn

Stops the heartbeat engine on one or all managed nodes/gateways (see wdmmn, for more details).

Figure 4 shows the data flow for the heartbeat control.

Figure 4. Data flow for heartbeat control

The heartbeat control commands are routed to the gateway (steps 1 and 2), where they are processed by the heartbeat processor.

Note:

The heartbeat processor is protected from closures of the oserv such that if the oserv is closed and then re-opened, the heartbeat processor restarts at the same frequency it was using when the oserv was closed.