Exago runs on the web server application Microsoft Internet Information Services (IIS). The following sections walk through the installation process for Windows based systems.
See System Requirements to ensure that you have sufficient hardware to run Exago.
Before installing Exago, ensure that IIS is installed and configured correctly. See Configuring IIS for Exago for details. Please refer back to this guide for necessary configuration settings.
Important: If you are upgrading an existing Exago installation, please ensure that the file eWebReportsManifest.txt is present in the install directory. Otherwise, the installer will overwrite any custom config or styling you've applied.
Download the Exago installer from our Downloads page.
Run the installer as an administrator. The installation menu will appear with three downloadable applications. Click the top icon to install the Exago Web Application, as pictured below.
Even though the installer has finished, Exago will most likely not function at this point. You must continue with some additional configuration.
Create the Directory Structure
After the installation is complete, configure Exago using the following steps. (See Configuring IIS for Exago for a more detailed walkthrough).
- Set permissions for the Config folder:
Right click on the folder named "Config" and click Properties.
In the security tab click "Edit" then "Add." Enter the IIS application pool user (default IIS_IUSRS).
In the "Permissions for Config" window select the user that was just created and select "Modify" or "Full Control" permissions.
Repeat this process for the MapCache and Drivers folders.
Caution: If these permissions are not set, an access denied message will appear when trying to add a MongoDB connection string.
- Create a folder for storing reports. This folder needs to be accessible from the web server, but is not required to be on the web server. It can reside on any server accessible by Exago via direct UNC or virtual path created in IIS.
Important: Do not create the reports folder within the Exago application structure. Doing so will cause ASP.NET sessions to crash when report folders are created or deleted within the Exago application.
Give the Report Folder full control privileges for the IIS application pool user. Below are three examples of report paths to the folder \ReportsRepository:
C:\ReportsRepository – Folder is on a file system.
\\Server Name\ReportsRepository – Physical folder is on a separate server.
/ReportsRepository – Assumes an IIS virtual directory called 'ReportsRepository' has been created to point to the folder.
- Create a folder for storing temporary data. By default this is a sub-folder of Exago called 'Temp'. However it is recommended to not use the install path's temp folder in production environments.
Give the Temp folder full control privileges for the IIS application pool user.
- Point your browser to the Administration Console. By default this is http://<YourServer>/Exago/Admin.aspx
Specify the location of the Report Folder in the 'Report Path' setting.
Specify the location of the Temp Folder in the 'Temp Path' setting.
Point your browser to the Home Page to verify that your installation was successful. By default this is http://<YourServer>/Exago/ExagoHome.aspx
At this point you will need to set up your data sources in order to use Exago. See Administration Console Setup to get started.
If you would like to set up Google Maps, GeoCharts, and/or any downloadable Application Themes, please see Installing Optional Features for more information.
- System Requirements - Baseline hardware requirements.
- Configuring IIS for Exago - Necessary config details for IIS.
- Installing the Scheduler Service - Scheduler config info.
- Install and Configure the Web Service - Web service config info.
- Installation Troubleshooting - Common install problems & their solutions.
- Administration Console Setup - Initial data sources setup guide.
- Installing Optional Features - How to set up GoogleMaps, GeoCharts, and Application Themes.