Sep 13, 2022
Access It! Service Transaction Processing
The following outlines the process of how event transactions are handled by the Access It! service.
This article applies to:
- Access It! v6.4.0.11 and greater
- Transaction originates at panel (i.e., Access Granted)
- Transaction is retrieved from the SCP by the Access It! Service
- Access It! Service adds the transaction to an in-memory event queue
- The Access It! Service retrieves the first 100 events within the event queue and begins processing one at a time:
- If the event changes the state of a device (i.e, Door Opened), the corresponding device state table is updated in the database and all workstations are notified and grids refreshed
- The transaction is then inserted into the current SQL AIUEvents database
- Unless configured to Log Only or <None>, the transaction is then posted to all connected workstations
- If a Macro is tied to the transaction it is then executed by the Access It! Service
- The Service then waits 5 seconds and repeats step 4
Access It! Universal.NET Service Buffer Transaction Protection
To prevent the possibility of the service running out of memory and loosing transactions, the following safeguard is in place
- When the event queue exceeds 5,000 transactions all SCP panels are instructed to stop reporting events and begin to store events in their own internal memory
- When the backlogged queue reaches 1,000 transactions all SCPs are instructed to start reporting events once again
- This cycle continues as needed