FANDOM


This article applies to TRIRIGA Application Platform Version 3.3.2 unless otherwise noted.

You can select the IBM TRIRIGA Application Platform installation process that applies to your hardware configuration, whether you have a JBoss Application Server (AS), Red Hat JBoss Enterprise Application Platform (EAP), Oracle WebLogic Server, or IBM WebSphere Application Server. For added flexibility, you can also install the platform with Oracle Database export files, or integrate the platform with an optional Brava installation.

After you determine the platform architecture, server types, and implementation sizes that apply to your business needs, you are ready to install the IBM TRIRIGA Application Platform.

System rolesEdit

Before you install the IBM TRIRIGA Application Platform, you can consult with other roles to avoid technical issues and understand the settings that apply to your particular implementation.

  • System administrator: Is responsible for the ongoing maintenance of the system. This role must consider how the IBM TRIRIGA Application Platform installation can affect the day-to-day operation of the physical servers, server software, and communications among the servers.
  • Database administrator: Is responsible for setting and managing database parameters. This role must consider how the IBM TRIRIGA Application Platform installation depends on the database size, data file locations, and day-to-day operation of the database. For customers without this dedicated role, they can request database configuration scripts for installations that accept all of the defaults and modify few settings.
  • System engineer: Is responsible for the installation or implementation of the system. This role must consider how the IBM TRIRIGA Application Platform installation can affect the configuration files, software components, and server communications that are already installed and working together.

System requirementsEdit

Before you install the IBM TRIRIGA Application Platform, you must verify the hardware and software product requirements that apply to your particular implementation.

The IBM TRIRIGA Support Matrix provides information about the IBM TRIRIGA supported software products. It lists the application servers, database servers, web servers, third-party servers, third-party components, and client options with which the IBM TRIRIGA Application Platform is certified.

Furthermore, the following list outlines the hardware requirements and other software considerations:

MemoryEdit

The database server must have at least 3 GB of physical dedicated memory.

Disk spaceEdit

You must prepare the following disk space requirements:

  • If you download all components of an installation, you need at least 1.8 GB of disk space.
  • In addition, the installation occupies approximately 300 MB of disk space.
  • For the installer to run, you need at least 160 MB in temporary space on the hard disk.
  • For a new installation, you need at least 5 GB within the database.

Application server and database serverEdit

The application server and database server must be in the same physical location, such as a room or building. Minimize the number of segments or "hops" along the path between the application server and the database server. The minimum network speed that is required is fast ethernet (100 Mbps), switched.

Display serverEdit

For UNIX or Linux, use of the Java Abstract Window Toolkit (AWT) requires an X Window System display server to take full advantage of IBM TRIRIGA features. This server can be either a real X or virtual X buffer, depending on the following considerations:

  • X virtual frame buffer (Xvfb) is an X server that can run on computers with no display hardware and no physical input devices. It emulates a dumb frame buffer by using virtual memory. Xvfb must be installed and configured. If you need more information, consult your operating system vendor.
  • If the server computer has a video card, a program such as X.Org, XFree86, or Xsun must be configured and started.
  • To enable the X display, the following commands must be run before you start an IBM TRIRIGA application server. These commands can be added to the ~/.bash_profile startup script so the system is ready to go before you start application servers or process servers:
Xvfb :1 &
export DISPLAY=:1
  • If you are using Xvfb and your graphs do not display as expected, use X instead of Xvfb.

Application server softwareEdit

The JBoss Application Server, WebLogic Server, or WebSphere Application Server software must be installed before you run the IBM TRIRIGA Application Platform installer.

JBoss application server softwareEdit

If you choose to install JBoss Application Server (AS) or Red Hat JBoss Enterprise Application Platform (EAP), prepare for the following guidelines:

  • For JBoss Application Server (AS), you can download the JBoss5.1.0.GA.zip installation file from http://sourceforge.net/projects/jboss/files/JBoss/JBoss-5.1.0.GA/. In Microsoft Windows, extract the .zip file to create a folder with the path of C:\JBoss\jboss-5.1.0.GA. When you are requested by the IBM TRIRIGA Application Platform installer, specify the C:\JBoss\jboss-5.1.0.GA folder as the complete path to your JBoss directory. This path is the typical path. If you choose an alternative path, the name of the JBoss directory must not have a space.
  • For Red Hat JBoss Enterprise Application Platform (EAP), you can download the jboss-eap-5.1.0.zip installation file from http://www.redhat.com/products/jbossenterprisemiddleware/application-platform/. In Microsoft Windows, extract the .zip file to create a folder with the path of C:\jboss-eap-5.1\jboss-as\. When you are requested by the IBM TRIRIGA Application Platform installer, specify the C:\jboss-eap-5.1\jboss-as\ folder as the complete path to your JBoss directory. This path is the typical path. If you choose an alternative path, the name of the JBoss directory must not have a space.
  • You must not install IBM TRIRIGA Application Platform on a pre-configured Red Hat JBoss Enterprise Application Platform instance. Do not modify any files after unzipping the Red Hat JBoss Enterprise Application Platform .zip file. You can configure Red Hat JBoss Enterprise Application Platform after the IBM TRIRIGA Application Platform installation is complete.

