Windows environment, Enterprise 10.9.1, Networkfleet connector 10.4 v9
I'm working to get a dashboard going for our snow response team for this winter. I started with a simple workflow (attached as "simple.png") of Networkfleet input to Field Mapper to Feature Service output. This successfully sent all incoming data into the feature service. I then added a Field Enricher, which I have not yet had success with, but the incoming data still flowed into the feature service. I started looking into the Field Enricher problem and found a lot of talk about using a filter on the incoming Networkfleet stream, not as a solution to my Field Enricher problem, but as a means to focus the data stream for specific needs. I decided I would try this to help with some duplication I was seeing in the table.
When I added the gps or gps-flat definition filters, my output stopped. I decided to try creating filters for all of the -flat Networkfleet definitions, with a JSON output for each, and an unfiltered JSON output (service screenshot attached as "vnfFiltering.png", sample output attached as "unfiltered2021_10_20.txt"). The unfiltered output is the only file receiving data; none of the filters are working. There are no errors in the logs associated with this (logs.png).
I also tried this from the connector documentation and came up empty:
Logging Configuration
- Use com.esri.geoevent.adapter.networkfleet.NetworkfleetMessageTranslator at the DEBUG level to see incoming XML and outgoing GeoEvent log messages. These messages can be used to determine if the Verizon Networkfleet Adapter is:
- Receiving XML messages from Verizon Networkfleet
- Parsing the XML correctly into GeoEvents
- Use com.esri.geoevent.adapter.networkfleet.NetworkfleetInboundAdapter at the DEBUG or TRACE level to see all other log details.
- DEBUG will show how the XML is being interpreted from the transport.
- TRACE will show all logical steps in the adapter.
