Skip navigation
All Places > GIS > Enterprise GIS > GeoEvent > Blog > Author: mpilouk-esristaff

GeoEvent

2 Posts authored by: mpilouk-esristaff Employee

On December 8, 2015, the GeoEvent team has released the update to the FlightAware connector. This is the Release 2 that adapts to the message field order changed by FlightAware. All users should adopt this update as the previous release is no longer functional.

After adding the Verizon Networkfleet input into GeoEvent Server for the first time, it is time to test it. This can be done without waiting for the actual data to come from the Verizon Networkfleet server and it is a good preparation step to ensure that the internal network behind your organization firewall is in a ready state. The UI of the Verizon Networkfleet input should look similar to the illustration below:

NetworkfleetConnector.PNG

 

Highlight the string value next to the URL and copy the string from localhost to the end of the long GUID to the clipboard (e.g. by using ctrl-c on the keyboard).

 

Using a web browser like Google Chrome or Mozilla Firefox, you can simulate data -- Chrome will be used in this example. Launch Chrome then click on the Apps button in the upper left corner.

 

GoogleChrome.PNG

 

If you already have the DHC app then it will show up on the browser. Otherwise click on the Web Store, search for the DHC app, and add it to Chrome.

 

ChromeApps.PNG

 

Click on the DHC app, Chrome will open another browser window. Fill in the DHC input as shown below:

 

ChromeDHC-Networkfleet.PNG

 

- Set the REQUEST to HTTP or HTTPS and POST

- Paste the URL copied from the Verizon Networkfleet input into the input box next to HTTP --  if the HTTP is selected then use 6180 after localhost or 6143 for HTTPS. For HTTPS the browser should accept the certificate from the GeoEvent Server instance otherwise posting will fail.

ChromeDHC-Networkfleet-https.PNG

 

- Set the Content-Type to application/x-networkcar-xml

- Copy the test XML from below into the BODY

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE NetworkfleetMessage SYSTEM "http://www.networkfleet.com/dtd/dataconnect/DataConnect.v2.1.dtd">

<NetworkfleetMessage Type="GPS">

<VIN>WAUG5678901234567</VIN>

<FleetId>6543</FleetId>

<MsgId>1761773890</MsgId>

<MessageTime>2007-10-03 22:42:13 GMT</MessageTime>

<MessageTimeUTF>1191451333</MessageTimeUTF>

<DeliveryStatus>Current</DeliveryStatus>

<GPSFixes NumFixes="1">

<GPSFix>

<FixTime>2015-1-15 22:42:13 GMT</FixTime>

<FixTimeUTF>1191451333</FixTimeUTF>

<Latitude>39.87545</Latitude>

<Longitude>-119.41060</Longitude>

<Ignition>On</Ignition>

<Speed Type="Avg" Units="MPH">12</Speed>

<Speed Type="Inst" Units="MPH">15</Speed>

<Speed Type="Max" Units="MPH">27</Speed>

<Heading>224</Heading>

<Odometer>94068.528</Odometer>

<AgeInMiles>0.012</AgeInMiles>

</GPSFix>

</GPSFixes>

</NetworkfleetMessage>

 

Before clicking the Send button, open another Chrome window and log in to GeoEvent Manager and navigate to the Monitor page. Click Reset Statistics to make sure all the counts are set to 0 and ensure the Verizon Networkfleet input is started. In the DHC app, click Send.

 

GEP-Monitor.PNG

NetworlfleetCounter.PNG

 

If all goes well the DHC app will show 200 OK response and the Verizon Networkfleet input count will increase on the Monitor page in GeoEvent Manager.

 

DHCresponse.PNG

NetworlfleetCounter1.PNG

On the DHC app, click the Send button a few more times and notice the Verizon Networkfleet input count increases each time. To test the data flow through GeoEvent Server, create a GeoEvent Service which includes the Verizon Networkfleet input as well as an output such as Write to a JSON File which you can then inspect the content of the file after sending a few more message from the DHC app.

 

Repeat this same test on another computer to verify GeoEvent Server is able to receive the data from other machines. For this, you will need to replace localhost with the actual machine name of the GeoEvent Server instance in the posting URL in the DHC app. If the count values for the Verizon Networkfleet input in the GeoEvent Manager's Monitor page increases after sending more data from the DHC app, then you are successfully configured. If not, first check the firewall rules on the GeoEvent Server instance and ensure communication on port 6180 or 6143 is allowed. If those ports are allowed but you are still not receiving data, there may be other factors related to your network configurations and rules within your organization that may be preventing the data to communicate between machines. In this case, reach out to your organizations network/IT person for assistance.