Installing IBM TRIRIGA Application Platform on WebSphere and Microsoft SQL Server

After your application server and database server are prepared, you can begin to install the IBM® TRIRIGA® Application Platform on IBM WebSphere® Application Server and Microsoft SQL Server.

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 New Database (data.zip required) and then select the data file to install.
2. Select the data file to install and click Choose.
3. Optional: If license files for this product are stored on this system, specify the full path to their location.
4. 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: 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.
5. 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. Select the database actions to be initiated, such as creating table spaces, creating the schema, and loading the database from a .zip file. Some of these tasks can be completed by the database administrator beforehand. When you create the database, you must load data using the installation program.
   2. Specify the information for the database server connection, such as the port and name. For example, 1433 is a typical value for the Microsoft SQL Server port, and tridata is a typical value for the Microsoft SQL Server database name.
   3. Specify the database user name and password. For example, tridata is a typical value for both fields. Verify that the database user that is being used for the new installation is uniquely associated to the database.
   4. Choose a collation for the Microsoft SQL Server database.
   5. Specify the database administrator user name and password. This information is required to set up the database structures and schema owner. You are not prompted to specify the database administrator user if you chose to load the database from a .zip file as the only database action to perform.
   6. Review the URL that the installer is using to test the data schema connection.
   7. Review the results of the test. If the test fails, verify that Microsoft SQL Server is running.
   8. 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.
6. 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. Optional: Install IBM Tivoli® Directory Integrator.
   3. Review the pre-installation summary and click Install.
7. 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.
8. When the installation is complete, click Done.
9. Confirm that your license files are in the tririga_root\config\licenses directory. If they are not, you must copy them to this directory. All application servers that access a database must have the same set of licenses. The only exception is the license file for the IBM TRIRIGA Connector for Business Applications. This product is licensed for a limited number of servers and the license file must be placed on that number of servers to stay in compliance. For more information, see the topic about license files.
10. 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.