What is a Middleware?
This page is destined to the Digifort Administrators who use, or intend to use the Digifort Middlewares.
Here you'll find a list of our available Middlewares, their functions and even a litle knowledge about it's structure, in a way that you'll know if the solution for your system has already been developed by our team.
If you're a Digifort Administrator using a external database, access controll, or anything that uses a external integration, go to the bottom of this page to find our list of Middleware and where they apply.
Understanding the Structure of a Middleware
Based on image above, we can use as an exemple a software with it's own database, or devices that allow TCP comunication, this way, the Middleware will intermediate all the comunication between the devices and Digifort, allowing it to generate events, bookmarks and so, through multi-directional comunication.
To know more, check out our list below and navigate to the bottom of this page to find the download of our Middleware Manual.
Digifort Middleware List
Database AC | This middleware is intended to connect your Digifort to a data source from a access controll software, whether by consulting a Query, reading data files or receiving HTTP commands. |
Entrypass | ||
Axis |
Barco | ||
Mauell |
LPR Listener | This Middleware is intended to receive the vehicle licence plates that were detected by the Digifort LPR through one or more cameras, so it can generate actions according to the according to the needs, which can be the following actions: Send the Plate to a database software, create a new text file with the registration, perform a database query, send the registration to the Helios WebService and so on, thus being able to generate actions in the registered Digifort Server. |
Southwest Microwave | This Middleware is intended to receive the events from a Intrusion Detection Device, wich must be configured which conditions should trigger the said events, thus generating the actions in the registered Digifort Server. |