Optional: Single server Avaya Experience Portal and Application server configuration

Last Updated : Jun 05, 2026 |

If you install Avaya Experience Portal, EPM, and the media server software on the same server, you can also install a Tomcat application. Tomcat 8.5.xx is the version that is shipped with Avaya Experience Portal. Tomcat 8.5.xx is available in the $AVAYA_HOME/Support/AppServer directory.

Avaya Experience Portal includes an installation script for the Tomcat application server. For details, see Optional: Installing a Tomcat application server on the Experience Portal server. You can also do a manual installation of the Tomcat application. For details, see Optional: Manually installing a Tomcat application server on the Experience Portal server.

The performance of the EPM and media server software can have a negative impact if the applications running on the system require more memory. If the applications are memory intensive, you must install the Application server on a different server.

The server must have sufficient disk space for the EPM and media server software as well as any logs created by the applications. If the applications generate a large number of log files, ensure that you monitor the available disk space carefully. For information about generating an alarm when disk space usage exceeds a given percentage, see Administering Avaya Experience Portal.

Requirements

To install an Application server on the Experience Portal server:

  • Do not modify or gain access to the VoicePortal database or the version of Postgres that Experience Portal installs and uses.

  • Do not modify or reconfigure the JDK installed during the Experience Portal software installation.

  • Experience Portal installs Tomcat server. You cannot:

    • Modify or reconfigure this Tomcat server. You must install a separate Tomcat server as an application server.

    • Deploy any applications on this Tomcat server. You must deploy Tomcat server as an application server.

  • Ensure that the Application server does not use any of the following reserved Experience Portal ports: 80, 443, 3005, 3009, 4080, 4443, 6080, 6443, 8005, 8009, 8080, 8443, 9443, 10443, 11443, 52080, 52233.

  • Ensure that you configure the applications to use the same ports as the Application server. By default, the Avaya-supplied Application server installation script sets the port for non-SSL connections to 5080 on Windows and to 7080 on Linux and the port for SSL connections to 5443 on Windows and 7443 on Linux.

  • Do not modify or upgrade the PHP software that Experience Portal installs unless Avaya recommends the modification or upgrade.

  • Do not modify the Apache httpd.conf, ssl.conf or httpd-ssl.conf files. To create an Apache configuration file, you must make sure that the settings of the custom conf file do not conflict with the Experience Portal configuration files mpp.conf, ssl.conf, vpms.conf and vpms_*.conf.