Database server softwareEdit

Oracle Database or Microsoft SQL Server must be installed before you run the IBM TRIRIGA Application Platform installer. During the installation process, you are required to provide the database administrator (DBA) user ID and password.

Oracle Database installationsEdit

Table spaces for new Oracle Database installations must be created before you run the installer. Analyze your base data. This data includes documents, leases, and portfolio data, such as people, organizations, assets, and locations. Set the sizes for the TRIDATA_DATA table space and TRIDATA_INDX table space to support at least this base data. The minimum size for the TRIDATA_DATA table space and TRIDATA_INDX table space is 2.5 GB each. If you use existing IBM TRIRIGA table spaces, verify that the autoextend option is enabled.

Java Development KitEdit

The Java Development Kit (JDK) must be installed before you run the IBM TRIRIGA Application Platform installer. The JDK must be installed before you run the IBM TRIRIGA application. Java must be running during an IBM TRIRIGA installation.

Security privileges and directory accessEdit

The administrator or user who runs the IBM TRIRIGA Application Platform installation must have create access and write access to the installation root directory.

IBM TRIRIGA licenses (keys)Edit

Starting with IBM TRIRIGA Application Platform version 3.2, IBM TRIRIGA distributes software licenses in a separate license file for each product. The license file names are in the format LICENSE_IBM_TRIRIGA_[productname].properties (for example, LICENSE_IBM_TRIRIGA_Application_Platform.properties). You can continue to use an existing TRIRIGALICENSE.properties file if you have one until it expires or you use a new product. For more information, see the topic about license files.

Installation processesEdit

Before you install the IBM TRIRIGA Application Platform, you must determine the installation type that applies to your particular implementation. Although there are several installation types, they all follow the same general installation process. These installation types include full installation, application server-only installation, and database-only installation.

General installation processEdit

Whether you choose a full installation, application server-only installation, or database-only installation, prepare the following access and information before you begin:

  • Administrator access to the servers on which you are installing
  • Database administrator access to the database server
  • For Oracle Database, the system identification (SID) or database instance name
  • For Microsoft SQL Server, the database name
  • For existing databases, the database instance login information
  • Server name and IP address of the database server
  • Server name of the process server
  • Optional: Server name and IP address of the tools server (or Brava server)

The process of installing IBM TRIRIGA is the same regardless of the level of security that is applied to your environment. After installation, you can secure your environments according to your business requirements. For instance, security considerations might include securing client communication and restricting access to servers.

Full installation processEdit

A full installation process installs the key components and configurations necessary for the IBM TRIRIGA platform and applications to operate:

  • Application server
  • Database scripts
  • Database
  • Optional: Configurations to connect to the tools server (or Brava server)

Server-only installation processEdit

An application server-only installation process installs and configures the application server and the IBM TRIRIGA .ear file. Configurations are required to establish the connection to the database. In addition, if you plan to use the optional Brava viewer, collect the necessary information to connect to the server. Do not select the server-only or database-only installation or upgrade unless you are directed to do so by your implementation team. It is very important to keep the application server and database server synchronized. The installation program updates the application server and database tables, indexes, and stored procedures, at the same time so the system maintains a known good state. In some rare cases, support or implementation teams might discover an issue where only the application server or only the database should be updated.

Database-only installation processEdit

A database-only installation process creates the database without installing the application server. Do not select the server-only or database-only installation or upgrade unless you are directed to do so by your implementation team.

Installation combinationsEdit

Before you install the IBM TRIRIGA Application Platform, you must determine the application server and database combination that applies to your particular implementation.

Many types of new installations can be selected for the IBM TRIRIGA Application Platform, including the following combinations:

Application server and database combinations Oracle Database Microsoft SQL Server
IBM WebSphere Application Server Yes, see video
IBM TRIRIGA 10.3 331:38

IBM TRIRIGA 10.3 3.3 WebSphere

Yes
JBoss Application Server (AS) Yes, see video
IBM TRIRIGA 10.3 325:51

IBM TRIRIGA 10.3 3.3 JBOSS

Yes
Red Hat JBoss Enterprise Application Platform (EAP) Yes Yes
Oracle WebLogic Server Yes, see video
IBM TRIRIGA 10.3 335:19

IBM TRIRIGA 10.3 3.3 WebLogic

Yes

For a list of the supported application servers, database servers, and their versions, see the IBM TRIRIGA Support Matrix.

Installation checklistsEdit

Before you install the IBM TRIRIGA Application Platform, you can follow the application server and database checklists that apply to your particular implementation.

Checklist for new installationsEdit

Review the following checklist to install both the application server and database:

