Nicinski nailed it but allow me to expand a bit. GeoEvent server is designed to ingest large amounts of info (your truck locations) from numerous sources (probably a db in your case) - Analysis it if you want - then exports it to numerous output types, in your case probably a streaming layer for performance on the JS client.
GeoEvent server is designed to ingest large amounts of info (your truck locations) from numerous sources (probably a db in your case) - Analyze, it if you want - then exports it to numerous output types, in your case probably a streaming layer for performance on the JS client.
Esri has out of the box tools to Ingest your data, store your data and display your data. What it's missing is the collection of your points (They may have this as well).
But, as an example. You could:
-Write a JS client (mandates online always) that sent the user's GPS location to a GeoEvent Server.
-GeoEvent Server then saves the point in a TruckGpsHistory (last hr), TruckCurrentGPS (latest), and a Streaming Layer. The streaming layer provides "real time" updates of your displays.
- You display clients simply use layers ava from published feature classes and the GeoEvent Server Streaming layer.
