Checklist for upgrade installations

When you are ready to upgrade the IBM TRIRIGA Application Platform, you can consult this checklist for other specific requirements that might apply to your upgrade installation.

Release notes
Read the IBM TRIRIGA Release Notes that apply to your upgrade version for information and instructions that are specific to that release. The installer upgrades the IBM TRIRIGA Application Platform only and does not upgrade any IBM® TRIRIGA® applications.
IBM TRIRIGA Best Practices for System Performance
The IBM TRIRIGA Best Practices for System Performance includes important information on optimizing TRIRIGA. Read this document before you install the IBM TRIRIGA Application Platform.
Complete installation

Follow the complete installation process for an upgrade installation.

If you are upgrading from version 2.7.x or earlier, you must upgrade to IBM TRIRIGA Application Platform version 3.4.1, before you can upgrade to IBM TRIRIGA Application Platform version 5.0.

Data recovery and backups

Before starting the upgrade process, create a data recovery plan to be used in the event of a IBM TRIRIGA Application Platform system failure. IBM TRIRIGA is a Java™ enterprise application that runs on a variety of Java application servers and database platforms. Each application server and database platform provides different methods and recommendations for backups and recovery. Consult the product information provided with the application server and database platform you are using with IBM TRIRIGA for backup and recovery operation standards and best practices.

The IBM TRIRIGA installation folder can be backed up regularly to preserve IBM TRIRIGA system settings.

The IBM TRIRIGA database must be backed up before you begin any upgrade. Stage all upgrades in a test environment and complete thorough reviews before you upgrade any production environment.

Tivoli Directory Integrator
If you previously installed Tivoli Directory Integrator by using the IBM TRIRIGA installer, you must uninstall it before you upgrade IBM TRIRIGA Application Platform. Use the Tivoli Directory Integrator uninstallation program, located in the install directory/TDI_IE/TDI/version/_uninst/ directory. Select the option for a complete uninstall. If you previously installed Tivoli Directory Integrator directly, separate from TRIRIGA installer, you do not need to uninstall Tivoli Directory Integrator.
Application server

In general practice, choose the same application server type for the IBM TRIRIGA Application Platform upgrade installation as the application server type from the previous installation.

When you begin the upgrade for a version of IBM TRIRIGA Application Platform that predates version 3.5.x, start only one application server. Do not start any other application servers until the upgrade of the first server is complete and you are able to log into IBM TRIRIGA. If two application server upgrades are started in parallel, conflicts might occur. IBM TRIRIGA Application Platform version 3.5.x or later upgrades include a lock for the .war startup sequence. In addition, all upgrade scripts are now run as a part of the application server startup sequence after an upgrade. The lock prevents other application servers from updating while a server runs the upgrade and synchronization process.

Directory name

Rename the directory of the current IBM TRIRIGA installation before you begin an upgrade. After that directory is renamed, use the name of the original directory for the upgrade installation.

For example, if the current installation directory is tririga, then rename it to tririga-old, and place the upgrade in tririga.

If you previously installed Tivoli Directory Integrator by using the IBM TRIRIGA installer, you must uninstall it before you rename the current IBM TRIRIGA installation directory.

Language packs

For more information, see the Importing language packs topic of the IBM TRIRIGA Application Platform: Globalization User Guide.

Java Development Kit
The Java Development Kit (JDK) must be installed before you run the IBM TRIRIGA Application Platform installer. The JDK must be installed before you run the IBM TRIRIGA application. Java must be running during an IBM TRIRIGA Application Platform installation. You must set the JAVA_HOME environment variable to the path of the JDK before you start the IBM TRIRIGA Application Platform installation program.

GNU OpenJDK is not supported and will not work with IBM TRIRIGA and the IBM TRIRIGA Application Platform installation program. The OpenJDK package should be completely uninstalled from the server.

First step in the upgrade
The first step in the upgrade is to run the installer. You must have write or create access to the installation root directory.
  • From the Windows environment, double-click the install_tririga_v5.0.0_Windows.exe file. On Windows, C:\TRIRIGA is the default installation location.
  • From Linux® command line, log in to a terminal as the IBM TRIRIGA user and type, for example, ./install_tririga_v5.0.0_Linux.bin -i console. To go back, type back and press the Enter key. On Linux servers, /usr/local/tririga is the typical installation location. After the root super user pre-creates this directory, run the chown tririga /usr/local/tririga command as root, where tririga is the name of the installation user.
Java virtual machine
During the upgrade:
  • Select the path to the Java virtual machine (JVM) that you want the installer to use. The screen lists the java.exe versions that are available on your target computer. IBM TRIRIGA supports Java 17 64-bit only.
  • If you see the “Unable to install the Java Virtual Machine included with this installer” message, then continue with the upgrade. This message is caused by the version of InstallAnywhere that is used by the installer. It has no effect on the upgrade.
Installation directory
During the upgrade, specify the complete path of the directory to which you want to install the files:
  • The installation path must not have any spaces. If it has spaces, specify another path. The typical location is tririga.
  • The directory must not have an existing installation. If it has an existing installation, rename that directory. For example, rename the directory to tririga-old plus the date.
Application data

During the upgrade, specify the full path of the renamed location that contains the existing IBM TRIRIGA installation files.

After the upgrade

After the upgrade is complete, start only one application server. You can follow the verification checklist to verify that your installation is running properly before starting another application server.

Always save a copy of the server.log file for the first application server that starts after an IBM TRIRIGA Application Platform upgrade.IBM TRIRIGA can be configured to use Single Sign On (SSO) technology if SSO has been configured in your environment. After the appropriate properties are configured, IBM TRIRIGA can accept tokens issued by application servers for SSO. IBM Support can assist with configuring IBM TRIRIGA properties for SSO. However, due to the number of supported products, technologies, and configurations supported by IBM TRIRIGA, IBM Support cannot assist in the configuration of SSO within your environment.

Database table lock during upgrade
During the initial startup of the application server, the database is prepared to work with the current IBM TRIRIGA Application Platform version. During this process, a lock is placed on one of the tables in the database. If the application server quits unexpectedly while this step is performed, the table lock might remain in place. In this case, ensure that there are no other application servers connected to the database, and then use the following SQL statement to remove the lock.
delete from environment_properties where property = 'upgrade.lock';

Be sure to commit changes to the database.

Verifying the installation
After the IBM TRIRIGA Application Platform installation is complete, verify that your installation is running properly, see the Verification checklist.