User Tools

Site Tools

Performing Other Post-Installation Tasks

After EASA is installed, the EASA web pages are tested, and the license is installed, a few other tasks may remain. An Administrator may want to:

  • Configure EASA to run as a Windows Service
  • Configure EASA to run on Linux as a user other than root
  • Change EASA's memory allocation

Run EASA as a Service

The EASA Server service is installed automatically on Windows.

Linux must be manually configured, see Running EASA as a Service.

Running under Linux as User other than Root

By default, EASA will run as root on a Linux computer. The steps below will configure EASA to run as a different user:

  • Stop the EASA Server. See Start or Stop EASA
  • Uncomment and set the RUN_USER variable to the desired user name in:
    • <EASAROOT>/tomcat/bin/easa.conf
  • Add read, write and execute permissions on the installation and data folders.
    • For example:
      • sudo chown -R easauser:easauser <EASAROOT>
      • sudo chown -R easauser:easauser <SERVERDATA>
  • By default EASA runs on port 80 which is not available to a user other than root.
  • To turn on port forwarding from 8080 to 80, edit two files:
    • In <EASAROOT>/tomcat/bin/easa.conf
      • Uncomment and set the CATALINA_IP variable to the IP address of the EASA Server computer.
      • Uncomment the EXTERNAL_PORT variable,
      • Uncomment the INTERNAL_PORT variable.
    • In <EASAROOT>/tomcat/conf/server.xml
      • In the first <Connector> tag,
        • Set: proxyPort to port 80
        • Set: port to port 8080
    • Start the EASA software on the EASA Server. See Start or Stop EASA.

The Linux EASA Server is now configured to run as a user easauser.

Modifying EASA's Memory Usage

EASA's default memory allocation is correct for most cases. However if EASA Technical Services advises increasing the amount of memory available to Java, please follow the steps below:

The EASA Server is configured to allocate 1100MB (1.1GB) of memory for Java. The procedure for raising or lowering the maximum heap size depends on whether the EASA Server runs under Windows or Linux and whether its runs as an application or as a service.

The memory setting should be at least 500 MB to maintain an acceptable level of performance from an EASA Server.

The EASA Server's current memory setting is found at:

  • EASA→Administrator→System→Diagnostics→Summary→Maximum allowed memory usage

Windows Servers, EASA run as an application

If EASA is run as an application, the environment variable JAVA_OPTS will be:

  • JAVA OPTS→-Xmx1100m

To change the EASA Server's allocation to 750 MB modify the environment variable below:

  • Settings→Control Panel→System→Advanced→Environment Variables
    • JAVA_OPTS→-Xmx750m

Windows Servers, EASA run as a service

If EASA runs as a Windows service, configure the maximum memory setting before installing the EASA service in:

  • <EASAROOT>\tomcat\bin\service.bat

Edit the service.bat file in a text editor, such as Notepad, and search for and then modify the default maximum memory setting of:

  • --JvmMx 1100

For example to allocate 750 MB for EASA, change the above line to:

  • --JvmMx 750

Additionally, raise the maximum heap size available to Windows services by running regedit, by modifying the third number in the SharedSection entry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

For example change:

  • SharedSection=1024,20480,768


  • SharedSection=1024,20480,2048

If EASA has already been set to run as a service, then the existing service must be removed and then installed again after changing the memory settings. See the Removing the EASA Service page for details on removing the service.

Linux Servers

To change the EASA maximum memory setting on a Linux computer, edit the line containing JAVA_OPTS in:

  • <EASAROOT>/tomcat/bin/

Change the default -Xmx1100m value to the desired maximum memory setting. For example to allocate 750 MB for EASA, set the value to -Xmx750m.