ArcGIS GeoEvent Server was designed to be configurable via the system properties. You can access and update the GeoEvent Server system properties to meet your deployment and use case requirements using either ArcGIS GeoEvent Manager or the configuration files.
Access using ArcGIS GeoEvent Manager
Administrators can edit GeoEvent Server system properties using ArcGIS GeoEvent Manager . 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. All the GeoEvent Manager
Access using the 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 in the following directories:
- Windows—<ArcGIS Server installation directory>\GeoEvent\etc
- Linux—<ArcGIS Server installation directory>/GeoEvent/etc
A few examples of configuration files an administrator may want to edit include the following:
- ArcGISGeoEvent.cfg—Contains command line options used to launch the JVM which runs GeoEvent Server. For details, see GeoEvent Server configuration file.
- com.esri.ges.manager.servicemanager.cfg—Specifies the maximum number of Track IDs a cache-aware node will maintain which is required for ENTRY / EXIT spatial relationship determinations. For details, see Maximum cache size configuration file.
- com.esri.ges.persistance.file.cfg—Used for managing the backup of your GeoEvent Server configuration. For details, see Backup configuration file.
- 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. For details, see Logging configuration file.
Changing GeoEvent Server system properties can have intended and unintended consequences; always test any changes before deploying to a production environment.