Configuring GeoEvent Server properties using GeoEvent Manager

ArcGIS GeoEvent Server was designed to be configurable. GeoEvent Manager, for example, allows you to design and publish GeoEvent Services whose input connectors, output connectors, filters, and processors are all configurable. This flexibility allows you to define the type of event data you want to ingest, the real-time analytics to perform on that streaming data, and the event dissemination and notification you require in your client applications.

Administrators may need to alter fundamental GeoEvent Server system properties. This can include command line options used to launch the Java virtual machine (JVM) which runs the application or global settings which specify the size of buffers used by input connectors.

Configuring GeoEvent Server properties using configuration files

Not all system properties are exposed through GeoEvent Manager. Properties such as the command line options used to launch the Java virtual machine (JVM) must be accessed from configuration files during application launch before the application's user interface is available.

The etc folder in the ArcGIS GeoEvent Server installation directory contains the configuration files for GeoEvent Server. All configuration files can be found at:

• Windows - <ArcGIS Server installation directory>\GeoEvent\etc
• Linux - <ArcGIS Server installation directory>/GeoEvent/etc

A few examples of configuration files an administrator might want to edit include:

• ArcGISGeoEvent.cfg - Contains command line options used to launch the JVM which runs GeoEvent Server.
• com.esri.ges.manager.servicemanager.cfg - Specifies the maximum number of TRACK_ID a cache-aware node will maintain which is required for ENTRY / EXIT spatial relationship determinations.
• org.ops4j.pax.logging.cfg - Specifies the logging level for GeoEvent Server components, the log message formatting, log message file size, and number of log message files to keep for historical purposes.