The Push Service is an add-on to the ResourceXpress server. It is an independent Windows Service used to update/sync booking with Exchange/O365 calendars. The benefit of using the Push Service is to reduce the number of requests made from ResourceXpress to the Exchange/O365 environment. Instead of the ResourceXpress server polling every 60 seconds any new bookings or updates are automatically pushed by
the Exchange/O365 server to ResourceXpress via a subscription.
...
Push Service Installation and Configuration
Install and Configure
Step 1: Please contact helpdesk@qedas.com to request the Push Server install files.
| Info |
|---|
This version of Push Service is only compatible with ResourceXpress V5 or above |
Step 2: Navigate to the download directory and run RXNewPushServiceV0.6-install.exe as administrator. Choose an installation directory or leave as default and click Next then Install and Finish.
Step 3: Navigate to the install directory, by default this will be
...
A more advanced text editor, for example, Notepad++ will offer an easier way of editing the application config files than the built-in server tools such as WordPad or Notepad
Step 4: Edit the required values as detailed in the following table and save the file.
Line | Parameter | Description | Example Value |
|---|---|---|---|
9 | TenantUrl | The ResourceXpress Application Server IP or FQDN. If the Push Service is running on the same server as the main application you can enter http://localhost | or http://<localrxserverFQDN> |
10 | NotificationUrl | The IP or FQDN of the server running Push Service. If Resourcexpress is integrated to a remote Exchange server or O365 this value must be the externally accessible FQDN | or |
11 | UseImpersonation | The value must be true if ResourceXpress connects to more than 20 Exchange resource mailboxes using EWS. | true or false |
12 | ApiKey | The Api key of your ResourceXpress application. | 12345678910abc12def31415 |
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0"?>
<configuration>
<configSections>
</configSections>
<appSettings>
<add key="EwsFrequency" value="5"/>
<add key="EwsFrequencyDelay" value="5"/>
<add key="ProcessSubscriptionInterval" value="1"/>
<add key="TenantUrl" value="http://localhost"/>
<add key="NotificationUrl" value="http://rxserver.domain.local"/>
<add key="UseImpersonation" value="true"/>
<add key="ApiKey" value="12345678910abc12def31415"/>
<add key="UseTLSVersion" value="1.0,1.1,1.2"/>
</appSettings>
<connectionStrings/>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.1"/>
</startup>
</configuration> |
Step 5: Open Windows Services as an administrator. Right-click the RXPushService and start the service.
...
Check the Windows Service RXPushService is running and is set to run automatically
Check the ApiKey value in the Push Service config file matches the ApiKey value in the application web.config file
Ensure the UseImpersonation value is set to true if connecting to more than 20 Exchange mailboxes using EWS
Ensure the Exchange Service Account has the Impersonation Role for ResourceMailboxes in the Exchange Admin Center
Ensure the Push Service server is accessible over the public internet and that the externally accessible URL is configured in the NotificationUrl value of the Push Service config file