Geocortex Reporting Help

Open topic with navigation

Install Geocortex Reporting in a Load-Balanced Environment

A typical Geocortex Reporting deployment consists of one server that hosts both the Reporting software and its data directory. This deployment case is suitable for most installations and can be installed and updated out of the box.

Alternatively, you may prefer to install Geocortex Reporting in a multi-server environment.

In a multi-server Geocortex Reporting deployment, each server operates independently to generate report content. This means that users can still generate reports if one server fails, and that servers do not share job information with each other.

All servers share a single copy of the Reporting data directory. For Geocortex Reporting, you need to set up a redundant file share for the data directory. This provides redundancy for Reporting's configuration files and any temporary files.

A redundant multi-server deployment of Geocortex Reporting

Prerequisites

To run Geocortex Reporting in a load-balanced environment, ensure the following requirements are met:

• You have a load balancer.

• Your load balancer does not rewrite URL paths.

• You have enabled sticky sessions on the load balancer.

  Sticky sessions (also known as 'session affinity' or 'session persistence') must be enabled on the load balancer. When sticky sessions are enabled, all requests from a client are routed to the same server for the duration of that client's session.

Installation Steps

The main installation steps for a load balanced deployment of Geocortex Reporting are the same as for a typical on premises deployment, with some exceptions and additional steps—described on this page.

The installation steps are as follows:

1. Set up file share. See Set Up File Share, below.

2. Install Geocortex Reporting:

   1. On the on-premises installation deployment page, see Install Geocortex Reporting.

   2. On each server, follow all steps as for a typical on-premises installation.

3. Configure post-installation settings:

   1. On the on-premises installation deployment page, see Configure post-installation settings.

   2. On each server, follow all steps as for a typical on-premises installation, with the exception of the Data and Portal sections.

   3. Complete Data configuration: See Data, below.

   4. Complete Portal configuration: See Portal, below.

4. Configure load balancer. See Configure load balancer, below.

Set Up File Share

Set up a redundant file share for the data directory. The file share will be shared between all servers, providing redundancy for Reporting's configuration files and any temporary files.

To set up the file share:

1. Find your existing file share, or create a new one.

   We recommend that you choose a permanent location for the data directory file share now. If you change the data directory location later, you will lose access to your existing reports.

2. Within the file share, create a folder for the Geocortex Reporting data.

3. Assign the GeocortexReporting application pool user Read / Write permissions. Typically this is the DomainName\MachineName$ user.

Configure Post-Installation Settings

Data

The Data panel allows you to select a location for Geocortex Reporting to store reports and other Reporting-related files.

• Click Browse and select the file share folder location.

Portal

The Portal panel allows you to register your Portal for ArcGIS or ArcGIS Online application.

Follow the instructions provided for a typical on premises installation, with the exception of the Redirect URL.

• Set the Redirect URL to use the public address of your load balancer.

Configure Load Balancer

• Configure your load balancer to direct traffic to the servers on which Geocortex Reporting is installed.

  Sticky sessions (also known as 'session affinity' or 'session persistence') must be enabled on the load balancer. When sticky sessions are enabled, all requests from a client are routed to the same server for the duration of that client's session.