Hello Jacob -
To the best of my knowledge, no one on the GeoEvent product team has experience ingesting XML from Globalstar's SPOT Commercial Account Data Push service. I did perform a quick test to verify that the XML illustrated below, taken from the sample provided in the SPOT service's PDF, could be received and adapted by GeoEvent using a Receive XML on a REST Endpoint input configured as shown below.
Looking briefly at the service's PDF, it appears that Globalstar supports HTTP, HTTPS, FTP, and SFTP.
GeoEvent will not support FTP / SFTP. The extension generally supports RESTful data streams, not FTP based feeds. (There are inputs capable of watching a system folder for files, but these inputs have some significant limitations and are generally intended to prove that real-time analytics you've designed into a GeoEvent Service behave as you intend. Moving toward production we expect real-time data feeds to arrive via HTTP/POST or as replies to queries you make on an external server's URL.)
Have you tried configuring the SPOT Data Push to provide you its XML data over HTTP? The out-of-the-box input Receive XML on a REST Endpoint introduced with the 10.3 product release should provide you that capability. That input creates a GeoEvent hosted REST endpoint which the external server should be able to reach via HTTP over port 6180 (e.g. http://myserver.domain:6180/geoevent/rest/receiver/name-of-input).
Minimizing your server's exposure to attacks such as Denial of Service should be something we tackle after confirming that XML being posted to GeoEvent can be successfully received and adapted. We want to rule-out, for example, any issues with your organization's firewall which might prevent the SPOT service from reaching the GeoEvent REST endpoint.
In the SPOT service's PDF, beneath the section titled Reducing the security vulnerabilities, I read that the receiver (GeoEvent in this case) can ignore the X-WSSE header information provided by the data feed. Once we confirm that GeoEvent can receive and adapt the XML being sent by the SPOT service, we can look at the possibility of using HTTPS to ensure data encryption and verifying data provided in the X-WSSE header. This may require some custom development on your part using the GeoEvent SDK to create a custom transport which implements the header validation illustrated in Appendix B – Sample Java Code to verify X-WSSE headers section of the SPOT servcie's PDF.
Hope this information helps -