Scribd
Upload
327 views1 page

Darwinbox Bio-Metric-Integration Pull v1.1

The document describes two options for integrating biometric attendance data from a client's biometric device directly into the Darwinbox application: 1) a push integration where the biometric device continuously sends data to Darwinbox servers or 2) a pull integration where Darwinbox provides a Java application to reside on the client's network that reads biometric data and updates Darwinbox servers. It then provides the required data fields and format that Darwinbox needs to enable the pull integration.

Uploaded by

Sanketh Thilak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
327 views1 page

Darwinbox Bio-Metric-Integration Pull v1.1

The document describes two options for integrating biometric attendance data from a client's biometric device directly into the Darwinbox application: 1) a push integration where the biometric device continuously sends data to Darwinbox servers or 2) a pull integration where Darwinbox provides a Java application to reside on the client's network that reads biometric data and updates Darwinbox servers. It then provides the required data fields and format that Darwinbox needs to enable the pull integration.

Uploaded by

Sanketh Thilak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

BIOMETRIC INTEGRATION

Capability to integrate biometric attendance data directly into Darwinbox application. This can be addressed using multiple
options.

1. PUSH

The client can avail a push biometric device (tested with ESSL Push server) which can continuously send biometric data to
Darwinbox servers. This setup requires setting up a push server domain / IP on the client biometric device.

2. PULL
Alternatively, Darwinbox provides a Java application that can reside on client’s internal network on a machine constantly
connected to the internet.

This setup requires for client to provide access to their internal biometric database for read access. The tiny app reads
biometric punches and updates Darwinbox servers.

HOW IS THE PULL INTEGRATION DONE?

WE REQUIRE THE FOLLOWING DETAILS FROM YOUR IT POC/VENDOR:

 TransactionID (a unique id that is generated for every swipe in and swipe out)
 EmployeeID (a unique id that is there for each employee)
 In/Out Status (For example 0 or IN for Swipe in and 1 or OUT for Swipe out) Timestamp
(the date and time when the swipe(in/out) out happened)
 All the above fields are mandatory.

If these fields are available in your database, then we will be able to install the Darwinbox biometric desktop application. This
will ensure the biometric integration with the Darwinbox web application.

PLEASE ENSURE THAT -


1- We need In and Out Status in a single column.
2- The in and out timestamps should be a in a single column.
3- The data should be real time.

PLEASE NOTE THE FORMAT OF THE DATA THAT WE NEED.

Employee_id status timestamp transaction_id


90106 1 2019-01-01 05:25:34 1
80059 2 2019-01-01 05:29:51 2
XYZ321 2 2019-01-01 05:32:08 3
ABC123 1 2019-01-01 05:32:17 4
90106 2 2019-01-01 05:30:45 5
80059 1 2019-01-01 05:32:02 6
10005967 2 2019-01-01 05:34:57 7
2009 2 2019-01-01 05:32:56 8
102032 1 2019-01-01 05:08:00 9
102824 2 2019-01-01 05:10:00 10

You might also like