The Engine is a standalone part of Jarrison Time that should always be running. It only runs on one designated machine, as a service.
The JT Engine processes device tasks using multi-threading. This means that by default it processes groups of up to 30 devices at a time, rather than one by one. Depending on the type of hardware the computer has, the number of simultaneous tasks may be configured in the jarrison.ini file.
Designated “Computer Name” - is the name of the PC which will run the JT Engine. This is normally the PC belonging to the person who is responsible for monitoring the systems devices. This field is not case sensitive.
Collect transactions every - the frequency with which the JT Engine will collect clockings, once it has been started.
Note that if ZK Teco brand devices are present in Devices, an additional option will appear here to ‘Delete transactions from ZK Teco devices only at’. This option will stop clearing clockings from device at each clocking import, and instead only do it at the set time. A clocking import will be done first at the designated time.
Log import from each device separately in audit - if selected the audit trail will reflect imports per device.
Number of days to keep log files - The number of days to keep log files
Auto update time from PC - if selected, the Engine sets the time on a daily basis, from five minute intervals up to five days.
Set the ping interval to - determines the time that the JT Engine waits to check (ping) all of the active Devices, any commands waiting to be performed are then performed after the ping command. Ten seconds is the recommended time.
Process ‘Leave Accrual’ daily - this option appears if the Leave module is enabled. If selected it will set leave accumulation to be processed by the Engine as part of its daily processes.
Backup database daily at - a backup will be performed at the time of day set here. It will only keep the selected number of backup files in the selected folder and delete the rest (WinZip files only). It is advised to back up to an external device or network.
Include supplementary database - if selected this will include the supplementary database in the daily backup routine.
Number of files to keep - The number of backups and log files to keep in their respective locations.
Delete from SQL Server - If SQL is version 2019 or higher then this option can be enabled to remove the .bak files created on the SQL server for each backup.
Backup Path - is the destination for the backup file, zipped or not. JT first performs the backup to the C:\JT-Backup folder, then zips if necessary, then copies the file to its final destination (HDD, flash drive, network drive etc.). The C:\JT-Backup folder on the PC where the database is installed must be created and needs to be shared with Read, Write and Modify (change) access for all users who want to perform the backup. Note that C:\JT-Backup must still exist on the SQL server regardless of what location is set here.
Backup Prefix - will always be prefixed to the backup file for easy identification, including the date and time of the backup.
Segment email attachments into - will divide the backup into smaller files as not to exceed a mailbox attachment size limit. You can piece it together again using JT Support only.
Backup on exiting Jarrison Time - this will automatically perform a daily backup upon exiting and only backup the database once a day, as soon as the first user exits each day.
Enable Cloud Backup - tick this option to use cloud options instead of local backup.
Once Cloud Backup is enabled select whether Google Drive or Microsoft SharePoint will be used.
If using Gmail in the ‘Gmail Email Address’ field enter the Gmail address to use, in the ‘Folder’ field add the name of a folder that is shared with Editor permission in Google Drive.
If using SharePoint in the ‘URL’ field enter the SharePoint URL, user account should be entered next to ‘Username’, password in ‘Password’ field. Then click ‘Get Folders’ to find available folders for selection, select the folder to be used.
Then click ‘Test Cloud Backup Settings’ to confirm details are in order.