Upgrading on IBM WebSphere Application Server and Microsoft SQL Server

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 Microsoft SQL Server administrator.

Before you begin

Verify that the Microsoft SQL Server and IBM WebSphere Application Server are running and that you have administrative authority on the servers.

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 Microsoft SQL Server. Consult with your Microsoft SQL Server administrator and specify the database information in the next set of screens.
    1. Specify the information for the database server connection, such as the port and name.
    2. Specify the database user name and password.
      Verify that the database user that is being used for the new installation is uniquely associated to the database.
    3. Optional: Select the option to configure your database for multibyte language support. Verify that no IBM TRIRIGA application instances are connected to the database, and the database user for the upgrade installation is uniquely associated with the database.
      If you do not configure the database for multibyte language support, you can select this option during a future upgrade. However, if you anticipate supporting multibyte languages in the future, you should configure the database for multibyte language support now. Single-byte support will be deprecated in a future TRIRIGA release. If you decide to update an existing database to support multi-byte characters, the conversion from single to multi-byte can take an extended period of time. Review the documentation for multi-byte upgrade information before starting the process.
    4. Optional: Choose a collation for the Microsoft SQL Server database.
    5. Test the data schema connection.
    6. Specify the sizes for the database pools.
  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.