Message broker data source settings in the Third-Party ALPR plugin - Configure a Message Broker data source to allow the Third-Party ALPR plugin can ingest ALPR data from cloud-based provider partners using a Secure File Transfer Protocol (sFTP) server. - Third-Party ALPR 5.10.11.0 - Plugin and extension guides

Genetecâ„¢ Third-Party ALPR Plugin Guide 5.10.13.0

Product
Third-Party ALPR
Content type
Guides > Plugin and extension guides
Version
5.10
Release
5.10.13.0
ft:locale
en-US
Last updated
2026-08-25

Configure a Message Broker data source to allow the Third-Party ALPR plugin can ingest ALPR data from cloud-based provider partners using a Secure File Transfer Protocol (sFTP) server.

Before you begin:
  • Ensure that you have configured a cloud infrastructure accessible from the plugin server.
  • Unlike other data sources in Genetecâ„¢ Third-Party ALPR, the Message Broker exports hotlists to a external systems, like Vigilant or Safefleet, instead of processing all ALPR reads locally. The external system matches ALPR reads against the hotlists and sends only the hits back to the plugin server.
Setting Description
Name Select a name for the data source that identifies where license plate data is coming from.
Raise 'no data' events Set the time threshold after which a custom Security Center event is triggered if no data is received from the specified data source. For more information, refer to Creating event-to-actions.
Anonymized raw data logging Select this setting to make the data source log raw data with the license plate anonymized.
NOTE: Raw data consists of the exact and unprocessed data that is received from the relevant camera or API. Some private fields are still anonymized for privacy reasons.
Message broker type Select the message broker type that corresponds to your Genetec cloud environment.
Maximum message rate Configure the maximum number of messages the data source is permitted to process in one second.
Tip:
  • Use this setting to limit the load on the system during data spikes.
  • Ensure that the value used here is high enough to process all messages instantly during regular operations.
Cross-reference hits Select whether the plugin includes more properties from the hotlist in hits from third-party devices.
NOTE:
  • If the hit is not found in the hotlist, the hit is still raised without the additional attributes from the hotlist.
  • If the hit is sent to the message broker with more properties also defined in the hotlist, the values in the hotlist overwrite what was sent in the hit.
Tenant ID Configure the name of the tenant for which you want to obtain data. Many tenants can use the cloud infrastructure at the same time.
Cities configuration Service URL Configure the location from which the plugin gets the information needed to connect to the message broker.
Allow self-signed certificates Select whether the system accepts a self-signed certificate. If your system does not have a valid security certificate, you can use a self-signed certificate.
NOTE: Enable this setting in your development or quality assurance environment, but not in your production environment.
OAuth Configure OAuth connection information to authorize secure access between the message broker data source and your system. These credentials consist of the authenticating information associated with your Cities Configuration Service that you created when deploying the cloud infrastructure.
Use virtual ALPR units per geofence Select the geofence-mapped areas used to map hits and reads to virtual ALPR units. Reads and hits are attached to the virtual ALPR units based on the location of the reads.