User Tools

Site Tools

Prior to Setup or Upgrade...

This article outlines the installation and upgrade process and provides links to detailed installation instructions for each of the three types of EASA installer.

Before you launch the installer please read the Pre-installation issues below to identify potential system conflicts.

New Installation

The new installation process involves the following sequence of steps:

  1. Install the EASA Server software, choose between…
  2. Obtain, install and check a license key after the 30-day evaluation period
  3. Configure user accounts on the EASA Server, see Users, Groups and EASAP categories
  4. Optionally, configure a database connection, see Connect to an external database

Upgrade Installations

The process to upgrade an existing installation to a newer version requires the following:

  1. Make a backup copy of the <SERVERDATA> folder
  2. Follow the New installation instructions above
    • Versions prior to 5.3 require that certain files and folders are manually migrated from the old <SERVERDATA> to the new one
      Manual migration generally requires EASA Tech Services but much of the process is documented, see Move to a newer EASA version

The EASA Help Pages provide detailed instructions on installing and testing the EASA Server and also provide solutions to many common problems. However, if further assistance is needed, especially when migrating to a newer version of EASA, please email

Pre-Installation Issues

Other Web Server Software

If another web server such as Microsoft Internet Information Services (IIS) is already installed and listening on port 80, the EASA Server will install itself on a different port displayed during installation, usually port 8080. If no other application is running on port 80 ( IIS, Apache, often Skype, etc…) the EASA Server will install itself on HTTP port 80.

Tomcat Already installed on an EASA Server

Tomcat™ (6.x or 8.x) is third party software that is required and installed as part of the EASA Server.

If Tomcat is already installed and running, it must be removed prior to installing EASA.

Run EASA as a Service

On Windows machines the EASA Server is installed and configured automatically by default to run as a service. To manually configure the service to use a particular user account to log in see EASA as a Windows service

On machines running Linux EASA may be set up to run as a service after completing the installation, see EASA as a Linux service

Java Runtime Environment on Linux Servers

The EASA installer for Linux computers does not include a Java Runtime Environment ('jre') as it did with past versions. A jre version 1.7 or later must be installed on the computer beforehand if EASA is to work properly.

Packages in Linux

Linux distributions such as Ubuntu Server should have all of the packages required to run the EASA installer and to run the EASA Server. One exception to this is C Shell (csh), which may not be included in the distribution by default but is required for correct operation of Compute Servers.

If csh is not included in the distribution, simply install EASA and afterwards, check: EASA > Administrator > Configure > Compute Servers

If the local Compute Server is showing as 'inactive', it is likely that csh needs to be installed, as follows:

  1. yum install csh on RHEL variants
  2. apt-get install csh on Debian variants