Numéro d’ID de bogue |
BUG-000087538 |
Envoi | May 8, 2015 |
Dernière modification | April 2, 2025 |
S’applique à | ArcGIS for Server |
Version trouvée | 10.3 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 2012 64 Bit |
Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
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
https://geonet.esri.com/community/gis/enterprise-gis/geoevent/blog/2016/08/15/geoevent-portal-integration-considerations
Solution de contournement
Workaround 1:
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).
Workaround 2:
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.
Étapes pour reproduire
ID de bogue: BUG-000087538
Logiciel: