ArcGIS 10.3.1 GeoEvent Server Patch 2

This is a general cumulative maintenance patch for ArcGIS 10.3.1 GeoEvent Server (Windows and Linux). Please download and install this patch at your earliest convenience.

• Enhancements and Issues Addressed with this Patch
• Files Installed with this Patch
• Installing this Patch on Windows
• Installing this Patch on Linux
• Patch Updates
• How to identify which ArcGIS products are installed
• Getting Help

 

Notes

 

• Clearing the browser cache will be required after this patch is installed to properly load the updated GeoEvent Manager User Interface.
• Depending on your product configuration you may need to ensure your inputs, outputs, and GeoEvent Services are started by using the ArcGIS GeoEvent Manager. If they are not started, you will need to manually restart them in the ArcGIS GeoEvent Manager.
• ArcGIS 10.3.1 GeoEvent Server must be installed before you can install this patch.

 

Enhancements and Issues Addressed with this Patch

Note: This patch is cumulative of previously released Patches and Hotfixes.

This issue was integrated into the code base at 10.6.1.

• BUG-000114349 - ArcGIS GeoEvent Manager fails to load in Chrome 67.

This issue is was included from 10.3.1 Patch 1 Hotfix 1 and integrated into the code base at 10.4.

• BUG-000100874 - GeoEvent data is being corrupted randomly when received using a ‘Receive CSV on REST’ input connector.

These issues were included from 10.3.1 Patch 1 and integrated into the code base at 10.4.1.

• Bug-000095066 Unable to change Active status of GeoFences.
• Bug-000094461 Synchronize GeoFences rule does not retain the changes made to the GeoSync filter field value in edit mode.
• Bug-000094460 GeoFence Synchronization does not update GeoFences which have been expired when a GeoSync Filter is specified.
• Bug-000094456 GeoFence Synchronization does not issue standardized queries required by ArcGIS Server to support different types of databases while querying for GeoFences.
• Bug-000094455 GeoFence Synchronization does not accommodate queries in which the END_TIME is NULL.

These issues were included from 10.3.1 Patch 1 and integrated into the code base at 10.4.

• Bug-000092043 In a federated ArcGIS for Server and Portal for ArcGIS environment, GeoEvent Manager doesn't allow users to login to environments which utilizes a DNS name for their Portal site.
• Bug-000091652 GeoEvent stream service output fails to restart after a Data Store Server connection is interrupted.
• Bug-000090104 GeoEvent is unable to retrieve layer information when using a registered data store connection to Portal for ArcGIS configured to use Integrated Windows Authentication.
• Bug-000089145 Generic JSON adapter stops working if it receives more than one message in 100 milliseconds.
• Bug-000089619 Outbound UDP Transport is not sending GeoEvents.
• Bug-000088127 GeoTagger processor does not recognize the newly synchronized GeoFences.
• Bug-000088532 GeoEvent feature service output fails to restart after a Data Store Server connection is interrupted.

 

Files Installed with this Patch

• agsconnection-datastore-10.3.1.jar
• arcgis-stream-container-10.3.1.jar
• generic-json-adapter-10.3.1.jar
• geotagger-processor-10.3.1.jar
• httpclient-10.3.1.jar
• i18n-support-10.3.1.jar
• internal-aoimanager-10.3.1.jar
• jms-messaging-10.3.1.jar
• messaging-api-10.3.1.jar
• udp-transport-10.3.1.jar
• text-adapter-10.3.1.jar
• webapp-10.3.1.war

 

Installing this Patch on Windows

 

Installing this Patch on Linux

Patch Updates

How to identify which ArcGIS products are installed

Getting Help

Download ID:7618