Skip To Content

What's new in the GeoEvent Extension?

En este tema

New at 10.3.1

ArcGIS 10.3.1 GeoEvent Extension for Server includes stability enhancements and improved functionality throughout the product. For a list of issues that are fixed in 10.3.1, see the 10.3.1 Issues Addressed List. For a summary of changes in the software, see the following sections.

ArcGIS GeoEvent Manager

  • ArcGIS GeoEvent Manager has been enhanced to utilize the full width of the browser. This is particularly useful when authoring/editing large GeoEvent Services.
  • It is now possible to delete GeoEvent Definitions and GeoFences in bulk instead of one-by-one.

Processing

  • The Field Enricher Processor now works with map services in addition to feature services.
  • The Track Gap Processor's GeoEvent Definition now has a GEOMETRY tag on its geometry field.
  • Error messaging has been improved on GeoEvent Services to inform users when the data stores that processors depend on cannot be reached.
  • All spatial processors introduced at 10.3 were updated with the ability to specify whether the resulting geometry should override the existing geometry or place the resultant geometry in a new field.

Connectors

  • A GeoJSON inbound and outbound adapter has been introduced enabling GeoJSON format to be used on inputs and outputs.

GeoEvent Gallery Items

  • The GeoEvent Test Harness is a stand-alone utility that allows users to establish performance benchmarks for a given configuration of the GeoEvent Extension.
  • The GeoEvent Cluster Aware Simulator is a stand-alone utility that enables users to simulate events evenly across the machines in a GeoEvent Extension cluster that has a Receive Text from a TCP Socket Input Connector.
  • The RabbitMQ Connector extends the ability of the GeoEvent Extension to configure an input to receive from RabbitMQ or an output to send to RabbitMQ.
  • The Extent Enricher Processor expands a geometry field into separate fields representing the envelope including xMin, yMin, xMax, yMax, and wkid.

New at 10.3

ArcGIS 10.3 for Server includes stability enhancements and improved functionality throughout the product. For a list of issues that are fixed in 10.3, see the 10.3 Issues Addressed List. For a summary of changes in the software, see the following sections.

  • Added the ability to bulk delete GeoEvent Definitions and GeoFences in ArcGIS GeoEvent Manager.

General product updates

  • The release of ArcGIS 10.3 marks the official change of the product name from ArcGIS GeoEvent Processor for Server to ArcGIS GeoEvent Extension for Server.

Internationalization (i18n) and localization (l10n)

The GeoEvent Extension has been localized to Arabic, Chinese (simplified), Japanese, Italian, Portuguese (Brazilian), Russian, and Turkish. Localized installers are available for these languages. A localization toolkit is available for localizing other languages.

Integrated security with ArcGIS for Server and Portal for ArcGIS

ArcGIS GeoEvent Manager now utilizes the same credentials as ArcGIS for Server or Portal for ArcGIS. In addition, GeoEvent Manager recognizes roles (Publishers and Administrators) and provides appropriate access to items in the GeoEvent Extension based on a users role. Lastly, the GeoEvent Extension now utilizes SSL certificates that have been registered with ArcGIS for Server.

Clustering and high availability

  • The Site-Cluster-Machine administration in ArcGIS Server Manager is used to administer GeoEvent Extension clusters.
  • GeoEvent Extension machines, when started, determine their assigned cluster, and their configuration is provisioned.
  • Establishes a distributed configuration store that is shared by all machines in a cluster.
  • When a new machine joins a cluster, any custom transports, adapters, and processors are propagated.
  • Inputs are run as distributed on every machine in the cluster or as pinned inputs on a single machine in the cluster based on their transport.
  • Pinned inputs are monitored and, upon failure, detection started on another machine in the cluster for high availability.
  • Stateful filtering (Enter, Exit) and processing (Incident Detector, Track Gap Detector) are made possible by sharing GeoEvents based on their TRACK_ID to the same machine in the cluster.

Stream Services

A Stream Service is a new type of ArcGIS for Server service that emphasizes low latency, real-time data dissemination for client-server data flows. Clients connecting to a Stream Service begin receiving data immediately upon subscribing to the service. Stream Services are published in the GeoEvent Manager using the Broadcast features to a Stream Service Output Connector.

