Essential GeoEvent Processor vocabulary
An understanding of the terms below is essential when using GeoEvent Processor.
A configuration is a collection of user-created inputs, outputs, GeoEvent Services, connectors, GeoEvent Definitions, tags, GeoFences, data stores, and more. A configuration file (.xml) can be exported using the GeoEvent Processor Manager Configuration Store and allows you to archive, restore, and share your configurations.
The Configuration Store in GeoEvent Processor Manager allows administrators to import and export GeoEvent Processor configurations. Importing a configuration adds and updates existing components.
Existing components are not modified unless a component with the same name is included in the configuration being imported.
Input Connectors and Output Connectors make it easy to get streaming data into and out of GeoEvent Processor. In GeoEvent Processor Manager, administrators can browse to the Site > GeoEvent Processor > Connectors page to view a list of the available connectors as well as create new connectors.
See Managing connectors to learn more about connectors.
The Data Store in GeoEvent Processor Manager at Site > GeoEvent Processor > Data Stores allows administrators to register system folders and ArcGIS Server connections with GeoEvent Processor. Registering is necessary because several types of Input Connectors, Output Connectors, and processors that participate in a GeoEvent Service must reference a registered data store when reading or writing event data.
Filters are components of a GeoEvent Service that filter out GeoEvents which do not satisfy a specified criteria as the events are routed between Input Connectors and Output Connectors. GeoEvents that satisfy the filters criteria pass through the filter for further processing.
See Filters to learn more about the types of filters available.
Data flows through GeoEvent Processor as a series of GeoEvents. When an event stream—which can be characterized as a sequence of messages containing attribute values such as the date/time an event occurred as well as coordinates specifying the event location—is received by an Input Connector, the data is interpreted and translated by the connector into a series of GeoEvents.
A GeoEvent Definition defines a schema for GeoEvents streaming through GeoEvent Processor and identifies the attribute fields and data types (date, string, integer, and so forth) for each GeoEvent. A GeoEvent Definition must exist in order for an Input Connector to construct GeoEvents from a data stream. Similarly, a GeoEvent Definition consistent with the schema of a designated output must exist in order for an Output Connector to deconstruct a GeoEvent and dispatch the event data.
A GeoEvent Service routes GeoEvents from one or more Input Connectors to one or more Output Connectors. Configurable filter and processor components can be included in a GeoEvent Service to identify, enrich, geotag, and further process GeoEvents as they are routed between a service's Input and Output Connectors.
A GeoFence is a geometry, most commonly a polygon, used for spatial proximity analysis. For example, an Incident Detector Processor might be configured to detect when the coordinates of a received event are inside or outside a specified set of GeoFences. A GeoTagger Processor might be configured to include the name of a GeoFence and whether an event is discovered to be inside in the events attribute data.
Input Connector (input)
An Input Connector is the component of a GeoEvent Service responsible for receiving and interpreting events from a data stream. The Input Connector retrieves attribute values from each event and constructs a GeoEvent, which can be routed through optional filters and processors to an Output Connector. Each Input Connector is configured to receive a data stream from a single specific data source. Every GeoEvent Service must include at least one Input Connector.
Output Connector (output)
An Output Connector is the component of a GeoEvent Service responsible for converting GeoEvents back into a data stream to send to a specified destination. Every GeoEvent Service must include at least one Output Connector, but may include more than one.
Processors are the components of a GeoEvent Service that allow you to perform real-time processing on GeoEvents, such as identification or enrichment, as they are routed through GeoEvent Processor.
See Processors to learn more about the types of processors available.
A tag is a label placed on a particular field of a GeoEvent Definition. Tags are similar to field aliases; they support consistency in expressions when different event definitions associate similar data with different field names. Certain built-in tags identify GeoEvent Processor fields containing critical information such as a TRACK_ID or GEOMETRY.
A Track ID is a field in a GeoEvent Definition that relates GeoEvents to specific entities. For example, a truck might be identified by its license plate number or an aircraft by an assigned flight number. These identifiers can be used as Track IDs to track the events associated with a particular real-world entity or set of incidents. GeoEvent Processor includes a built-in tag, TRACK_ID, which should be applied to the field of a GeoEvent Definition that supplies the unique identifier for an entity or incident.