Output Connectors
GeoEvent Processor 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 Processor to learn more about adapters and transports.
Output Connectors
GeoEvent Processor 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 TCP socket Publish text to a UDP socket |
Text message | Send a text message |
Web (including KML and RSS) | Publish GeoEvents on a REST endpoint Push JSON to an external website |
WebSocket | Publish JSON to a WebSocket Push JSON to an external WebSocket |
Output Connectors available on the ArcGIS GeoEvent Processor Gallery include the following:
ActiveMQ | Send text to ActiveMQ |
Hadoop | Write to Hadoop |
MongoDB | Write to MongoDB |
Send a Tweet |
Esri Partner-contributed Output Connectors available on the ArcGIS GeoEvent Processor 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 Processor Manager.
See Extending GeoEvent Processor to learn more about customizing connectors.
Do you have ideas for new Output Connectors? Visit ArcGIS Ideas, tag the ideas with geoevent processor, and choose the ArcGIS Server category when posting.