18.1 Engine and Device Action Monitor

18.1 Engine and Device Action Monitor

Info
Engine

1. The Engine is a service application which runs independently to Jarrison Time, and runs in the background on one designated computer. It is used to manage and monitor all communications to all of the devices linked to Jarrison Time and to perform background tasks like automatic emails, backups and all other planned events.

2. All devices, which are in correct working order (powered on and accessible through the network), are displayed in blue and have ‘On Line’ as their description. Any device which is not connected to the network or has no power, will be displayed in red and show ‘Off Line’ as the current status.

3. The Engine icon will also have green waves if all devices are online, red waves if all devices are offline and orange waves if at least one device is offline while others remain online. The icon will have blue waves if the Engine is not running. If any unit is offline, please contact the network administrator or your supplier, as no clockings or employee updates will be possible with offline devices.

4. Right-clicking on the icon will allow starting or stopping of the service, or updating if it has become unsynchronized (colours). 

Info
Device Action Monitor

1. Since the Engine runs as a service it has no direct interface, however its activities can be seen from ‘Access’, ‘Device Action Monitor’. This provides snapshots of what the engine is busy with at any given time. Note that the user machine’s time needs to be synchronized with the server time in order for the Monitor to reflect accurately. 

2. You can set the display to only show devices from a specific area by selecting the Area. To enable the Area selection box, right-click on the icon in the system tray and select ‘Show Areas’. 

3. Individual commands can be sent to each device by right-clicking onto the device in the list, then selecting the required command. These commands are listed below (same as found in the Devices window): 

4. Note that if a ZK device has become unresponsive after successive communication attempts, the engine will suspend further attempts until the device is manually reset by right-clicking on it.

 

    • Related Articles

    • 25.1 Device Action Monitor

      Device Action Monitor The monitor can be accessed from 'Access', 'Device Action Monitor'. This window allows the status of devices and actions of the JT Engine to be monitored. Devices may be grouped by region, or a search may be entered to refine ...

    • 24.1 Devices/Details

      Devices Details Enabled - each device needs to be enabled to be included in the JT Engine’s list (viewable from the Device Action Monitor). Remote Clockings Import - if selected will disable all other parameters besides the device name and will ...

    • 11.8 Engine

      Engine 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 ...

    • 32.1 T & A Devices

      T & A Devices In some cases T&A Devices from external access control systems need to be defined within JT. This option is not available with all Import Locations (external access control databases). To setup the Time and Attendance terminals, click ...

    • 30.1 Device Clocking Reasons

      Device Clocking Reasons Clocking Reasons are brief descriptions that can be sent to compatible devices via Send Configuration, allowing individuals to select on the device why they are clocking in or out. Each reason should have a direction and type ...