Output Connectors
In this topic
The GeoEvent Extension is capable of sending event data it has received to a variety of different destinations. An Output Connector must know about the communication channel over which it will be sending the data and be able to translate the GeoEvents to an expected format. These tasks are handled by adapters and transports—technical implementations beneath each and every connector.
See Extending the GeoEvent Extension to learn more about adapters and transports.
Output Connectors
The GeoEvent Extension includes the following Output Connectors:
ArcGIS Server | Add a Feature Update a Feature |
Send an Email | |
File | Write to a CSV File Write to a JSON File |
Instant message | Send an Instant Message |
Socket | Publish Text to a UDP Socket Push Text to an External TCP Socket |
Send Features to a Stream Service | |
Text message | Send a Text Message |
Web (including KML and RSS) | Push JSON to an External Website |
WebSocket | Push JSON to an External WebSocket |
Output Connectors available on the ArcGIS GeoEvent Gallery include the following:
ActiveMQ | Send text to ActiveMQ |
Hadoop | Write to Hadoop |
KML | Send to KML |
MongoDB | Write to MongoDB |
Send a Tweet |
Esri Partner-contributed Output Connectors available on the ArcGIS GeoEvent Partner Gallery include the following:
AGI * | Send to Cesium |
* This Output Connector is coming soon.
Looking for a different connector?
If the connectors available do not provide the flexibility you need, you can customize the connectors using the GeoEvent Manager or develop your own connectors using the GeoEvent Extension Software Development Kit (SDK).
See Extending the GeoEvent Extension to learn more about customizing or developing your own connectors.
Do you have ideas for new Output Connectors? Visit ArcGIS Ideas, tag the ideas with GeoEvent, and choose the ArcGIS Server category when posting.