geoeventteam-esristaff

Things to consider when migrating from Tracking Server to GeoEvent Processor

Discussion created by geoeventteam-esristaff on Jan 7, 2014
This thread provides several considerations for users to think about who are or will be migrating from ArcGIS Tracking Server to ArcGIS GeoEvent Processor for Server. The 10.1 release was the last release of Tracking Server and users are encouraged to migrate to GeoEvent Processor. This thread is intended to be used as a place for you to post your questions about the migration process so everyone in the Tracking Server community can benefit from the discussion.

There are several differences in terminology between GeoEvent Processor and Tracking Server, but the concepts are similar. Below is a term map that lists Tracking Server terms with the equivalent GeoEvent Processor terms.

Tracking Server (TS) to GeoEvent Processor (GEP) term map:

  • TS Message Definition -> GEP GeoEvent Definition.

  • TS CSV over TCP Generic Input Connection Definition -> GEP Text over TCP input.

  • TS CSV over UDP Generic Input Connection Definition -> GEP Text over UDP input.

  • TS UDP Generic Input Connection Definition -> GEP text over UDP input.

  • TS Datalink -> GEP input

  • TS Custom Datalink -> GEP input based on a custom connector, with or a without a custom transport and/or custom adapter.

  • TS Server Action -> GEP processor within a GeoEvent Service.

  • TS Custom Server Action -> GEP custom processor within a GeoEvent Service.

Outcomes