Skip to main content

Configuring Remote Report Execution Host for Azure App Service Deployments

  • Updated

Configuring Remote Report Execution Host for Azure App Service Deployments

When Exago is deployed as an Azure App Service, some additional configuration is necessary. At a high level, these configuration steps are:

  1. The Exago Scheduler Service must be installed and properly configured on an Azure Virtual Machine. Exago v2019.1.5+ must be installed for both the Azure App Service and the Virtual Machine, and the version numbers must be the same.
  2. On the Azure App Service installation, enable the Scheduler and Remote Execution.
  3. Enable Exago’s Puppeteer image rendering libraries on the Azure Virtual Machine (for versions pre-v2020.1).

Detailed information about each of these requirements follows.

1. Azure Virtual Machine

Exago’s Puppeteer image rendering libraries were introduced in v2019.1.5 of the application. At a minimum, v2019.1.5 must be installed on the Azure Virtual Machine. The version number of the Scheduler Service must match the version number of the Web Application.

Refer to the topics in the Recommended References section below for complete details on the installation and configuration of the Scheduler Service and how to install Exago on a Virtual Machine in Azure.

Recommended References

2. Settings

The Scheduler Service should already be properly installed and configured on the Azure Virtual Machine.

On the Exago installation running as an Azure App Service, there are four parameters in the Admin Console which direct it to schedule and execute reports on the Virtual Machine instead of in the App Service:

  • General > Scheduler Settings > Enable Report Scheduling must be set to True. By default, the value is False.
  • General > Scheduler Settings > Enable Remote Report Execution must be set to True. By default, the value is False.
  • General > Scheduler Settings > Schedule Remoting Host must be set to the virtual machine Scheduler Service’s protocol, host name/IP address and port. (for example http://a.b.c.d:2000)
  • General > Scheduler Settings > Remote Execution Remoting Host must be set the same as Schedule Remoting Host above.

Recommended References

3. Enable Puppeteer pre-2020.1

By default, Exago will use the older WkHtmlToImage libraries for visualization rendering. Therefore, Puppeteer must be manually enabled by adding or changing a key in the virtual machine Scheduler Service‘s eWebReportsScheduler.exe.config file, as shown below:

<appSettings>
	<add key="useWkHtmlToImage" value="false" />
</appSettings>

This file is located in the Scheduler Service‘s installation directory. For example, D:\Exago\ExagoScheduler\eWebReportsScheduler.exe.config.

Recommended References