Installing TRIRIGA Application Platform on a Liberty profile and Oracle Database

After your database server is prepared, you can begin to install the TRIRIGA® Application Platform on a Liberty profile and Oracle Database.

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 Liberty (Embedded). Specify the Liberty profile information in the next set of screens.
   1. Specify the Java memory setting values in megabytes.
   2. Specify HTTP and HTTPS ports and the session timeout value used by the Liberty Profile.
   3. Optional: Configure TRIRIGA to run Liberty as a Windows service. You must run the TRIRIGA installation program as an Administrator to create the Windows service. If you did not run the TRIRIGA installation program as an Administrator, quit the installation program and restart it with Administrator privileges. This service will replace an existing Liberty Windows service on the system unless you assign it a unique service name.
   4. Specify the application context root for accessing the IBM® TRIRIGA application. This path must begin with a slash (/).
5. For the database type, select Oracle. Consult with your Oracle Database 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 data schema database server, such as the host name, port, and system identification (SID). For example, 1521 is a typical value for the Oracle Database server port, and orcl is a typical value for the Oracle Database server system identification.
   3. Specify the data schema user name and password. For example, tridata is a typical value for both fields.
   4. 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.
   5. Optional: Specify the data schema table space parameters, such as the file names and file sizes in megabytes. This screen is displayed if you chose to create the table spaces. The default file size is 2500 MB (or 2.5 GB), which is the minimum that is required. To determine the correct size of these files, conduct a careful analysis. If the autoextend option is enabled for table spaces within the database, the table spaces are automatically extended as needed. However, this extension might severely affect performance.
   6. Optional: Specify the database administrator user name and password. This screen is displayed if you chose to create the table spaces and schema. 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.
   7. Review the URL that the installer is using to test the data schema connection.
   8. Review the results of the test. If the test fails, verify that Oracle Database 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.
   9. 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. 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 using the appropriate method.
    • On Windows servers, open a command prompt and run the command to start the Liberty profile. tririga_root\wlp\bin\run.bat
    • On UNIX servers, open a command prompt and run the command to start the Liberty profile. tririga_root/wlp/bin/run.sh
    The command window closes after initial startup. Liberty continues to run as a background process.