# Configuring IIS for Exago

This guide covers the IIS configuration details necessary in order to install Exago. First-time users are highly encouraged to use this guide during their installation process. Following these steps in order will reduce the amount of troubleshooting necessary to get Exago running.

1. Install Prerequisites
2. Install Exago
3. Set the Application Pool
4. Set Folder Paths and Permissions
5. Check that the Web Site is Running
6. Open the Admin Console

# Install Prerequisites

Exago runs on Internet Information Services (IIS) version 5.1 or later, and requires Microsoft .NET Framework version 4.5 or later. In addition, Exago requires the following Windows Features to be installed:

- Internet Information Services
  - Web Management Tools
    - IIS Management Console
  - World Wide Web Services
    - Application Development Features
      - .NET Extensibility
      - ASP.NET
      - ISAPI Extensions
      - ISAPI Filters
    - Common HTTP Features
      - WebDAV Publishing

Before installing Exago, please ensure that these features are present on your system. To verify, access the Windows Features panel via Control Panel > Programs > Programs and Features, and click Turn Windows features on or off.

In the Windows Features dialog, expand Internet Information Services and ensure that the prerequisite features are selected. If any are not installed, check the relevant boxes, press OK, then restart the server.

These features are necessary in order for the proper Application Pools to be available.

# Install Exago

At this point, Exago can be installed.

Run the installer and follow the instructions for installing the Exago Host Application.

We do not recommend installing Exago in a managed directory such as the Program Files, Windows, or Users folders. Using one of these file paths can cause permissions conflicts.

Take note of the web site which Exago is installed, and the virtual path.

For a more detailed walkthrough, see Installing Exago on Windows.

# Set the Application Pool

Next, verify that Exago is using a valid application pool.

Open IIS via Control Panel > Administrative Tools > Internet Information Services (IIS) Manager.

In the left-most Connections pane, select the Exago application.

In the right-most Actions pane, click on Advanced Settings...

In this menu, click on the [...] button to the right of the Application Pool.

In the Select Application Pool menu, determine which of the app pools has the properties:

- .Net Framework Version: 4.0
- Pipeline mode: Integrated

Select this app pool, then press OK to close the App Pool menu, and then OK to close the Settings menu.

Next, ensure that the app pool is running. In the left-most Connections pane, select Application Pools.

Check the Status column for your selected app pool.

If does not say Started, select the app pool and in the right-most Actions pane, press Start.

# Set Folder Paths and Permissions

Exago uses Temp and Reports folders to store working data and the reports file system, respectively. Create these folders in locations suitable to your environment.

The Reports folder should not be within the Exago application directory. This could cause timeout errors while using the application.

The Temp folder may contain sensitive report and database information. It should be in a secure location, inaccessible by web users.

Several Exago folders require you to set additional permissions for the application pool user. First, determine the user: Open IIS to the Application Pools pane, and look at the app pool which is running Exago. The Identity property indicates the application user:

By default, this is set to ApplicationPoolIdentity. This corresponds with the built-in user IIS_IUSRS. If this is a different user, then set permissions for that user account instead.

The following folders require the app pool user to have read/write permissions:

- Config
- Temp
- MapCache
- Reports

> NOTE. This process may differ slightly depending on your version of Windows.

First, right-click on the folder and select Properties.

Open the Security tab. Then click the Edit... button.

If the application pool user is not available to select, you need to add it. Press the Add... button.

Then enter the username in the dialog box, and press OK (the default app pool user is IIS_IUSRS).

With the user selected, check the box for Allow Full control. Then press OK.

Repeat this process for every folder listed above.

# Check that the Web Site is Running

Before starting Exago, ensure that the Web Site is running. Open IIS, and in the left-most Connections pane, locate and select the web server under which Exago was installed

Verify in the right-most Actions pane that the Start button is greyed out, and the Restart and Stop buttons are available. If the Start button is not greyed out, press it to start the web server.

Next, in the left-most Connections pane, locate and select the web site under which Exago was installed.

Verify in the right-most Actions pane that the Start button is greyed out, and the Restart and Stop buttons are available. If the Start button is not greyed out, press it to start the web site.

# Open the Admin Console

You're almost done! To verify that Exago was installed correctly, open a web browser and navigate to http://[YourServerAddress]/[YourExagoVirtualPath]/Admin.aspx

If you see the Exago Administration Console, then your installation was successful.

In the Admin Console General Settings, set your Temp and Reports paths to the folders you previously created. Then press OK.

Then navigate to http://[YourServerAddress]/[YourExagoVirtualPath]/ExagoHome.aspx

If you can see the Exago UI, and you have an empty folder/reports tree, then you've set your paths correctly.

Congratulations! You've completed your first Exago installation.

# Additional Notes

We highly recommend Setting up a State Server to handle Exago sessions.

If you are experiencing problems that aren't detailed in this guide, please file a support ticket, and a representative will be happy to help you get set up.