I am trying to compile the Reverse Geocode Processor from github. I can get it to compile fine in maven, but when I place it in the deploy folder (or use the UI in manager), it doesn't show up in the list of available processors.
I have downloaded the pre-compiled versions from the ESRI website, and only the 10.3 version seems to work when I deploy it. We would like to use the one from Github so that we could update the code to use our internal Geocoder instead of the ESRI World geocoder.
We are using GeoEvent for ArcGIS 10.4.1 Server. Any help would be greatly appreciated.
Thanks,
Shawn
Solved! Go to Solution.
It appears that somehow my dev machine (separate from the production/deployment server) had a mismatch somewhere. It said I had ArcServer 10.4 with GeoEvent installed. But on a whim, i tried downloading the 10.3.x branch of the GitHub project. When i compiled it and deployed to GeoEvent (deploy folder), it worked fine.
Thanks to everyone for the advice and great tips! Very useful info. Now all i have to do is tweak the code to use our geocoder instead of the ESRI world geocoder and I'm all set.
Thanks everyone!
You might want to try submitting an issue with the GitHub project - Issues · Esri/reverse-geocoder-for-geoevent · GitHub I'm not sure if the devs are looking at the Geonet forums.
Yeah, I've tried to submit an issue there as well, but I haven't heard anything yet. Just trying to cast a wide net hoping between the two sites that someone will know something. But I appreciate the help and guidance
-Shawn
Hi Shawn,
I just built it for 10.4.0 and deployed on an instance of GeoEvent 10.4.1 and it showed up just fine. I also built and tested deploying version 10.5.0 without any problem.
I would suggest to check the Log page on GeoEvent Manager. In my case the Log entries were as shown in the screen shot below.
And the Reverse Geocoder Processor showed up on the list of Processors under the Site/Components page.
If you obtained the jar that built from another machine, make sure to do a 2-step copy of the jar to get around the OS file permission. I normally do this by copying the new jar to my Desktop folder first then copy it in the next step from the Desktop folder to the <geoevent>\deploy. When in doubt, stop GeoEvent Windows service and empty out the <geoevent>\data folder to clear all the old jar caches then restart GeoEvent Windows service.
Hope this helps,
Morakot
It appears that somehow my dev machine (separate from the production/deployment server) had a mismatch somewhere. It said I had ArcServer 10.4 with GeoEvent installed. But on a whim, i tried downloading the 10.3.x branch of the GitHub project. When i compiled it and deployed to GeoEvent (deploy folder), it worked fine.
Thanks to everyone for the advice and great tips! Very useful info. Now all i have to do is tweak the code to use our geocoder instead of the ESRI world geocoder and I'm all set.
Thanks everyone!