IBM TRIRIGA Application Platform Version 3.6.0

Installing IBM TRIRIGA Application Platform on WebLogic and Microsoft SQL Server

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

Before you begin

Verify that the Microsoft SQL Server and Oracle WebLogic 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 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 Oracle WebLogic 12c (Standalone). Specify the WebLogic Server information in the next set of screens.
    1. Select Oracle WebLogic 12c (Standalone).
    2. Specify the paths to your WebLogic Server home and Domain Home directories..
    3. Specify the appropriate information for your WebLogic Server host, including the admin server port. Enter the server password.
    4. Specify the Java memory setting values in megabytes.
    5. Optional: Define an alternative application context path to access the IBM TRIRIGA application. This path must begin with a slash (/).
    6. Specify the path to the xercesImpl.jar file.
  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. 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. Start the WebLogic Server when prompted.
  9. When the installation is complete, click Done.
  10. 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.
  11. Start IBM TRIRIGA by starting the WebLogic Server Node Manager, Administration Server, and Managed Server.

What to do next

If the installation failed, see the topic about validating the deployment on WebLogic Server and Microsoft SQL Server.

Verify that your installation is running properly.