BUG-000120621 for ArcGIS GeoEvent Server

Bug ID Number	BUG-000120621
Submitted	March 7, 2019
Last Modified	June 5, 2024
Applies to	ArcGIS GeoEvent Server
Version found	10.6.1
Operating System	N/A
Operating System Version	N/A
Status	Known Limit

Additional Information

There are a variety of factors which impact whether a client web application can successfully subscribe to a stream service, including but not limited to: • Single machine deployment vs. two-machine deployment • Correct configuration of SSL certificates on the server(s) • Federating the ArcGIS Server beneath which GeoEvent Server is run with an Enterprise portal • Use of AGS service folders vs. root folder of REST Services Directory • Using AGS Server Manager to secure the AGS service folder and/or stream service • Use of ArcGIS Server built-in users and roles vs. Web Tier / Active Directory user authentication • Assigning ownership of a stream service to an ArcGIS Enterprise portal named user To simplify deployments whose solutions leverage GeoEvent Server and where stream services are an important part of the solution, the recommendation is to *not* There are a variety of factors which impact whether a client web application can successfully subscribe to a stream service, including but not limited to: • Single machine deployment vs. two-machine deployment • Correct configuration of SSL certificates on the server(s) • Federating ArcGIS Server beneath which ArcGIS GeoEvent Server is run with an Enterprise portal • Use of ArcGIS Server service folders vs. root folder of ArcGIS REST API Services Directory. • Using ArcGIS Server Manager to secure the ArcGIS Server service folder and/or stream service • Use of ArcGIS Server built-in users and roles vs. web-tier/Active Directory user authentication • Assigning ownership of a stream service to an ArcGIS Enterprise portal named user To simplify deployments whose solutions leverage ArcGIS GeoEvent Server and where stream services are an important part of the solution, the recommendation is to not federate ArcGIS Server beneath which ArcGIS GeoEvent Server is running with an Enterprise portal. This is only possible in a two-machine deployment in which the base ArcGIS Enterprise is deployed to one machine, and a second ArcGIS Server with ArcGIS GeoEvent Server is deployed to a second machine. The second ArcGIS Server is licensed using only an ArcGIS GeoEvent Server license, limiting its role in the deployment. Ensure the server connection registered as 'Default' is an 'ArcGIS Server' type connection in ArcGIS GeoEvent Manager, and use this 'Default' connection to publish stream services. Single machine deployments in which ArcGIS Server beneath which ArcGIS GeoEvent Server is running with is licensed as both a GIS Server (allowing it to support an Enterprise portal as a hosting server) and ArcGIS GeoEvent Server. In this case, the server connection registered as 'Default' is an 'ArcGIS Enterprise' type connection and this connection can be used to publish stream services. Publishing stream services to Enterprise portal content item folders created using the ArcGIS Enterprise content manager is not supported. Publishing to ArcGIS Server services folders created by ArcGIS Server Manager in the REST Services Directory works, but the best practice is to use the REST Service Directory’s root folder.