ArcGIS GeoEvent Server can send event data it has received to a variety of destinations. An output connector must recognize the communication channel over which it will send the data and be able to translate the GeoEvents to an expected format. These tasks are managed by adapters and transports—technical implementations beneath each and every connector.
See Extend GeoEvent Server to learn more about adapters and transports.
Output connectors
GeoEvent Server includes the following output connectors:
| Output types | Output connectors |
|---|---|
ArcGIS Server | |
File | |
Instant message | |
Kafka | |
Socket | |
Text message | |
Web | |
WebSocket |
Output connectors available on the ArcGIS GeoEvent Server Gallery include the following:
| Output types | Output connectors |
|---|---|
ActiveMQ | Send text to ActiveMQ |
GeoMessage | Send GeoMessage |
MQTT | Push CSV to an External MQTT Message Broker Push JSON to an External MQTT Message Broker Push XML to an External MQTT Message Broker |
RabbitMQ | Send text to RabbitMQ |
Other output connectors
If the available connectors 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 Extend GeoEvent Server to learn more about customizing or developing your own connectors.
If you have ideas for new output connectors, post them on the ArcGIS GeoEvent Server Ideas place in the Esri Community.