Workflow Manager Invalid Geoevent Server

3608
1
Jump to solution
05-21-2015 07:58 AM
AllWeatherHeather
Occasional Contributor

Please help! I had a great demo up and running the included geofence based emailing and SMS. Now I see this when I look at the GeoEvent Service...

Any suggestions? A couple notes:

  • JDITESTGIS is listed in the Registered ArcGIS Server list on the Data Stores page and I can validate it
  • GeoEventProcessor is the name of the folder I have the services published in with ArcGIS Server
0 Kudos
1 Solution

Accepted Solutions
AllWeatherHeather
Occasional Contributor

I had a great call Friday with RJ Sunderman and got my GeoEvent Processor all sorted out.

First, renaming and restarting the GeoEvent Service made the error message I described above dissapear, however the email and SMS notifications based on enter my geofences was still not working.

To debug, I created a new cache-out output connector using the default configuration. This new output connector could then be added to different points in the geoevent service to listen to the output that reaches that point.

http://localhost:6180/geoevent/rest/cache/cache-out?f=generic-json

Was used to review the data that was captured by the output connector.

https://localhost:6143/geoevent/admin/cache/cache-out/delete?geoEventDefinitions=*

Allowed me to clear the cache between debug points.

I was able to move the output connector through my model and eventually discovered that the field I was using in the geofence layer to later enrich the data was null, preventing the enrichment from happening. This debugging technique was great for viewing the current state of the geoevent as it flowed though my service.

I was able to fix up my geofence data and get it all going again.

Thanks RJ!

View solution in original post

0 Kudos
1 Reply
AllWeatherHeather
Occasional Contributor

I had a great call Friday with RJ Sunderman and got my GeoEvent Processor all sorted out.

First, renaming and restarting the GeoEvent Service made the error message I described above dissapear, however the email and SMS notifications based on enter my geofences was still not working.

To debug, I created a new cache-out output connector using the default configuration. This new output connector could then be added to different points in the geoevent service to listen to the output that reaches that point.

http://localhost:6180/geoevent/rest/cache/cache-out?f=generic-json

Was used to review the data that was captured by the output connector.

https://localhost:6143/geoevent/admin/cache/cache-out/delete?geoEventDefinitions=*

Allowed me to clear the cache between debug points.

I was able to move the output connector through my model and eventually discovered that the field I was using in the geofence layer to later enrich the data was null, preventing the enrichment from happening. This debugging technique was great for viewing the current state of the geoevent as it flowed though my service.

I was able to fix up my geofence data and get it all going again.

Thanks RJ!

0 Kudos