Item Description
Release notes Read the IBM TRIRIGA Release Notes that apply to your installation version for information and instructions that are specific to that release.
Data recovery and backups Before starting the installation process, create a data recovery plan to be used in the event of a IBM TRIRIGA Application Platform system failure. IBM TRIRIGA is a Java enterprise application that runs on a variety of Java application servers and database platforms. Each application server and database platform provides different methods and recommendations for backups and recovery. Consult the product information provided with the application server and database platform you are using with IBM TRIRIGA for backup and recovery operation standards and best practices. After a successful installation, the IBM TRIRIGA installation folder can be backed up regularly to preserve IBM TRIRIGA system settings.
Full installation Follow the full installation process for a new installation. Do not select the application server-only or database-only installation or upgrade unless you are directed to do so by your implementation team. The application server and the database server must remain synchronized at all times. The installation program updates both servers to ensure they are in synch. If you are upgrading an existing IBM TRIRIGA implementation, see the IBM TRIRIGA Application Platform 3 Upgrade Installation Guide.
Language packs The installer copies language packs into the [install directory]\userfiles\LanguagePacks folder. Starting with the IBM TRIRIGA Application Platform version 3.3, the directory structure of the language packs separates the label packs from the data packs. You must unpack the main language pack before you select the individual language pack to import. Make sure that you import the correct type of language pack in the specific interface. For example, if you are in the Label Manager, you must import a label pack. If you are in the Language Manager, you must import a data pack. Importing a data pack is not required if your installation is US English only. For more information, see the IBM TRIRIGA Application Platform 3 Localization User Guide.
First step in the installation The first step in the installation is to run the installer: 
  • From the Windows environment, double-click the install.exe file. On Windows, C:\Tririga is the default installation location. 
  • Connect and log in to your application server as the IBM TRIRIGA user through SSH or other remote terminal application. If an X Windows connection is not available, log in to the system as the IBM TRIRIGA user, and use the ./install.bin -i console command. If you are connecting from a Linux system through an X Windows session, you can use the command ./install.bin to install using the graphical installation program. 
  • From the UNIX or Linux command line, log in to a terminal as the IBM TRIRIGA user and type ./install.bin -i console. To go back, type back and press the Enter key. On UNIX servers, /usr/local/tririga is the typical installation location. After the root super user pre-creates this directory, run the chown tririga /usr/local/tririga command as root, where tririga is the name of the installation user.
Java virtual machine (JVM) During the installation:
  • Select the path to the Java virtual machine (JVM) that you want the installer to use. The screen lists the java.exe versions that are available on your target computer. IBM TRIRIGA supports Java 6 only. WebSphere Application Server installations support IBM Java versions 6 or 7. JBoss and WebLogic Server installations support Oracle Java.
  • If you see the following message, “Unable to install the Java Virtual Machine included with this installer”, then continue with the installation. This message is caused by the version of InstallAnywhere that is used by the installer. It has no effect on the installation.
Installation directory During the installation, specify the complete path of the directory to which you want to install the files:
  • The installation path must not have any spaces. If it has spaces, specify another path. On Windows, C:\Tririga is the typical location. On UNIX, /usr/local/tririga is the typical location.
  • The directory must not have an existing installation. If it has an existing installation, rename that directory. For example, rename the directory to add the word "old" and the date.
Application data During the installation, choose the compressed file where the IBM TRIRIGA application data is stored. This compressed file is named data.zip and is selected automatically by the installer. If the file is not selected, then locate and select the correct file.
After the installation After the installation is complete, verify that your installation is running properly. For more information, see the verification checklist.

Checklist for new installations on Oracle DatabaseEdit

Review the following checklist to install on Oracle Database:

Item Description
Release notes Read the IBM TRIRIGA Release Notes.
Multibyte language support If you support multibyte languages, the Oracle Database must originally be installed as a multibyte database. If the database was not originally installed as a multibyte database, it cannot be changed afterwards.
Multibyte language support If you support multibyte languages, take the following steps before you begin the installation:
  • Set the instance character set to UTF-8 or UTF-16. If you do not select a UTF-8 or UTF-16 character set, a multibyte character is shown as a question mark when saved in the database.
  • Set the NLS_LENGTH_SEMANTICS parameter to CHAR (not BYTE). If you use BYTE instead of CHAR, the platform does not run the length operations correctly and data can be lost.
  • Set a block size of at least 16K.
User name requirement For Oracle Database, the schema owner must use the same user ID as the database user.

Checklist for new installations on Microsoft SQL ServerEdit

Review the following checklist to install on Microsoft SQL Server:

Item Description
Release notes Read the IBM TRIRIGA Release Notes.
Multibyte language support If you support multibyte languages, take the following steps during the installation:
  • Verify that the database user that is being used for the new installation is uniquely associated to the database.
  • Select the option to configure your database for multibyte support.
  • Choose a collation for the database.
Multibyte language support and WebLogic Server If you support multibyte languages, verify on the WebLogic Server that the JDBC URL in your DataSource-TRIRIGA-data sets the property of SendStringParametersAsUnicode to true.
Multibyte language support and WebSphere Application Server If you support multibyte languages, verify in the WebSphere Application Server data source that the custom property of sendStringParametersAsUnicode is set to true.
User name requirement For Microsoft SQL Server, you can use different values for the database name and the database user ID.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.