Scroll

Installing Exago on Linux

The following sections walk through the installation process for Linux based systems.

(Follow this link for Windows Installation)

Supported distros

  • Red Hat Enterprise Linux 7+
  • SUSE Linux Enterprise Server 12+
  • CentOS 7+
  • Fedora 21+
  • Debian 8+
  • Ubuntu 14+

Requirements

  • Apache 2.4+ or Nginx
  • mono 4.0+
  • mod-mono (for Apache)
  • mono-fastcgi-server4 (for Nginx)
  • any basic font or font package

The Exago installer can automatically download and install supported versions of mono and mod-mono. Apache or Nginx must be installed prior to Exago.

Optional:

  • mono-basic, which provides support for VB.NET

WARNING. Exago is incompatible with SELinux.

Apache

Installer Application

The Exago Linux Setup Application can be used to install the Exago Web Application, Web Service API, and Scheduler Service. The installer can also install mono and mod-mono. Use the following steps to install Exago on Linux.

Navigate to the Downloads page, select a build, and then use the Linux Download option. Decompress the download. Run installExago.sh as root. The install script can be run as a guided installation or silently with parameters.

Silent Installation with Parameters

Apache must be installed prior to installing Exago.

Usage:

[-d <install path>] [-m <TRUE|FALSE>] [-i <WEBAPP|WEBAPI|SCHEDULER>] [-y] [-h]
-d <install path> Set the install location to use
-m <'TRUE'|'FALSE'> Set whether or not to install Mono
-i <WEBAPP|WEBAPI|SCHEDULER> Set the component to install
-a <Web App Apache Alias> Default is set to '/Exago'
-s <WebService Apache Alias> Default is set to '/ExagoWebApi'
-y Do not prompt for final verification before installing
-h Show this help screen

Guided Installation

Apache must be installed prior to installing Exago.

The installer will attempt to detect system information such as OS and Apache versions. If it cannot detect something it will prompt for the information.

Specify an install path when prompted. If a path is not specified, the installer will default to /opt/Exago.

IMPORTANT. In order for Exago to function it is necessary to install Mono when prompted. If Mono is already installed, this option will have no effect.

Install the Exago Web Application by entering 1 in the field.

  1. Web Application
  2. Web Service API
  3. Scheduler Service

Note. It is possible to install any of these components at a later time by running installExago.sh again.

The installer will detect the Apache installation and generate a default configuration file called exago.conf in the Apache site path.

The installer will automatically set read/write permissions for the current Apache user on the install paths.

  • Config - Permissions and path set automatically
  • Temp - Requires read and write permissions
  • Reports - Requires read and write permissions
  • MapCache - Requires read and write permissions

Folder Configuration

The Config sub-folder of the Exago installation has read and write permissions set by default and the default path /opt/Exago/Config is preferred.

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. The report folder can reside on any server accessible by Exago, provided a mount point is accessible on the Exago server.

IMPORTANT. Do not create the reports folder within the Exago application structure. Doing so can cause ASP.NET sessions to crash when report folders are created or deleted within Exago.

  1. Set the Report folder’s read and write permissions for the Apache user to 775.
  2. Set the default ownership to the specific <apache user>:<apache group>
  3. Specify the location of the Report Folder in the “Report Path” setting of the Administration Console.

The group ownership on the reports directory is not mandatory, and can be changed to have other group ownership as needed for access outside of Exago.

Default UMASK for files written by Exago is 027 and can be changed by updating the MonoUnixUmask option in the generated exago.conf apache configuration file.

The recommended path for the Temp folder is /opt/Exago/Temp.

  1. Set the Temp folder’s read and write permissions for the Apache user to 775.
  2. Set the default ownership to <apache user>:root
  3. Specify the location of the Temp Folder in the Temp Path setting of the Administration Console.

Set the MonitoringService folder's read and write permissions for the Apache user to 775, and set the default ownership to <apache user>:root.

Continue the installation process in the Admin Console.

Nginx

Installer Application

The Exago Linux Setup Application can be used to configure Nginx for use with Exago.

Navigate to the Downloads page, select a build, and then use the Linux Download option. Decompress the download. Run installExago.sh as root.

Nginx must be installed prior to installing Exago.

Usage:

<Install Dir> <Config>:<Alias> [<Config>:<Alias>]
<Install Dir> Exago Installation Directory
<Config>:<Alias> ex. WEB:Exago, WEBSERVICE:ExagoWebApi

Nginx proxies incoming and outgoing requests to a running instance of Exago using a fastcgi module that is installed during the installation process.

Two Exago scripts created during installation need to be started manually or configured to run automatically:

<Web App Install Dir>/bin/startExago.sh
<WebService Install Dir>/bin/startWebService.sh

The required configuration is created in a separate site file located at /etc/nginx/sites-available/exago. The site file is not enabled by default. The location definitions for the web app and/or web service API need to be manually copied into an appropriate site file for the system.

Example

server {
        listen 80;
        listen [::]:80;
        server_name _;
        root /var/www;

        location /<Web App Alias>/ {
                include /etc/nginx/fastcgi_params;
                root <Web App Install Dir>;
                access_log /var/log/nginx/exago.log;
                fastcgi_param SERVER_NAME $host;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_param PATH_INFO "";
                fastcgi_pass 127.0.0.1:9000;
        }
}

Hidden Article Information

Article Author
Nick
created 2016-01-08 18:45:21 UTC
updated 2017-12-07 15:31:34 UTC

Labels
Install, linux, linux configuration, apache, nginx,
Have more questions? Submit a request