ContentsInstallation and setup

Upgrade from e2016

Applies to ISPICIO_E 2.1.1.0 Last reviewed

Move an existing e2016 installation on Apache Tomcat to e2022: update Java, Tomcat and PostgreSQL, deploy the new application and remove the old one.

On this page

e2016 is the previous generation of ISPICIO_E. The current generation is called e2022; the WAR file and the address of the application carry this name.

Update Java

ISPICIO_E requires Java 25 or newer. Install a suitable JDK on the server on which ISPICIO_E runs. You can install Java in several ways. OpenJDK and Eclipse Temurin are recommended. Eclipse Temurin is well documented, see the installation instructions.

Update Tomcat

ISPICIO_E requires Apache Tomcat 11 or newer. Apache Tomcat provides a migration guide for each major version, see the Migration Guide. The step from 8.5.x to 9.0.x, for example, is described in the migration guide for Tomcat 9.0.x.

Update PostgreSQL

ISPICIO_E requires PostgreSQL 19 or newer. With PostgreSQL 12.0 or older, ISPICIO_E does not start.

Create a dump (backup) of your database before you update PostgreSQL. The PostgreSQL documentation describes how: SQL Dump. Select the documentation for your PostgreSQL version there.

Update ISPICIO_E

Download the current version from the Downloads page and unpack the ZIP archive. It contains the WAR file e2022.war.

Stop e2016

Stop the application e2016 in the Tomcat Manager. You reach it at YOUR_SERVER_URL:8080/manager. For details, see the Tomcat documentation: Tomcat Web Application Manager How To.

Deploy the new version

  1. Connect to your server via SFTP.

  2. Copy the new WAR file to the Tomcat folder webapps/, where the application e2016 is located (tomcat/webapps/e2016).

  3. Set up the connection to the PostgreSQL database. There are two ways to do this. Use only one of them and do not combine them. You find the current settings of e2016 in tomcat/webapps/e2016/WEB-INF/classes/application.properties.

    Option A: environment variables (strongly recommended)

    Set the environment variables in tomcat/bin/setenv.sh. If the file does not exist, create it and make it executable:

    touch tomcat/bin/setenv.sh
    chmod 755 tomcat/bin/setenv.sh

    Add the following content to setenv.sh and fill in the values:

    # Ispe config
    export ISPE_DB_HOST=
    export ISPE_DB_PORT=5432 # change if port is different
    export ISPE_DB_NAME=ispe # change if db name is different
    export ISPE_DB_USER=
    export ISPE_DB_PASSWORD=

    On Windows, the file is called setenv.bat, see Installation with Apache Tomcat.

    Option B: configuration file (not recommended)

    Edit the file tomcat/webapps/e2022/WEB-INF/classes/application-e2022.yml and replace the variables in ${...} with your database settings:

    spring:
      datasource:
        url: jdbc:postgresql://${ISPE_DB_HOST}:${ISPE_DB_PORT}/${ISPE_DB_NAME}
        username: ${ISPE_DB_USER}
        password: ${ISPE_DB_PASSWORD}
  4. Restart Tomcat, for example in the terminal:

    1. Connect to your Tomcat server via SSH.
    2. Change to the folder tomcat_home/bin.
    3. Stop Apache Tomcat with ./shutdown.sh.
    4. Start Apache Tomcat with ./startup.sh.
  5. Check that e2022 is available. The new application runs in the new context e2022: replace e2016 with e2022 in the address in your browser, for example my-ispicio-server.com/e2022. A login form appears.

    If e2022 is not available, check the logs, either in the Tomcat Manager or via SSH or SFTP on the Tomcat server. The section “Troubleshooting” below names the log file.

Remove e2016

After you have logged in to e2022 successfully, you can remove e2016 from your server. Back up the file /webapps/e2016.war if necessary, delete it and restart Tomcat.

Troubleshooting

Check the log file

ISPICIO_E writes its log to tomcat/logs/ispicio-e2022.log. Make sure that the Tomcat user can write to this file.