Clock server process threads

There are several processes, called threads, running on the WBCS. Each thread is responsible for a specific set of tasks or actions. Combined, the threads perform the necessary background maintenance and communication required for the clocks connected to the WBCS to function.

The WBCS comes with these threads:

  • adminConsoleDispatcher allows the Admin Console to connect to the WBCS.
  • archive controls the archiving of data and removes exported swipes from the journal.
  • dbupdate retrieves employee data, schedules, and biometric templates from the system. This thread also exports biometric templates from the clocks, if any exist. New biometric templates are usually exported after enrollment.
  • exportswipes exports unsent clock punches from the journal to the system.
  • readerprocess facilitates communication and processing between the clocks and the WBCS.

ImportEmployeeSchedules

A new thread was introduced in the Fixpack 22 release so that the WBCS can import employee schedules on a scheduled basis from the system. This thread works with the Web Services or XML communication methods. However, if you are using the XML method and the system has been configured to use the Readers - Export Schedules Directives task, you do not need to use the Import Schedules thread.

To enable this thread, add this line to the settings.conf file:

class.thread.importschedule = com.infor.wfm.clock.server.thread.EmployeeSchedulesDump

Also, you must configure the thread to run on a schedule or at regular intervals. The thread is configured in the same manner as the other threads, described in this section.

Thread parameters can be configured to run on a schedule or to run at regular intervals. Each thread should either be scheduled or set to run on an interval, but not both.

Be advised that running threads too frequently, especially during peak times, may affect performance. Care should be taken to balance the need for timely information and the overall performance of the WBCS.