Database Ownership

Each adTempus instance uses its own database to store configuration information. To ensure that only one instance is ever using a database at the same time, the adTempus service saves locking information in the database while it is running. It periodically records a "heartbeat" update to the database indicating that it is still active, and when it shuts down it releases its lock on the database. On startup, the service checks to see if the database already belongs to another instance. If so, it determines whether the other instance is active:

New feature iconThis locking mechanism is new for adTempus 5. Earlier versions used a different locking mechanism (see the version 4 user guide for more information). Future versions of adTempus may use this heartbeat information to support automatic failover.