Updated on 1/17/2020
Version 2019.4
General Information
Direct link to topic in this publication:

You have to pay attention to which SharePoint server you want to access. SharePoint Online has a few limitations in comparison to the On-Premise solution: 

  • The RemoteEventReceiver has to be hosted on port 443
  • The certificate of the RemoteEventReceiver has to be valid because it is not possible to add your own certificates to the Trusted Root Authorities.

All kinds of listed installation locations (local, remote IIS or Azure) are working for SharePoint on-prem and SharePoint Online. RER must be reachable from SharePoint in any case and the certificate must be trusted.

Test the RemoteEventReceiver Connection

To test the RER connection, try to access the RER from the Sharepoint host, you would like to send events. It is accessible in the browser with the following URL: https://HOST/services/remoteeventreceiver.svc
The browser MUST NOT show any certificate issue, otherwise, Sharepoint cannot sent the events sucessfully to the RER.

If your SharePoint is a SharePoint farm then the information below might be of interest to you: 

Usage of a SharePoint Farm

For this to work for multiple WebApplications in a SharePoint farm, the FireStart server has to be configured as follows:

For each WebApplication from which events should be handled by FireStart, create a new string value named <DNS_Name_WebApplication> with the value <DNS_Name_WebApplication; Frontend_Hostname1;Frontend_Hostname2;…;Frontend_HostnameN[;ApplicationServer_Hostname]> under HKLM\SOFTWARE\PROLOGICS\PSA\SharePoint\FarmConfig.

In case events from the application server should be handled as well (e.g. because of a script running on the AS that creates list items), the application server also has to be listed.

Business Entities are mapped to the DNS name of the SharePoint farm or to the name of the web application. The load balancer has to route the SharePoint traffic to the SP frontends.

Previous  |  Next