Upgrading on IBM WebSphere Application Server and IBM DB2

After your application server and database server are prepared, you can begin to upgrade the IBM TRIRIGA® Application Platform. For specific settings and values, you might need to consult with your IBM WebSphere® Application Server administrator and IBM DB2 administrator.

Before you begin

Verify that the IBM DB2 and IBM WebSphere Application Server are running and that you have administrative authority on the servers. Ensure the IBM DB2 database instance and the database have been configured for TRIRIGA.

Procedure

  1. Run the installer file. Follow the installation instructions.
    1. Accept the license.
    2. Check for the latest available fix pack and apply it.
    3. Choose the Java Virtual Machine to use with the installation program.
      The 64-bit version of Java 8 is required.
    4. Select the installation folder.
    5. For the installation type, select Existing Database.
    6. Select the installation folder for the deployment you want to upgrade.
  2. For the application server, select IBM WebSphere Application Server (Standalone). Specify the WebSphere Application Server information in the next set of screens.
    1. Specify the information for the WebSphere Application Server configuration, such as the cell, node, server, profile, and home.
      Log on to the WebSphere Application Server and run the manageprofiles.[bat|sh] –listProfiles command to identify the cell, node, server, profile, and home values.
      WebSphere Application Server home is defined as C:\Program Files\IBM\WebSphere\AppServer, for example.
      Copy values displayed in the WebSphere Application Server administrative console and paste them to the TRIRIGA installation program fields to avoid typos or other errors. Do not install TRIRIGA into a WebSphere Application Server directory that contains a space. In addition, TRIRIGA cannot be used with cell, node, or server names that include an underscore or dash character.
    2. Specify the WebSphere Application Server administrator user name and password.
      The server must be running after this step to verify that the configuration was specified correctly and needed for the deployment.
    3. Optional: On Windows, define an alternative application context path that accesses the IBM TRIRIGA application.
      This path must begin with a slash (/).
    4. Specify the Java memory setting values in megabytes.
    5. Specify the server host name.
  3. For the database type, select IBM DB2. Consult with your IBM DB2 administrator and specify the database information in the next set of screens.
    1. Specify the information for the data schema database server, such as the host name, port, and database name.
      For example, 50006 is a typical value for the IBM DB2 server port, and tririga is a typical value for the IBM DB2 database name.
    2. Specify the IBM TRIRIGA database user name and password.
      For example, tridata is a typical value for the database user name.
    3. Specify the names of the data schema table spaces.
      Only letters and the underscore can be used in the table space name.
      For example, TRIDATA_DATA is a typical value for data and TRIDATA_INDX is a typical value for indexes.
    4. Review the URL that the installer is using to test the data schema connection.
    5. Review the results of the test. If the test fails, verify that IBM DB2 is running. If you see an informative message that your database might not properly support multibyte characters and your implementation must support multibyte characters, then click Cancel. Adjust your database and restart the installer.
      For the IBM TRIRIGA Application Platform to work correctly, the instance must be configured to use Oracle compatibility mode. To support multibyte characters, the codeset of the IBM DB2 instance must support UTF-8 and string_units must be set to CODEUNITS32.
    6. Specify the sizes for the database pools.
      These settings determine the number of connections that the application server starts when it initializes and the number that it can grow to under load.
  4. Complete and review the installation information in the final set of screens.
    1. Specify the names of the Simple Mail Transfer Protocol (SMTP) mail server and front end server.
    2. Review the pre-installation summary and click Install.
  5. Click Next.
    1. Optional: If you want to monitor the progress in the directory where IBM TRIRIGA is installed, you can open the ant.log file in a log monitoring utility.
      In Windows, you can run the WinTail utility. In UNIX, you can run the tail –f ant.log command.
  6. When the installation is complete, click Done.
  7. Verify that your license files are in the tririga_root\config\licenses directory.
  8. Optional: If you made customizations that were saved in the userfiles directory, copy those files into the upgrade installation.
  9. Restart IBM TRIRIGA by locating the WebSphere Application Server directory with the appropriate method.
    • On Windows servers, start the WebSphere Application Server service IBM WebSphere Application Server V8.5 - NODENAME from Control Panel > Administrative Tools > Services.
    • On UNIX servers, run the stopServer and startServer commands and specify the server name, WEBSPHERE_HOME/profiles/AppSrv01/bin/stopServer.sh SERVER_NAME and then WEBSPHERE_HOME/profiles/AppSrv01/bin/startServer.sh SERVER_NAME.
    • Alternatively, you can start the application through the WebSphere Application Server admin console. Log into the WebSphere Application Server admin console, go to Applications > All Applications, select the IBM TRIRIGA application and click Stop and then Start.

What to do next

Verify that your installation is running properly.