The global settings available in ArcGIS GeoEvent Server allow you to configure GeoEvent Server to align with a variety of deployments. For example, you may want to configure proxy settings for internet access, set the frequency of automated backups, or increase the maximum supported message sizes.
The following section provides an overview of the global settings available in GeoEvent Server. Some settings may require additional information from your IT department or third-party vendors to properly configure. Incorrectly configured settings can result in reduced functionality or data loss.
Automatic backup settings
The Automatic Backup Settings section allows you to configure scheduled backups of the entire GeoEvent Server configuration.
The following settings are available under the Automatic Backup Settings section:
- Backup Options—A backup can be scheduled to run daily, weekly, or monthly. A backup occurs daily at 12 a.m. with up to 10 days of configurations stored. Configure the automatic backups folder under Site > GeoEvent > Data Stores.
- Enable Automatic Backups—If the value of the Enable Automatic Backups setting is set to true, automatic backups are generated. If the value is set to false, automatic backups are not generated. By default, automatic backups are available.
- Max Backups—The Max Backups setting allows you to store n number of configurations. Once the maximum number of configurations is reached, GeoEvent Server automatically deletes the oldest backup file to make room for new ones.
Geofence manager settings
The GeoFences Manager Settings section allows you to configure options for the spatial operators, geometric precision, and data storage considerations for geofences.
The following settings are available under the GeoFences Manager Settings section:
- First GeoEvent triggers Enter—Used in conjunction with the spatial filtering processors (for example, filter, GeoTagger, Incident Detector, and more) to determine whether the first GeoEvent of a defined track appears inside a geofence and whether an enter condition should be triggered. The default is true.
- First GeoEvent triggers Exit—Used in conjunction with the spatial filtering processors (for example, filter, GeoTagger, Incident Detector, and more) to determine whether the first GeoEvent of a defined track appears outside a geofence and whether an exit condition should be triggered. The default is false.
- GeoFence Acceleration Degree—The resource priority given to spatial evaluations. The value is a non-negative whole number between 0 and 3. Higher values represent increased usage speed at the cost of longer initial loading time and higher memory consumption. The default is 3.
- 0—No acceleration
- 1—Mild acceleration (consumes the least amount of memory)
- 2—Medium acceleration (consumes more memory and takes more time to accelerate when adding a geofence, but works faster)
- 3—High acceleration (consumes the most memory and takes the longest time to accelerate when adding a geofence, but works faster than the others)
- GeoFence Purging Enabled—Determines whether an expired geofence based on the END_TIME tagged field is automatically deleted. The default is false.
- GeoFence Purging Interval (seconds)—Used in conjunction with the Geofence Purging Enabled setting to define an interval to check for expired geofences. The default is 300 seconds.
- Spatial Index Maximum Level of Details—The level of precision of stored geofence geometries. A higher value improves indexing for smaller geographic areas (smaller geofences), but increases memory usage. The value should be between 4 and 32. The default is 16.
Geometry processor settings
The Geometry Processor Settings section allows administrators to manage which selectable linear units are available for use in the processors within GeoEvent Server.
The following setting is available under the Geometry Processor Settings section:
Allowed units list—A list of allowed metric and imperial units, such as meter, kilometer, mile, yard, and more. If the value of a unit listed under the Allowed units list setting is set to true, the unit is active. If the value is set to false, the unit is inactive.
Http proxy settings
The Http Proxy Settings section allows administrators to configure GeoEvent Server to access online resources through an HTTP proxy. This is typically an internal site users must first authenticate against before connecting to the internet.
The following settings are available under the Http Proxy Settings section:
- Http Proxy Host—The host name, or address, of the HTTP proxy server.
- Http Proxy Password—The password to present to the server if the proxy requires authentication.
- Http Proxy Port—The port number of the HTTP proxy server.
- Http Proxy User—The user to pass to the server if the HTTP proxy requires authentication.
Http and Https proxy settings
The Http and Https Proxy Settings section allows administrators to configure GeoEvent Server to access online resources through an HTTP and HTTPS proxy. This is typically an internal site users must first authenticate against before connecting to the internet.
The following setting is available under the Http and Https Proxy Settings section:
Host to exclude from http and https proxy—The hosts that should be accessed without going through the HTTP proxy. This defines internal hosts. The value of this property is a list of hosts, separated by the | character. The wildcard character * can be used for pattern matching. For example, http.nonProxyHosts="*.foo.com|localhost" indicates that every host in the foo.com domain and the localhost should be accessed directly even if a proxy server is specified.
Https proxy settings
The Https Proxy Settings section allows administrators to configure GeoEvent Server to access online resources through an HTTPS proxy. This is an internal site that users must first authenticate against before connecting to the internet. These settings are functionally the same as the HTTP proxy settings, but are secured through SSL communication.
The following settings are available under the Https Proxy Settings section:
- Https Proxy Host—The host name, or address, of the HTTPS proxy server.
- Https Proxy Password—The password to present to the server if the proxy requires authentication.
- Https Proxy Port—The port number of the HTTPS proxy server.
- Https Proxy User—The user to pass to the server if the HTTPS proxy requires authentication.
Incident manager settings
The Incident Manager Settings section defines the maximum number of closed and open incidents in the Incident Detector Processor. Increasing the values allows you to monitor additional track ID tagged events, but it also results in higher memory usage.
The following settings are available under the Incident Manager Settings section:
- Maximum number of closed incidents—The maximum number of closed incidents in the Incident Detector Processor. By default, the Incident Detector Processor can retain the current state of 1,000 open incidents.
- Maximum number of opened incidents—The maximum number of open incidents in the Incident Detector Processor. By default, the Incident Detector Processor can retain the current state of 1,000 closed incidents.
Input and output settings
The Input and Output Settings section allows you to configure the input buffer capacity value. Any changes to this setting are not reflected in existing inputs and a restart of the ArcGIS GeoEvent Server service is recommended.
The following setting is available under the Input and Output Settings section:
Input Buffer Capacity (MB)—This value determines the maximum message size (in MB) that can be maintained in memory for an input. Large batches of events or those with highly complex geometries can sometimes exceed the default setting of 20. The value should be set between 1 and 2047.
SMS settings
The SMS Settings section provides the Short Message Service (SMS) endpoints for most cellular carriers.
The following setting is available under the SMS Settings section:
Carriers—A list of cellular carriers, such as T-Mobile, Verizon, and more. When sending a text message, the output is automatically populated using these settings to include number@carrier.com. For example, for Verizon, it would be 5551234567@vtext.com. The endpoints can be updated and new carriers can be added.
SMTP settings
The SMTP Settings section allows administrators to configure the Simple Mail Transfer Protocol (SMTP) connection details specific to their organization. These settings are used in conjunction with the Send an Email output connector and should be configured by the organization's system administrator or IT department.
The following settings are available under the SMTP Settings section:
- Default SMTP authentication—The authentication method used to connect to the SMTP server (Anonymous, SSL, or TLS).
- Default SMTP password—The password to present to the server if the authentication method requires credentials.
- Default SMTP port—The port number of the SMTP server.
- Default SMTP server host—The host name, or address, of the SMTP server.
- Default SMTP user name—The username to present to the server if the authentication method requires credentials.
Spatiotemporal big data store settings
The Spatiotemporal Big Data Store Settings section defines the default settings when creating spatiotemporal big data store data sources. The values can be changed on the publishing dialog box in GeoEvent Manager.
The following settings are available under the Spatiotemporal Big Data Store Settings section:
- Default Number of Shards—The default number of shards into which a spatiotemporal big data store's data is divided. It is recommended that you set this value to the number of nodes in a spatiotemporal big data store cluster; however, it should never exceed the number of nodes. Acceptable values range from 1 to n, with a default value of 3.
- Default Replication Factor—The default replication factor used when publishing to the spatiotemporal big data store. Acceptable values range from 0 to n, where n is the maximum number of spatiotemporal big data store machines.
Stream service settings
The Stream Service Settings section allows you to adjust multiple aspects of the stream services connection details and message sizes.
The following settings are available under the Stream Service Settings section:
- Maximum web socket text message size (bytes)—Defines the maximum size (in bytes) that a text message can be when sent through a WebSocket. Text messages larger than this cannot be delivered. Value must be between 1 and 2,147,483,647 (2 GB).
- Related Feature Refresh Interval (seconds)—Defines how often (in seconds) the server should periodically query the feature service to see what features are in the spatial filter. This is applicable when a related feature service is selected when publishing a stream service and a spatial filter is added from the client side.
- Support thread count—The number of threads used to manage all client connections. This provides better isolation so that slow clients do not affect other clients. The more threads used, the more server resources are consumed. Value must be between 1 and 100.
- WebSocket buffer size (bytes)—The size (in bytes) a WebSocket allocates to hold data in transit (data that has been sent, but not read by the receiver). Value must be between 1 and 2,147,483,647 (2 GB).
- WebSocket maximum idle time allowed (seconds)—The maximum amount of time (in seconds) the server keeps idle client connections before disconnecting them. Value must be between 1 and 2,073,600 (24 days).
Viewer settings
The Viewer Settings section allows you to define the basemap used in the Event Viewer available in GeoEvent Sampler and the Geofence Viewer available on the Geofences page in GeoEvent Manager.
The following setting is available under the Viewer Settings section:
Viewer Basemaps—Add map and vector tile services to use as basemaps in connected or disconnected environments.