Synchronize Card Swiping Records to Third-Party Database

You can enable synchronization function to apply the card swiping records of specified resources from HikCentral Professional to the third-party database automatically.

  1. In the top left corner of Home page, select > Basic Management > System.
  2. Select Third-Party Integration > Data Interchange on the left.
  3. Switch on Data Interchange to enable data interchange function.
  4. Click Add and select the resource(s) for card swiping records synchronization. Set the direction to In, Out, or Null.
    Note:

    • Setting the direction is only available for card readers. For other devices, Null will be displayed no matter what direction is selected.

    • You can click in the Operation column to delete the resource or click Delete All to delete all added resources.

  5. Select the encoding format of data interchange.
  6. Optional: Check Do Not Push Failed Records.

    The failed records will not be pushed to the third-party system.

  7. Select Database Synchronization.
  8. Optional: Switch on Auto Push Failed Record to select the push mode.
    Push at Fixed Time

    The failed record will be pushed at the time you set.

    Push at Fixed Interval

    The failed record will be pushed according to the interval you set.

  9. Optional: Select Database Type from the drop-down list to set the database type.
  10. Set the required parameters of the third-party database, including server IP address or domain name, server port, database name, user name, and password.
  11. Click Test Connection to test whether database can be connected.
  12. Set table parameters of database table and table fields according to the actual configurations.
    1. Enter the table name of the third-party database.
    2. Enter the mode of the third-party database.
    3. Set the mapped table fields between the HikCentral Professional and the third-party database.
    4. Optional: Click Customize Items to Display to select the items to be displayed in the table.
  13. Click Save.

    The data will be written to the third-party database.