I just updated Geoevent to 10.7.1 hoping to improve overall stability issues. After the upgrade my Networkfleet input no longer worked. When I tried to create a new input it advances to the Create Input screen but the page is blank. The system logs show quite a few error messages that dont really make sense to me. I will attach a screen shot.
I have tried restarting services and server itself with no luck.
Hey Cassidy,
We updated our release process, so there are some extra steps that you have to go through to upgrade to the new Networkfleet Connector. The steps should be detailed in the release documentation, so I encourage you to read through the upgrade sections there. Here's a brief overview of the steps below.
The new Networkfleet Adapter is released with a version of 10.4.0. This indicates the adapter is compatible with all versions of GeoEvent 10.4 and later (this is the change in process that we made).Because the version is changing on the .jar you are deploying you must do the following:
1. In GeoEvent Manager, go to Site > GeoEvent > Connectors and edit the Networkfleet Connector. Ensure that it is using the Networkfleet Adapter and the HTTP Transport. Press Save (you must save it so it updates to the new adapter).
2. Go to Services > Inputs and add a new Networkfleet input. The dialog to create a new input should display the properties correctly.
Best, Eric
Thanks Eric. I have gone through the 10.4 documentation that you have outlined above. When I create the new input it does not receive any data. Once I renamed the input to the old name it started working. I can see the data pass all the way through the stream output in the monitor but nothing is showing up in a map. I think this all ties back to the schema errors I mentioned in the other post.
I started looking at the data in Logger and it appears that the data coming from Verizon is not consistent but I think some of it should be passing through Geoevent. I will attach a screenshot, but when you look at the data, some of the events are missing the Heading field. Could this be causing the schema problem? I would think the ones in the correct order would make it through to the service?
Hey,
Page 6 in the documentation lists the different message schema you might expect to receive from Networkfleet. In most cases people only get the NetworkfleetGPS messages (but some people get all of them).
You can put a filter between your input and your output (stream service or logger) to filter for only the GPS messages. That will ensure you only pass the GPS messages through.
Another thing you should probably do prior to the stream service is add a new GeoEvent Definition that "flattens" the original NetworkfleetGPS definition (the attached configuration has this definition). If you use the flat definition, you will have to re-create your stream service using the new flat definition.
Use a Field Mapper to map the nested/grouped fields into the flat definition as shown below:
Thanks...I will give this a shot. I currently have the Filter and Field Mapper in place so I will try to flatten it as well and see if that works.
No luck mapping to the flattened schema. When I try to set up the field mapper I do not see the entire speed hierarchy. I am only seeing one set of speed attributes (not GPSFix.Speed[0], GPSFix.Speed[1], etc.)
I have gone back and deleted everything related to Networkfleet in my GeoEvent installation and I still cant seem to get anything to work.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
