Installing TRIRIGA Application Platform on a Liberty profile and IBM DB2
After your database server is prepared, you can begin to install the TRIRIGA Application Platform on a Liberty profile and IBM DB2.
Before you begin
Verify that IBM DB2 is running and that you have administrative authority on the server. Ensure the IBM DB2 database instance and the database have been configured for TRIRIGA®.
Procedure
- Run the installer file. Follow the installation
instructions.
- Accept the license.
- Check for the latest available fix pack and apply it.
-
Choose the Java Virtual Machine to use with the installation program.
The 64-bit version of Java 17 is required.
- Select the installation folder.
- For the installation type, select New Database (data.zip required).
- Select the data file to install and click Choose.
- Optional: If license files for this product are stored on this system, specify the full path to their location.
- For the application server, select IBM WebSphere Liberty (Embedded). Specify the Liberty
profile information in the next set of screens.
- Specify the Java memory setting values in megabytes.
- Specify HTTP and HTTPS ports and the session timeout value used by the Liberty Profile.
- 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.
- Optional:
On Windows, specify the application
context root for accessing the IBM®
TRIRIGA
application.
This path must begin with a slash (/).
- For the database type, select IBM DB2. Consult with your IBM
DB2 administrator and specify the database information in the next set
of screens.
- Select the database actions to be initiated, such as
creating table spaces and loading the database from a .zip file. Some of these tasks can be completed by the database administrator beforehand.For example, if your database administrator pre-created the table space, clear the first option.When you create the database, you must load data using the installation program.
- 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.
- Specify the IBM
TRIRIGA database user name and password. For example, tridata is a typical value for the database user name.
- 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.
-
Specify the database administrator user name and password.
This information is required to set up the data schema.
- Review the URL that the installer is using to test the data schema connection.
-
Specify the time zone.
Make sure this value matches the time zone of the database and local application server.For example, America/Los_Angeles.
- 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.
- 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.
- Select the database actions to be initiated, such as
creating table spaces and loading the database from a .zip file.
- Complete and review the installation information
in the final set of screens.
- Specify the names of the Simple Mail Transfer Protocol (SMTP) mail server and front end server.
- Review the pre-installation summary and click Install.
- Click Next.
- 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.
- 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.
- When the installation is complete, click Done.
- 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.
- 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. - On Windows servers, open a command prompt and run the command to
start the Liberty profile.
What to do next
Verify that your installation is running properly.