The GeoEvent Server 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 GeoEvent Server to learn more about adapters and transports.
GeoEvent Server includes the following output connectors:
Add a Feature
Update a Feature
Add a Feature to a Spatiotemporal Big Data Store
Update a Feature in a Spatiotemporal Big Data Store
Send an Email
Write to a CSV File
Write to a JSON File
Write to a GeoJSON File
Send an Instant Message
Publish Text to a UDP Socket
Push Text to an External TCP Socket
Send Features to a Stream Service
Send a Text Message
Push JSON to an External Website
Push GeoJSON to an External Website
Push JSON to an External WebSocket
Push GeoJSON to an External WebSocket
Output connectors available on the ArcGIS GeoEvent Server Gallery include the following:
Send text to ActiveMQ
Azure IoT Hub
Send JSON to Azure IoT Hub
Write to Hadoop
Publish Text to Apache Kafka
Send to KML
Write to MongoDB
Send text to RabbitMQ
Send a Tweet
Looking for a different connector?
If the connectors available do not provide the flexibility you need, you can customize existing connectors or create your own using GeoEvent Manager or develop your own connectors using the GeoEvent Server Software Development Kit (SDK).
See Extending GeoEvent Server to learn more about customizing or developing your own connectors.
Do you have ideas for new output connectors? Post your ideas on the Real-Time GIS space on GeoNet.