An understanding of the terms below is essential when using ArcGIS GeoEvent Server.
ArcGIS GeoEvent Manager
ArcGIS GeoEvent Manager is the application used to administer GeoEvent Server. Use GeoEvent Manager to monitor event record counts for integration, processing, and broadcast; creating and managing inputs and outputs; and designing and publishing GeoEvent Services. GeoEvent Manager is also the application for reviewing and updating GeoEvent Definitions, importing geofences, and managing GeoEvent Server configurations and data store connections.
Configuration
A GeoEvent Server configuration is a collection of user-created inputs, outputs, GeoEvent Services, connectors, GeoEvent Definitions, tags, geofences, data stores, and more. A GeoEvent Server configuration file (.xml) allows you to archive, restore, and share your configurations with others. The configuration file can be exported using GeoEvent Manager.
Configuration store
The configuration store in GeoEvent Manager allows administrators to import, export, and reset GeoEvent Server configurations. Importing a configuration adds and updates existing components. Resetting a configuration restores the default GeoEvent Server configuration.
Connector
Connectors can be either input connectors or output connectors. Connectors allow you to get streaming data into and out of GeoEvent Server. In GeoEvent Manager, administrators can browse to Site > GeoEvent > Connectors to view a list of the available connectors as well as create new connectors.
Data store
The Data Store page in GeoEvent Manager allows administrators to register system folders and ArcGIS Enterprise, ArcGIS Server, and ArcGIS Online connections with GeoEvent Server. Registering a connection 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.
Event Viewer
The Event Viewer is a web map viewer available in GeoEvent Sampler that can be used to display the geometry of sampled event records.
Filter
A filter element in a GeoEvent Service filters out event records that do not satisfy specified criteria. Event records which satisfy a filter's criteria pass through the filter for further processing.
Event record
Real-time data flows through elements in a GeoEvent Service as a series of event records. Event records are data describing observations. They usually have scalar attributes such as serial numbers or other asset identifiers. They also have temporal attributes such as the date and time of an observation. Event records may contain coordinates, specifying a point at which the observation was made, but can also contain //point, polyine, or polygon geometry// formatted as JSON strings. An input connector (input) adapts raw data formatted as JSON, XML, or delimited text to create an event record for processing by a GeoEvent Service.
GeoEvent Definition
A GeoEvent Definition defines the schema of an event record. Event records routed between filters and processors in a GeoEvent Service have attributes with specific data types, such as dates, strings, integers, or geometries. The attribute field names and their data types are specified in a GeoEvent Definition. A GeoEvent Definition must exist for an input connector to construct event records from a data feed. Similarly, a GeoEvent Definition consistent with the schema of a designated output must exist for an output connector to deconstruct an event record and disseminate the event data.
GeoEvent Sampler
GeoEvent Sampler is a utility in the service designer of GeoEvent Manager. It samples a fixed number of event records as they are routed through elements of a published GeoEvent Service. The sampled event records can be viewed in the sampler window as prettified JSON or delimited text. Sampling event records can provide greater insight, earlier, into real-time data feeds and can assist in designing, validating, and troubleshooting different routes in a GeoEvent Service.
GeoEvent Service
A Geoevent Service performs real-time analysis on event records as it routes them from one or more input connectors to one or more output connectors. Configurable filters and processors can be included in a GeoEvent Service to identify, enrich, geotag, and further process event records as they are routed between a service's inputs and outputs.
Geofence
A geofence is a geometry, most commonly a polygon, used for spatial proximity analysis. For example, a spatial filter can be configured to detect when the location of a received event is inside or outside a specified set of geofences. A geotagger processor can be configured to include the name of a geofence and whether an event is discovered to be inside or outside a geofence.
Input connector (input)
An input connector (or input) is a GeoEvent Service element that receives and interprets events from streaming data. An input connector retrieves attribute values from each event and constructs an event record, which can be routed through optional filters and processors to an output connector. Each input connector is configured to receive event data from a single data source. Every GeoEvent Service must include at least one input connector.
Output connector (output)
An output connector (or output) is a GeoEvent Service element that converts event records back into a data stream to send to a specified destination. Every GeoEvent Service must include at least one output connector.
Processor
A Processor is a GeoEvent Service element that allows you to perform real-time processing and analysis on event records, such as identification or enrichment of the event data, as they are routed through GeoEvent Server.
Real-time analysis
Real-time analysis is the processing performed by a combination of one or more configurable filters and processors in a GeoEvent Service. A processor such as a field enricher processor that is configured to incorporate values from a feature record or table into an event record is an example of real-time analysis. Another example of real-time analysis is a geotagger processor that is configured to enrich an event record with the name of a geofence that an event record's geometry shares a spatial relationship with. A filter that is configured to discard event records when their attributes or geometry fail to satisfy specified criteria and a processor that is configured to calculate a derivative value or manipulate a string's value are also examples of GeoEvent Service elements configured to perform real-time analysis on streaming data.
Route
A route is the connection between two elements (input, output, filters, and processors) in a GeoEvent Service. Each connection between two configurable elements in a GeoEvent Service is referred to as a route. The series of connections between an input, one or more filters or processors, and an output can be referred to as a route or an event record processing workflow.
Stream container
A stream container is the run time entity hosting a stream service. For example, a Jetty web server that supports WebSockets may be referred to as a stream container.
Stream layer
A stream service contains a stream layer, similar to a feature service containing one or more feature layers. Each stream layer corresponds to a specific geometric type such as a point, polyline, or polygon. Stream services can only contain a single stream layer (unlike feature services or map services, which can have multiple layers).
Learn more about stream layers in ArcGIS Maps SDK for JavaScript
Stream server
A stream server refers to the REST endpoint of a stream service in the ArcGIS Server REST Services Directory. For example, information about a stream service named Assets can be found at http://<server>:<port>/<site>/services/Assets/StreamServer.
Stream service
A stream service is a type of ArcGIS Server service. Stream services are discoverable in the ArcGIS organization, listed in the ArcGIS REST Services Directory for review, and can be administered using the ArcGIS Server Administrator Directory. Stream services are created in ArcGIS GeoEvent Manager using the Send Features to a Stream Service output connector.
Note:
Stream services do not contain multiple layers such as map services or feature services.
Tag
A tag is a label placed on a field in 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. Several built-in tags identify the GeoEvent Server fields containing important information such as TRACK_ID or GEOMETRY.
Track ID (TRACK_ID)
A Track ID (TRACK_ID field) in a GeoEvent Definition relates event records to specific entities. For example, a truck may 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 Server includes a built-in tag, TRACK_ID, that should be applied to the field of a GeoEvent Definition that supplies the unique identifier for an entity or incident.