nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enterprise server referenced feature services webhooks

Hlynur

Hello.

I am trying to create referenced FeatureServices webhooks on our Enterprise server logged in as an admin and following this guide:
Create webhooks—Portal for ArcGIS | Documentation for ArcGIS Enterprise

And I'm already getting stuck on part 2 as when I go an select my relevant referenced FeatureService webhook directory, as when I get a list of all the services on our server under the directory OurServer/admin/services then there are only Mapserver services marked there an no FeatureServices.

So when I do select a Mapserver service, for example directory:
OurServer/server/admin/services/folder/MyService.MapServer

and go to its page then I see that the FeatureServer Extension is enabled, then I scroll further down to click onto create a webhook, I am brought to a directory:
OurServer/server/admin/services/folder/MyService.MapServer/webhooks/create

And that all goes fine and dandy.

So my question is, is it correctly understood here that I shouldn't be seeing FeatureServices in my directory at all and its enough to do as above described to create a FeatureService webhook, and if not then what am I doing wrong and how can I access a FeatureService through the admin interface to create a webhook for it?

What I want to accomplish is that FME Flow picks up on a entry being created/edited within the dataset in a FeatureService and by that kicking off a Flow workspace through an automation.

-Hlynur GISus

Find more posts tagged with

Accepted answers

All comments

KevinHibma

Is you ArcGIS Server using a proxy server to send requests?

Can you try using a different webhook receiver? I like to suggest https://webhook.site - You can create a URL at this site and send webhook messages to it. It's perfect for testing.

Hlynur

Ok dug into the Debug modus on our Enterprise server and see that my service is truly sending hook requests left and right but it fails by giving the error "Failed to connect to webhooks due to missing connection details.". Also I can keep the hook without deleting itself by increasing the interval to 100 from 20.
So now that is left to figure out is why Enterprise server allows me to create the webhook with the connection criteria just to then say that there are connection errors when it should do its job (remember that when I create my hook then at creation it triggers and connects without a hitch to our FME Flow (the other end of this whole ordeal)).
All input greatly welcomed.

-Hlynur

Hlynur

Thanks for this @KevinHibma, will give this a try. Other thing I have noticed is that my webhooks get automatically deleted by the server shortly after I create them. Looked into that and saw that Server can disable webhooks that return too many rejections. Which shouldn't be the case here as hooks that have no activity happening in their respected feature services get removed by our server as well...

KevinHibma

@Hlynur - Perhaps you've already got an answer as it's been a few weeks. However, to explain:

The video you link is for ArcGIS Online Hosted Feature Services. You're using Enterprise, or more specifically, referenced feature services, served from ArcGIS Server, which technically appear as an extension to the MapService as Jake mentions, when viewing them in the ArcGIS Server Administrator. This difference is significant. You won't find webhook administrative pages here in ArcGIS Enterprise (ArcGIS Server). You need to continue managing them from the original link you posted.

To your problem of the webhook not sending a message. There are a few things you can do. First, if you enable debug logs in the Server, then perform an edit on the feature service, you should see debug logs about the webhook process. Look specifically for a messaging talking about webhook dispatched - If you see this message, you know the webhook message was sent and that would infer the problem is with the receiver. If you don't see this message, then there is a problem either with webhooks themselves, or possibly the FS isn't setup correctly to support edit and webhook workflows.

Hlynur

Furthermore I notice that after I log out of the admin account and log in again after a while the webhooks I have created from before have vanished.

Plus when I try the trick shown here at 11:19 (enter admin between rest and serviced in my service in question):
https://youtu.be/D9PMC2yGJbA?si=MWZMEp6vfTsMGo48&t=680

then the page I get is much more poorer than the one shown in the video:

And it is lacking the Webhook section at the bottom, regardless of if I have created one or not.
Hope this gives some insight into what I am doing wrong here...

Hlynur

Thank you for this @JakeSkinner, so then I'm baffled why my process doesn't work. Its a simple Webhook:

Which should basically just kick of a workspace to run on FME Flow when I create, update or delete an entry in the single dataset in the FeatureService. But nothing happens on the Flow end when I do so.

However when I originally connect the Webhook to Flow then the automation there runs of without a glitch by itself (just when it is started originally and nothing after that). So it seems like the two systems are speaking well with each other and the dataset in question is in a feature set on our SDE that has Archiving, Global ID's and Editor tracking enabled.

So Im not sure what Im doing wrong here, any suggestions are very much welcomed.

-Hlynur

jskinner

Hi @Hlynur,

is it correctly understood here that I shouldn't be seeing FeatureServices in my directory at all and its enough to do as above described to create a FeatureService webhook,

Yes, that is correct.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.