.png){kind=logo}
SignServer Timed Services
A Timed Service (formerly called just service) is a task that is run on a timely basis, performing maintenance tasks like changing active key, or it could generate a report.
A Timed Service framework supports a couple basic properties that is used to calculate when and how a timed service should run. These properties are:
Property | Description | ||||||
|---|---|---|---|---|---|---|---|
ACTIVE | True if the service should be run. Otherwise, it is disabled. | ||||||
CRON | Defines a CRON expression of how often the service should run. The expression must conform to Unix CRON standard. Only one | ||||||
INTERVAL | Defines the interval in seconds the service should run. | ||||||
INTERVALMS | Defines the interval in milliseconds the service should run. The platform and application server might put a lower bound on the value. The lower limit for GlassFish is by default 7000 milliseconds but can be changed by editing | ||||||
SINGLETON | True if the service only should be run on one of the nodes in the cluster at the time. If the property is not set or set to false, the service runs simultaneously on all nodes in the cluster. If the node running a singleton service fails, another node senses this and starts up the service. | ||||||
WORK_LOG_TYPES | Specifies the log types for logging invocations of the service in a comma-separated list.
By default, if this property is not set, |
