Optional: Updating the co-resident application server

If you have installed a Tomcat application server on the Avaya Experience Portal server, you can choose to update the version of the application server, but it is not required.

Before you begin

From the EPM main menu, select Real-time Monitoring > Active Calls and ensure that the applications hosted by the co-resident application server are not handling any active calls.
Back up the required configuration files, data files, web applications and associated components, libraries and binaries from the directory where the application server is installed. For more information on the required backup files, contact the application developer.

Procedure

Log on to Linux on the Experience Portal server.
If you are an Avaya Services representative, and use Avaya Enterprise Linux, the Avaya Service accounts will not be available after the Avaya Enterprise Linux upgrade. The Avaya Service accounts will be available through EASG configuration during the Experience Portal upgrade.
- Log on to the local Linux console as root.
- Or log on remotely as a non-root user and then change the user to root by entering the su - root command.
If you use Avaya Enterprise Linux, enter the /sbin/service appserver stop command to stop the application server.
Navigate to the Support/AppServer directory under the Avaya Experience Portal installation directory by entering the cd $AVAYA_HOME/Support/AppServer command.

$AVAYA_HOME is the environment variable pointing to the name of the installation directory specified during the EPM software installation.

Tip:

This script is also available in the Support/AppServer directory of the Experience Portal installation DVD.
Run the installation script by entering the bash InstallAppServer.sh install_dir command, where install_dir is the name of the directory in which you have installed the existing application server.

For example, to install the application server in the /opt/AppServer directory, you would enter bash InstallAppServer.sh /opt/AppServer.
Follow the prompts displayed by the script.

When the script has completed, the system displays the message Application Server Installation complete.

Note:

The installation script also registers the application server as a Linux service so that it will be restarted whenever the server restarts.
Start the application server by entering the /sbin/service appserver start command.
Give the server time to start, and then check the server status by entering the following command:

/sbin/service appserver status.

The server should respond that the tomcat service is running.
If you want to administer the tomcat server from the Tomcat Manager Web interface, you need to add a tomcat user as specified in the Adding Tomcat user accounts section in the Implementing Avaya Experience Portal on a single server guide.

If you use the Avaya provided application installation script, the script creates the user accounts automatically.

Note:

You can access the Tomcat Manager Web Interface from the System Management > Application Server menu in the EPM web interface with the tomcat user account.
If you want to administer the server, open a web browser and go to http://EP-server:7080/manager/html, where EP-server is the hostname or IP address of the Experience Portal server.

Next Steps

It is recommended that you create a backup of the deployed application and application support runtime libraries files from the older version of Tomcat before it is deleted. These files will be lost if the older version of the Tomcat is deleted. It is also recommended that the deployed applications and application support runtime libraries are re-generated for the updated version of Tomcat.

After you install the application server:

Deploy the speech applications to the application server as described in your application server documentation.
You can delete the previous directory structure of the application server. If the new application server is installed in the same root directory as the old application server, make sure that you do not delete the new application server or the symbolic link named tomcat, which points to the new application server.
For example, if you update Tomcat-8.5.42 to Tomcat-8.5.57 in the /opt/AppServer directory, where /opt/AppServer is the root location of the old application server, you will see the following directory structure:
- /opt/AppServer/OLD_apache-tomcat-8.5.57.tar.gz
- /opt/AppServer/apache-tomcat-8.5.57.tar.gz
- /opt/AppServer/tomcat
You should only delete /opt/AppServer/OLD_apache-tomcat-8.5.57.tar.gz.

Note:

The new version does not overwrite the existing directory structure of the application server. Instead, it creates a sub directory for the new version within the directory.

	Tip:
	This script is also available in the Support/AppServer directory of the Experience Portal installation DVD.

	Note:
	The installation script also registers the application server as a Linux service so that it will be restarted whenever the server restarts.

	Note:
	The new version does not overwrite the existing directory structure of the application server. Instead, it creates a sub directory for the new version within the directory.