See Stream Services for more information on Stream Services.

GeoEvent Service, filtering, and processing improvements

  • Filtering has the ability to work with new spatial operators including contains, crosses, intersects, disjoint, equals, overlaps, touches, and within.
  • New processors have been introduced that provide additional spatial capabilities, including Buffer Creator, Convex Hull Creator, Difference Creator, Envelope Creator, Intersector, Projector, Simplifier, Symmetric Difference Creator, and Union Creator.

GeoFence improvements

  • GeoFence performance has been significantly improved with the addition of in-memory spatial indexing.
  • GeoFence import and GeoFence synchronizations work in a clustered environment.
  • Spatial expressions have been enhanced with a scope property that can be a value of Any or All.
  • GeoFence synchronizations have been enhanced with the ability to use a Stream Service as a synchronization source, enabling highly dynamic GeoFencing.
  • A manual sync button has been added to the GeoFence page, enabling a sync on demand.

ArcGIS GeoEvent Manager improvements

  • GeoEvent Manager is fully localizable, including support for right-to-left languages such as Arabic.
  • Auto-logout of GeoEvent Manager now shows a pop-up dialog box, providing the opportunity to reauthenticate without losing work from the current session.
  • Search capabilities have been added to all listing pages including inputs, GeoEvent Services, outputs, GeoEvent Definitions, Connectors, transports, adapters, and processors.
  • Importing and exporting of a GeoEvent configuration has been enhanced to allow selective import and export of GeoEvent Services, inputs, outputs, and GeoFences.
  • The GeoEvent configuration import and export user interface has been enhanced to enable a full server reset.
  • Enhanced the GeoEvent Manager Monitor page with the ability to start, stop, and restart GeoEvent Services, inputs, and outputs.
  • Enhanced the GeoEvent Manager Monitor page with the option to view a live GeoEvent Activity Graph for GeoEvent Services, inputs, and outputs.
  • GeoEvent Services, inputs, and outputs can now be copied by clicking a Copy icon in the listing page to create a new item.
  • When editing a published GeoEvent Service, the status and live monitoring statistics are displayed.
  • GeoEvent Service editing now provides the ability to undo and redo user interactions.
  • GeoEvent Service editing has been enhanced to allow flows in any direction, for example, right-to-left and top-to-bottom.
  • Processor dialog boxes have been enhanced to show label descriptions of available properties.
  • When editing a GeoEvent Service, access to the input and output properties are provided when you right-click an input or output.
  • When editing a GeoEvent Service, new line styles are included when connecting different components including diagonal, Bezier, and flowchart.

Connector improvements

  • Connectors, GeoEvent Definitions, and Tags have been enhanced with an AccessType property to restrict users from editing core GeoEvent Extension items.
  • A generic XML adapter has been added that is similar in concept to the generic JSON adapter.
  • The KML adapter has been removed as an out-of-the-box component in the GeoEvent Extension and is now available as a product gallery item to foster community-driven open source contributions, particularly for inbound KML.
  • The NMEA adapter has been enhanced to handle GPGLL and GPRMC messages.
  • The Feature Service outbound transport has been enhanced to validate when starting and reports errors, if any are found.
  • The HTTP transport has been enhanced, allowing HTTP headers and parameters in the POST body when polling an external website.
  • The HTTP inbound and outbound transport has been enhanced when in client mode to support the PUT method.
  • The HTTP inbound transport has been enhanced, while in server mode, with the ability to process a request when the acceptable MIME types is not set.
  • Authenticated proxy support has been added as a global property.

Data store improvements

  • The GeoEvent Extension now comes with a preconfigured default data store connection to the local ArcGIS Server where the GeoEvent Extension is running.
  • A manual sync button has been added to data stores, enabling a sync on demand.

Software Development Kit (SDK) improvements

  • Display labels for transports, adapters, and processors have been externalized, enabling localization.
  • A new sample is provided showing how to work with a GeoEvent Extension-aware transport—this enables the transport to peak into the contents of the GeoEvent and use field values.