You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Home > Access It! Universal.NET > Access It! Universal.NET Service Transaction Processing
Access It! Universal.NET Service Transaction Processing
print icon

Access It! Universal.NET Service Transaction Processing

The following outlines the process of how event transactions are handled by the Access It! Universal.NET service. This information applies to version 6.4.0.11 and greater

  1. Transaction originates at panel (i.e., Access Granted)
  2. Transaction is retrieved from the SCP by the Access It! Universal.NET Service
  3. Access It! Universal.NET Service adds the transaction to an in-memory event queue
  4. The Access It! Universal.NET Service retrieves the first 100 events within the event queue and begins processing one at a time:
    1. 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
    2. The transaction is then inserted into the current SQL AIUEvents database
    3. Unless configured to Log Only or <None>, the transaction is then posted to all connected workstations
    4. If a Macro is tied to the transaction it is then executed by the Access It! Universal.NET Service
  5. 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

scroll to top icon