| Page Properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
RessourcesEvent = System Hooks RemarksThis tutorial should eventually replace the System Hooks page in this directory, as the content of that page will be moved to a concept page. Technical Review of Example Webhook Consumer Server needed. |
...
To use the webhook service for the intended purpose of intercepting metadata when updating objects, we need to create a new entry in the Webhook list within our systems' SystemHookConfiguration.json file, whereafter the API gateway (API Service) needs to be restarted. . The url attribute must refer to the webhook service identifier (derived from the artifact ID in the services' maven file) and direct to one of the endpoints declared in the service.
The services responsible for the webhook execution need to be restarted after changing the SystemHookConfiguration.json file. The corresponding services of each webhook are listed here. For the enrichment of metadata, the pertaining Service would be the API gateway.
| Code Block | ||
|---|---|---|
| ||
{
"systemhooks": {
"webhooks": [
{
"enable": true,
"predicate": "spel:true",
"type": "dms.request.update.metadata",
"url": "<your host base url><protocol>://<webhook service identifier>/api/dms/request/update/metadata",
"useDiscovery": true
}
]
}
}
|
...