POST
|
If you're using ArcGIS Enterprise 11.1 or newer you have access to Feature Service webhooks which will function much the same way as the Survey123 webhooks. Instead of a new survey triggering the webhook, a new feature being created would trigger the webhook. You can use Make.com or pretty much any webhook receiver as long as your Enterprise can send information beyond your network. The biggest difference between S123 and Ent-FS webhooks is you'll need to set everything up yourself in Make. There is no out of the box connectors in Make for the Ent-FS webhooks; you'll need to use the Webhook connector in make, get the webhook URL, and then in ArcGIS Administrator directory you'll add this URL as the payload URL while making the webhook.
... View more
3 weeks ago
|
0
|
0
|
69
|
POST
|
If you navigate to: https://sever/webadaptor/admin/system/properties Click Update Enter the following JSON (or append it) {"isWebhooksEnabled":false} You'll need to restart GIS Server. This will prevent it from trying, thus no logs.
... View more
4 weeks ago
|
0
|
0
|
124
|
POST
|
Something else comes to mind now that I read your upgrade path a bit closer. Just so I understand, you had 11.1 (no observed errors), then upgraded to 11.2 (now seeing errors). Are you using feature or geoprocessing webhooks? If not, I can give you the switch to disable them and it'll stop trying to recover webhooks, thus you won't see any errors. Otherwise, I think it's an issue logged recently (give this to your tech support analyst: BUG-000164209).
... View more
4 weeks ago
|
0
|
0
|
130
|
POST
|
The most common reason you see these errors are due to a closed port between the ArcGIS Server(s) and ArcGIS Data Store machine. Can you verify 45671 and 45672 are open?
... View more
4 weeks ago
|
0
|
0
|
137
|
POST
|
I'll see if I can find someone on the team who can confirm the details (base64, sha256, etc). One thing - the payload body you're using, have you encoded it? Does it have any special characters or anything?
... View more
4 weeks ago
|
0
|
1
|
165
|
POST
|
I'd turn debug logs on in the server. Perform your feature service action (add feature), and then check the logs. You should see messages specific to webhooks. Based on your explanation it sounds like you will NOT see the webhook dispatched message. But you might see errors or other log messages that could be helpful.
... View more
a month ago
|
0
|
1
|
82
|
POST
|
I don't work on Monitor webhooks, but from your description of the SHA256 X-esrihook-Signature, it sounds like it's implemented the same as other Esri webhooks (feature service for example). The answer of "how" you validate in the receiver largely depends on the receiver itself. If you're using Power Automate or Make or some commercial receiver, you'll need to investigate what methods they have available. The basic approach is to build up a string by adding: sha256= to the calculated encoded payload body using the sha256 hash. This provides the calculated signature that you can compare to the X-esrihook-signature. The follow Python code represents how to do this. (myKey is a variable hardcoded into the script that matches the key you used in the webhook creation) import hashlib
import hmac
import base64
encodeKey = str.encode(myKey)
signature = 'sha256=' + base64.b64encode(hmac.new(encodeKey, payload,
digestmod=hashlib.sha256).digest()).decode()
if signature == xsigHash:
return True
else:
return False
... View more
a month ago
|
1
|
0
|
224
|
POST
|
Sync is not currently supported with ArcGIS Enterprise Hosted Feature Service webhooks. We have an enhancement to add support. However, adding this level of support comes with some technical challenges, as such, I can't offer any sort of timeframe of when/if we'll achieve this.
... View more
03-21-2024
05:38 AM
|
0
|
0
|
166
|
POST
|
The Survey123 connector is not part of the new Enterprise connectors (this is why you don't see it mentioned). You can see the high level "buckets" in Power Automate where S123 is it's own entity. I'm not on the Survey123, nor the team developing the Enterprise connectors (I come from core webhooks in Enterprise), so at the risk of saying something incorrect, my understanding is the S123 connector is hardwired to connect to ArcGIS Online and will only find surveys in there, thus they cannot use this connector for Enterprise. Looking at your guide - you have specific instructions on an Enterprise connection to S123: I've never seen this before, and I don't see it now while looking through PA. Perhaps my knowledge is out of date, or my subscription doesn't have the correct access. Apologies if I've posted some incorrect information. Please do correct me if I'm wrong.
... View more
02-20-2024
08:09 AM
|
0
|
3
|
290
|
POST
|
This is a difficult question to answer, but simply, you shouldn't see any impact on the feature layer because of the webhook traffic. After the edit is performed, the information for the webhook is processed in a separate process from the feature layer. The feature layer doesn't become locked, or wait for the webhook to finish. Is it possible this many edits could cause the webhook process to degrade? Maybe? Probably not? Again, a very difficult question to answer without actually benchmarking it (I do not have metrics like these). You can't control the ArcGIS Online processes that do this. What you do have control over is where the webhook is being sent to, which is either a commercial vendor or your own custom service -- does this process scale and handle a lot of webhooks? You might want to try and reduce the number of webhooks being dispatch which would reduce load everywhere. Take a look at the scheduleInfo parameter when you create your webhook. By increasing the frequency, more edits will be grouped into a single webhook. However, as-is, you shouldn't really expect more than 2 webhooks dispatched every minute (based on the 30 second default). That means you could have 3 edits or 10,000 edits in a single 30 second time period, it'll only ever be 1 webhook. {
"name":"Every-30seconds",
"startAt":"1478280677536", //Integer
"state":"enabled",
"recurrenceInfo": {
"frequency":"second",
"interval":30
}
}
... View more
02-20-2024
07:34 AM
|
1
|
1
|
167
|
POST
|
Unfortunately feature service webhooks are not available in ArcGIS Enterprise 10.8.1. They were added in 11.1 The suggestion to use the Survey 123 webhook could possibly work if that made sense for your workflow: using a survey to submit a record. Otherwise, you don't really have any options in 10.8.1 Enterprise to listen for new features short of deploying a custom server object interceptor (SOI) Edit -- I missed the fact this was posted to the Survey 123 community, so I'll guess that you are indeed using Survey123. Without testing myself, I believe this should be possible. The connectors in Power Automate are great: they make it really easy to setup connections, but almost everything those connectors provide could be manually setup. Inside Power Automate, if you start your Flow with When a HTTP request is received -- this listens for incoming webhook payloads. Save your flow, you'll get a webhook URL, copy that, and then manually add it into the Survey123 webhook payload URL. After that you'll need to build out the logic in Power Automate to parse the respond and get the information you're after.
... View more
02-20-2024
07:16 AM
|
1
|
5
|
302
|
POST
|
Hi - Unfortunately at this time, only the Organization webhooks can be sent directly to Notebook Server. Enhancing Enterprise Feature Service webhooks so they can direct payloads to Notebook Server is on our roadmap, however I cannot predict when we'll implement this functionality. You've identified the middle-ware workaround of sending to Power Automate or Make and having them send off the request to the notebook. Alternatively, if you've exposed your Notebook as a WebTool, you might be able to direct the webhook to this endpoint. I'm mostly confident that the webhook would trigger the tool (notebook), the problem becomes getting the payload contents which I don't believe can be handled. So if the notebook could go and do something without information from the payload, this might be a solution for you?
... View more
01-30-2024
10:13 AM
|
2
|
0
|
138
|
POST
|
What type of Feature Service are you using? If you're using ArcGIS Enterprise with a referenced feature service (your data is coming from an Enterprise Geodatabase): yes, the server generation numbers are time based as you mention. If you're using a hosted feature service (same for both Online and Enterprise), the server generation numbers are incremented through transactions, but have no relationship to actual time values. To the best of my knowledge, the values for a hosted feature service are only "refreshed" (incremented) any time an edit happens. Assume your feature service had 0 edits over a 12 hour period: the values should not increase. Contrary, if you had hundreds of edits in the same time period, you would see a large jump between numbers.
... View more
12-11-2023
12:02 PM
|
0
|
1
|
325
|
POST
|
A few questions? What version of ArcGIS Enterprise are you using? Are you using Organization or Feature Service webhooks? Some background information: Organization webhooks do not use the challenge/hash method as referenced in the help link. They use a straight keyword which is included in the payload that the receiver can use to decide if the payload is trustworthy. Enterprise Feature Service webhooks made use of the same pattern as the Org webhooks in 11.0 (Beta) and 11.1. That is, the keyword sent in the payload. Beginning at 11.2 (just released), the Enterprise Feature Service webhooks were updated to match Online Feature Service security model, sending a signature hash in the header based on a given keyword/payload itself. This update matches the security model your referenced in the doc. For Enterprise Feature Service webhooks, you can see the doc note here indicating this change happened in 11.2: https://developers.arcgis.com/rest/enterprise-administration/server/create-webhook.htm As you said you're using Flask (Python), if you want some code that does the CRC/Hash/Signature workflow, you can see the code I have here: https://github.com/Esri/webhooks-samples/blob/master/Developer/azure/function.python/Hook/__init__.py and https://github.com/Esri/webhooks-samples/blob/master/Developer/azure/function.python/Hook/hash_check.py - This code was developed for Online Feature Service webhooks, but you pull the functions out, putting them into Flask and applying them to Enterprise 11.2 Feature Service webhooks
... View more
11-14-2023
06:56 AM
|
0
|
0
|
293
|
POST
|
Today, ArcGIS Online does not support Organization webhooks (as found in Enterprise). Online supports webhooks on Feature Services and Survey123. I know they have this request officially logged (I cannot find the tracking reference right now). As far as I know, there is no planned date date to implement Organization webhooks in Online; it's still in the research phase.
... View more
11-14-2023
06:43 AM
|
0
|
0
|
141
|
Title | Kudos | Posted |
---|---|---|
1 | a month ago | |
2 | 01-30-2024 10:13 AM | |
1 | 02-20-2024 07:34 AM | |
1 | 02-20-2024 07:16 AM | |
1 | 01-03-2013 10:44 AM |
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|