Any feature output connector in ArcGIS GeoEvent Extension for Server fails to list ArcGIS GIS Server services when federated with Portal for ArcGIS.
Last Published: May 15, 2017ArcGIS for Server
Bug ID Number
May 8, 2015
May 31, 2023
ArcGIS for Server
Operating System Version
2012 64 Bit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
This issue was a known limitation in the 10.3.x releases of the Geoevent Extension that did not yet fully support federation with Portal for ArcGIS. This behavior was addressed with the 10.4.x releases and required that the DEFAULT data store connection be a Portal type connection. If federation occurs after installing the GeoEvent Extension it will require resetting the GeoEvent Configuration to detect the correct connection type.
For additional information regarding GeoEvent and Portal federation please see the following article:
GeoEvent & Portal Integration Considerations
In GeoEvent Extension's Data Store, register the same 'default' server as a new 'Server' connection with the 'Use Token' option enabled (so it passes Portal Token for Authentication).
1. If working with a federated server, make it a hosted server.
2. Publish services to the hosted server.
3. Register ArcGIS GIS Server again with ArcGIS GeoEvent Extension for Server, and the services under 'Hosted' folder are displayed in the list.
Workaround 3: Unfederate ArcGIS GIS Server with Portal for ArcGIS.