Clock background process threads
The 9000 uses threads to execute periodic updates to the clock or application.
Background processes are configured in the settings.conf file by indicating the interval at which the process is executed. You should only configure the processes that are required. All other processes should be disabled.
See Adding, removing, and disabling clock configurations.
This table summarizes the available threads:
| Thread | Description |
|---|---|
| Database Update | Retrieves updates to the local clock server database from
the WFM application. Database update downloads application updates, such as
employee record changes. Specify the interval at which the thread will run. For example, every 300 seconds or 5 minutes:
|
| Swipe Export | Exports swipes to the WFM application. Swipe export exports swipes stored on the clock to the application, where the Process Clocks task will apply the swipes to the timesheet. Specify the interval at which the thread will run. For example, every 120 seconds or 2 minutes:
|
| Database Purge | Purges old swipes that have already been exported to the
WFM application. Use purging to maintain the space usage in the clock by removing old records.
|
| Fingerprint Export | Exports newly enrolled fingerprints to the WFM application.
If using biometric verification, fingerprint export ensures that employee fingerprint(s) enrolled at a clock are exported to the application. The application then propagates the fingerprint(s) to other clocks the employee is registered to use. This feature saves time because the employee does not need to be enrolled at each clock. In addition, if a clock database has to be rebuilt the fingerprint(s) can be restored to the clock. Specify the interval at which the thread will run, for example every 120 seconds or 2 minutes
|
| Message Processor | Supports internal operations. Message Processor ensures that a number of internal processes are completed. This clock background process should not be disabled and the thread schedule should not be altered. This is the default configuration:
|
| File Update | Processes software and configuration updates. File Update allows the clock to check for software and configuration updates automatically. In addition, if software or configuration updates are required the same thread will initiate the process to completion. Specify the interval at which the thread will run. For example, every 600 seconds or 10 minutes:
|
| Schedules Table Dump | Retrieves schedules to the local clock server database from
the WFM application. If utilizing schedule validation or view schedules feature of the clock, this specific table dump must be configured to download employee schedules to the clock. Unlike database update, which only downloads new schedules, the schedules table dump downloads all schedules available for the clock. Specify the interval at which the thread will run. For example, 43200 seconds (12 hours):
|
| Time Approval Synchronizer | Synchronizes time approval records between the clock and
application. If utilizing the time approval feature of the clock, the time approval synchronizer thread will synchronize processed time approval records between the clock and the WFM application. Specify the interval at which the thread will run. For example, every 120 seconds or 2 minutes:
|
| Reader Status Export | When necessary, updates the IP address of the clock's
reader configuration in the WFM application. Reader Status Export ensures that the true IP address of the clock is reflected in the clock's reader configuration of the WFM application. The clock only updates the reader configuration if the IP address has changed and is not consistent with the current value in the reader configuration. Specify the interval at which the clock will verify its IP address and, if necessary, update the WFM application:
|