Event-Driven Services
Generic Event Notification Service
The generic event notification service asynchronously processes HTTP messages from varying sources sent over SSL, converting the HTTP request body to an input message property within your integration.
To use the generic event notification service
1. Configure your notification emitter to POST securely over SSL to the following endpoint URL (where {provisioningid} is the ID of the configuration that you would like to execute):
https://notifications.pervasive.com/notification/provisioning/{provisioningid }
2. Include the following custom HTTP request headers in your request:
• dcuid – The DataCloud username you would like to use to log in to DataCloud.
• dcpwd – The password associated with the username.
Note: The DataCloud will only accept notifications over SSL, so the transport will be secure, but you should take measures to ensure your method of creating the messages is also secure.
A successful response will contain two interesting HTTP response headers:
• dcurl: The version of the API that is currently being used.
• dcuuid: The unique identifier for the execution that was submitted.
Sample Request
POST https://notifications.pervasive.com/notification/provisioning/12345 HTTP/1.1
Accept-Encoding: gzip,deflate
Accept: null
Content-Type: text/xml
dcpwd: password
dcuid: username
User-Agent: Jakarta Commons-HttpClient/3.1
Host: notifications.pervasive.com
Content-Length: 69
Sample Response
HTTP/1.1 200 OK
Content-Type: text/plain;charset=UTF-8
Date: Tue, 04 Dec 2012 19:35:53 GMT
dcurl: https://datacloud2.pervasive.com/EntityAPIService/EntityAPIWebService
dcuuid: 12345678-1234-abcd-efgh-1234abcd5678
Server: Apache-Coyote/1.1
Content-Length: 1
Connection: keep-alive
Last modified date: 12/17/2021