Chapter 2. Installing IBM TRIRIGA Application Platform. IBM 3 Release 4.2

PDF

Document

Chapter 2. Installing IBM TRIRIGA Application Platform

You use the IBM TRIRIGA Application Platform to run, build, and manage the

IBM TRIRIGA applications. Installing the platform involves preparing the application and database servers, verifying the installation, configuring the platform settings, and inspecting log reports for installation issues. IBM TRIRIGA

Application Platform can be installed on a variety of platforms. Use this installation information to plan and install IBM TRIRIGA Application Platform in the configuration that suits your environment and your needs.

Overview of hardware configuration

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

Platform architecture

Enterprise software applications are n-tier, where "n" can represent any number of tiers, or layers of processing. The IBM TRIRIGA Application Platform is a logical four-tier system: web, application (and process), tools, and database.

The layering of an application into logical tiers also separates the functions in each tier. In terms of physical tiers, each physical tier describes the actual hardware configuration, the pieces of equipment, and the function of each piece.

Clients

Browser, CAD,

SOAP clients

HTTP

Web server

HTTP

Application servers

Tools server

JDBC

Application server

TCP/IP

ODBC

Database server

HTTP

Internet

Process server

JDBC

Figure 1. Diagram of the IBM TRIRIGA Application Platform architecture

The IBM TRIRIGA Application Platform Compatibility Matrix lists the servers, components, and operating systems on which the IBM TRIRIGA Application

Platform is certified.

Related information :

IBM TRIRIGA Application Platform Compatibility Matrix

Servers

The IBM TRIRIGA Application Platform uses many different types of servers. The word "server" is often used to mean a physical piece of equipment, but it can also represent a logical separation that is based on function. Each of these logical servers can be collocated on physical servers, or separated so that each logical tier is installed on their own physical server.

The following logical function-based servers are used in the IBM TRIRIGA

Application Platform:

Web server

Receives HTTP requests for web content. Also referred to as a front-end server.

Application server

Carries out the user business logic with WebLogic Server or WebSphere ®

Application Server.

Process server

Carries out the background processing and analytics with WebLogic Server or WebSphere Application Server.

Tools server

Carries out the reporting.

Database server

Holds the relational database and supported database management system such as Oracle Database, IBM DB2

® server, or Microsoft SQL Server.

Web server

The web server is the tier with which each user web browser communicates.

Examples of web servers include IBM HTTP Server, Microsoft Internet Information

Services (IIS), and Apache HTTP Server. The web server handles HTTP requests only and does not run business logic. The IBM TRIRIGA Application Platform also supports Secure Sockets Layer (SSL) by using HTTPS. Typically, HTTP uses port 80

(non-secure connection) and 443 (secure connection), but it can be configured to use other ports. Each time a user requests a JavaServer Page (JSP), the web server passes the request to the application server for processing. The web server is a physical manifestation of the web tier.

Application server

The application server is a Java virtual machine (JVM) with an instance of the runtime application. This server runs most of the business logic. Application server processes are CPU-intensive and require a great deal of memory. The application tier consists of JavaServer Pages (JSP) and Java classes. The Java ™ 2 Platform,

Enterprise Edition (J2EE) application server provides a JSP container, a database connection pool, and transaction management services. The application server is a physical manifestation of the application (middleware) tier.

Process server

The process server is a JVM with an instance of the runtime application that is set up as a dedicated processing or analytics engine. This server is configured almost exactly like an application server, but no users sign on to this server. It handles all workflow requests that are queued from users or by the IBM TRIRIGA software.

The process server is a physical manifestation of the application (middleware) tier.

Chapter 2. Installing IBM TRIRIGA Application Platform

Tools server

The tools server houses the third-party extensions from IBM TRIRIGA. You can designate a IBM TRIRIGA application server as a BIRT process server. If you choose to run both BIRT and IBM TRIRIGA on the same server, expect BIRT report handling operations to increase the load on the server. BIRT is run in the same

JVM as IBM TRIRIGA in all cases.

Database server

The database server runs the database process. The database is where data is stored. The major database servers use Structured Query Language (SQL) to store and retrieve data. The Oracle Database server, IBM DB2 server, and Microsoft SQL

Server use SQL. But each server is a different database engine and each has its own extended SQL for competitive differentiation. The application tier communicates with the database tier by using JDBC connection pools. The database server is a physical manifestation of the database tier.

Implementations

The physical configuration of any system depends greatly on the number of users and amount of data that it supports. For information about IBM TRIRIGA

Application Platform system implementations, see the IBM TRIRIGA Best Practices

for System Performance.

Before you deploy IBM TRIRIGA in your organization, plan how the user community should access TRIRIGA applications. IBM TRIRIGA requires a user name and password to gain access to applications. Refer to the IBM TRIRIGA

Application Platform 3 Single Sign-On Setup User Guide if you want to configure single sign-on (SSO) to manage user access to TRIRIGA applications.

Related information :

Best Practices for System Performance

Installing the platform

You can select the IBM TRIRIGA Application Platform installation process that applies to your hardware configuration, whether you have a Oracle WebLogic

Server or IBM WebSphere Application Server. For added flexibility, you can also install the platform with Oracle Database export files.

Overview of TRIRIGA Application Platform installation

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

Application Platform.

Before you install IBM TRIRIGA Application Platform

Verify IBM TRIRIGA Application Platform hardware and software requirements before you start the installation process.

The IBM TRIRIGA Application Platform Compatibility 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.

Refer to the IBM TRIRIGA Application Platform 3.4.x Best Practices for System

Performance guide for extensive system performance information.

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

Memory

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

Ensure that you allocate enough memory to your application servers.

Monitor memory usage regularly to avoid out of memory errors. You might also want to consider deploying a second process server to ensure that workflow processing continues if a process server experiences a failure.

Disk space

You must prepare the following disk space requirements: v If you download all components of an installation, you need at least 1.8

GB of disk space.

v In addition, the installation occupies approximately 300 MB of disk space.

v For the installer to run, you need at least 160 MB in temporary space on the hard disk.

v For a new installation, you need at least 7 GB within the database.

v Each WebSphere Application Server profile requires approximately 1 GB of disk space.

Application server and database server

The application server and database server must be in the same physical location, such as a room or building to avoid issues with network latency.

Minimize the number of segments or along the path between the application server and the database server. The minimum network speed that is required is fast Ethernet (100 Mbps), switched.

Application server software

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

If the value set for the maximum number of parameters allowed in an inbound request is too low, an error can occur when saving a workflow object map. In this case, you can either increase the value, or set the value to unlimited. Refer to the product documentation for your application server for details.

Database server software

Oracle Database, IBM DB2, 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 installations

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.

Chapter 2. Installing IBM TRIRIGA Application Platform

IBM DB2 installations

An IBM DB2 instance and database must be created before you run the

IBM TRIRIGA Application Platform installer.

Java Development Kit

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 access

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)

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.

Related concepts :

“Create and configure a DB2 database for TRIRIGA” on page 15

To configure TRIRIGA with DB2 version 10.5, you must create a database before you start the TRIRIGA Application Platform installation program. You can either create the database manually, or, you can use scripts that are provided with

TRIRIGA.

Related information :

IBM TRIRIGA Application Platform Compatibility Matrix

Types of installation

Before you install the IBM TRIRIGA Application Platform, determine the installation path that applies to your particular implementation. Although there are several installation paths, they follow the same general installation process. These installation types include full installation and database-only installation. Full installations install and configure all key components for IBM TRIRIGA, including the application server. Database-only installations create the database without installing the application server.

Installation preparation

Whether you choose a full installation or database-only installation, prepare the following access and information before you begin: v For Oracle Database, the system identification (SID) or database instance name v For Microsoft SQL Server, the database name v For IBM DB2, the instance port and database name v For existing databases, the database instance login information v Server name and IP address of the database server v Server name of the process 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.

Select the installer for your operating system

Select installation location

Select installation type

Select new or upgrade installation

Installation of application server and/or database

Select database type

Configure database connection

Configure databases

Installation complete

Figure 2. Flow diagram for the general IBM TRIRIGA installation process

Full installation process

A full installation process includes installing the key components and configurations necessary for the IBM TRIRIGA platform and applications to operate: v Application server v Database scripts v Database

Chapter 2. Installing IBM TRIRIGA Application Platform

Select the installer for your operating system

Select installation location

Full installation

New installation

Microsoft SQL Server

Upgrade

Installation of application server and/or database

Oracle Database IBM DB2

Configure database connection

Configure database

Database creation

Installation complete

Figure 3. Flow diagram for the full IBM TRIRIGA installation process

Database-only installation process

A database-only installation process creates the database without installing the application server. Do not select the database-only installation or upgrade unless you are directed to do so by the team responsible for planning the IBM TRIRIGA deployment. If you install the database now and you install a newer version of the application server later, an incompatibility can occur between a new feature and the database.

Select the installer for your operating system

Select installation location

Database only

New installation

Installation of database

Upgrade

Microsoft SQL Server Oracle Database

Configure database connection

IBM DB2

Configure database

Installation complete

Figure 4. Flow diagram for the database-only IBM TRIRIGA installation process

Installation checklists

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

Checklist for new IBM TRIRIGA Application Platform installations

Item

Release notes

Description

Read the IBM TRIRIGA Release Notes that apply to your installation version for information and instructions that are specific to that release.

Chapter 2. Installing IBM TRIRIGA Application Platform

Item

Data recovery and backups

Full installation

Language packs

First steps in the installation

Description

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.

Follow the full installation process for a new installation. If you are upgrading an existing IBM TRIRIGA implementation, see the IBM TRIRIGA Application Platform 3 Upgrade Installation

Guide.

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.

v Install the 64-bit version of IBM Java 7. The Java installation path must not contain spaces.

v 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.

– 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.

Item

Java virtual machine

(JVM)

Installation directory

Application data

After the installation

Description

During the installation: v 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 the 64-bit version of IBM Java 7 only.

WebSphere Application Server installations support 64the

-bit version of IBM Java 7. WebLogic Server installations support Oracle Java.

v 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.

During the installation, specify the complete path of the directory to which you want to install the files: v 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.

v 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.

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 is complete: v Verify that your installation is running properly. For more information, see the topic about the verification checklist.

Checklist for new IBM TRIRIGA Application Platform installations on

Oracle Database

Item

Release notes

Multibyte language support

User name requirement

Description

Read the IBM TRIRIGA Release Notes.

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.

If you support multibyte languages, take the following steps before you begin the installation: v 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.

v 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.

v Set a block size of at least 16K.

For Oracle Database, the schema owner must use the same user ID as the database user.

Chapter 2. Installing IBM TRIRIGA Application Platform

Checklist for new IBM TRIRIGA Application Platform installations on

Microsoft SQL Server

Item

Release notes

Users

Multibyte language support

Multibyte language support and WebLogic

Server

Multibyte language support and WebSphere

Application Server

User name requirement

Description

Read the IBM TRIRIGA Release Notes.

Verify that the database user that is being used for the new installation is uniquely associated to the database.

If you support multibyte languages, take the following steps during the installation: v Select the option to configure your database for multibyte support.

v Choose a collation for the database.

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.

If you support multibyte languages, verify in the WebSphere

Application Server data source that the custom property of sendStringParametersAsUnicode is set to true.

For Microsoft SQL Server, you can use different values for the database name and the database user ID.

Checklist for new IBM TRIRIGA Application Platform installations on

IBM DB2

Item

Release notes

IBM DB2

Multibyte language support

Data collection performance settings in

WebLogic Server.

Data collection performance settings in

WebSphere Application

Server.

Description

Read the IBM TRIRIGA Release Notes.

Perform DB2 configuration steps.

v If you support multibyte languages, the IBM DB2 database must originally be created as UTF-8. If the database was not originally created as UTF-8, it cannot be changed afterwards.

v Set the string_units parameter to CODEUNITS32.

Data collection performance settings are configured with data source properties using the following parameter values: user=TRIRIGA DB User DatabaseName=DB Name jdbcCollection=NULLIDR1

Data collection performance settings are configured by adding a new property to the data source properties: jdbcCollection=NULLIDR1

The isolation level for WebSphere Application Server is set to webSphereDefaultIsolationLevel=2 to prevent database locking.

Related information :

IBM TRIRIGA Release Notes

IBM TRIRIGA Application Platform 3 Upgrade Installation Guide

Create and configure a DB2 database for TRIRIGA

TRIRIGA.

Configuring an existing DB2 version 10.5 server for use with TRIRIGA involves several steps. You must create a TRIRIGA user, create a database, and configure instance and database level settings before you start the IBM TRIRIGA Application

Platform installation program. You can create these database objects by using scripts that are provided with TRIRIGA. Scripts for Windows, Linux, and UNIX are provided in the IBM TRIRIGA Application Upgrade V10.4.2 Multiplatform

Multilingual package. The script files are located in the Scripts directory of the

TRI_APPLICATION_UPGRADE_10.4.2.zip

archive file.

If you create the database objects manually, refer to the scripts for configuration values. You can specify your own values when you create the users, name the database and instance, and define the port that is used by the TRIRIGA database instance. You must accurately provide the DB2 installation directory.

The DB2 database used with TRIRIGA must be configured with the following parameters.

v The DB2 database instance and database must be set to Oracle mode.

v DB2 database parameters must be configured to optimize TRIRIGA performance.

– STMT_CONC=OFF

– PAGESIZE=32 K

– DB2_DEFERRED_PREPARE_SEMANTICS=YES v The user ID created for TRIRIGA to access the database must have DBADM,

SECADM, ACCESSCTRL and DATAACCESS privileges for the database.

v The database must be configured with the UTF-8 code set and CODEUNITS32 string unit if you need to support multibyte characters.

The DB2 port used to communicate with TRIRIGA needs to be available through any firewall software that is active on the system. You can disable firewall software on the DB2 server before you run the TRIRIGA database creation scripts. Firewall software can prevent the TRIRIGA scripts from completing successfully. You can reactivate the firewall after the database is created.

Configuring DB2 version 10.5 for TRIRIGA on Windows by using scripts

Use the db2createinst and db2createdb commands to create and configure a DB2 database on Windows.

Procedure

Create a system user for TRIRIGA, for example, tridata. This system user is used by TRIRIGA to access the database. This user is given permission to access the database by the scripts.

DB2 administrative user is db2admin.

Create the DB2 instance and set it to Oracle Compatibility mode.

Chapter 2. Installing IBM TRIRIGA Application Platform

Copy the db2createinst.cmd command file from \scripts in the installation media to a temporary directory on the DB2 server.

Open a DB2 command window and run the db2cmdadmin command to set up the DB2 environment:

Alternatively, you can use Start > DB2 Command Window –

Administrator .

Run the db2createinst command to create and configure the database instance.

db2createinst name port installDir

db2admin password > outputfilename

The name parameter specifies the DB2 instance name. The port parameter specifies the server port that is used by this instance of DB2. The installDir parameter specifies the installation location of DB2. You must use double quotation marks around the value if the path contains spaces.

The db2admin parameter specifies the DB2 administrator. The outputfilename parameter specifies the file that is used to capture output from the command. The following example provides sample syntax for the db2createinst command.

C:\temp>db2createinst triinst 50006

"c:\program files\ibm\sqllib" db2admin mypassword > db2createinst.log

If the command generates an instance creation return code of 0, the DB2 database instance is created and set to Oracle Compatibility mode, and the message Instance instance name has been created successfully and started on port port number is displayed. If the command generated any return codes other than 0, examine the output of the command to determine the cause of the error. You can capture the output of the script to a file to evaluate the command results. Do not attempt to create the database until the db2createinst command completes successfully.

Create and configure the DB2 database.

Copy the db2createdb.cmd command file from \scripts in the installation media to a temporary directory on the DB2 server.

Start the db2createdb command from the DB2 command window.

db2createdb name instance territory installDir

tririgaUser db2admin > outputfilename

The name parameter specifies the name of the database. The instance parameter specifies the instance that is associated with the database. The territory parameter designates the code that is used by the database manager internally to provide region-specific support. The installDir parameter specifies the installation location of DB2. You must use double quotation marks around the value if the path contains spaces. The tririgaUser parameter specifies the TRIRIGA user ID that is used to access the database. The db2admin parameter specifies the DB2 administrator user

ID. The outputfilename parameter specifies the file that is used to capture output from the command. The following example provides sample syntax for the db2createdb command.

C:\temp>db2createdb tririga triinst

US "c:\Program files\ibm\sqllib" tridata db2admin > db2createdb.log

If the command generates an exit return code of 0, the DB2 database is created and configured, and the message Database database name has been created successfully on instance name.

is displayed. If the command generated any

exit codes other than 0, examine the output of the command to determine the cause of the error. You can capture the output of the script to a file to evaluate the command results. Do not continue with the IBM TRIRIGA Application

Platform installation process until the db2createdb command completes successfully.

What to do next

If you have a firewall, reactivate it and make sure remote connections can be made to the database. Use IBM Data Studio or another SQL tool to verify that a remote connection can be made to the database before you start the IBM TRIRIGA

Application Platform installation program. You may need to allow access to the port used by DB2 in the firewall.

Configuring DB2 version 10.5 for TRIRIGA on UNIX and Linux by using scripts

Use the db2createinst, db2configinst, and db2createdb commands to create and configure a DB2 database on UNIX or Linux.

Procedure

Log in to the server that is running DB2 version 10 as a user that has administrative permissions on the system. The user must be able to create system users and DB2 instances.

Create system users for TRIRIGA.

Create a system user for TRIRIGA to access the database, for example, tridata. This user is given permission to access to the database by the scripts.

Create the DB2 instance owner, for example triinst. The DB2 instance owner creates the DB2 instance for TRIRIGA. This user must not have any existing

DB2 instances associated with it. The triinst user ID must be assigned to the db2iadm1 group.

Create the fenced user ID for the DB2 instance, for example, db2fenc1. This user ID might already exist on the system and can serve as the fenced user

ID for other DB2 instances. The db2fenc1 user ID must be assigned to the db2iadm1 group.

Create the DB2 database instance.

Copy the db2createinst.sh command file from /Scripts in the installation media to a temporary directory on the DB2 server.

Ensure the user ID has execute privileges on the file and write privileges to the current directory.

Open a shell window and run the db2createinst command to create the database instance.

db2createinst.sh name port installDir fenceUser

> outputfilename

The name parameter specifies the DB2 instance owner. The port parameter specifies the server port that is used by this instance of DB2. The installDir parameter specifies the installation location of DB2. The fenceUser parameter specifies the DB2 fence user. The outputfilename parameter specifies the file that is used to capture output from the command. The following example provides sample syntax for the db2createinst command.

Chapter 2. Installing IBM TRIRIGA Application Platform

./db2createinst.sh triinst 50006

/opt/ibm/db2/V10.5

db2fenc1 > db2createinst.log

If the command generates an instance creation return code of 0, the DB2 database instance is created, and the message Instance instance name has been created successfully on port port number is displayed. If the command generated any return codes other than 0, examine the output of the command to determine the cause of the error. You can capture the output of the script to a file to evaluate the command results. Do not attempt to configure the database instance until the db2createinst command completes successfully.

Configure the DB2 database instance.

Copy the db2configinst.sh command file from /scripts in the installation media to a temporary directory on the DB2 server.

Ensure the user ID has execute privileges on the file and write privileges to the current directory.

From the shell window, run the db2configinst command to create the database instance.

db2configinst.sh name port installDir > outputfilename

The name parameter specifies the DB2 instance to configure. The port parameter specifies the server port that is used by this instance of DB2. The installDir parameter specifies the installation location of DB2. The outputfilename parameter specifies the file that is used to capture output from the command. The following example provides sample syntax for the db2configinst command.

./db2configinst.sh triinst 50006

/opt/ibm/db2/V10.5

> db2configinst.log

If the command generates a return code for starting instance of 0, the DB2 database instance is created, and the message Instance instance name has been configured successfully and started on server name is displayed. If the command generated any return codes other than 0, examine the output of the command to determine the cause of the error. You can capture the output of the script to a file to evaluate the command results. Do not attempt to create the database until the db2configinst command completes successfully.

Create and configure the DB2 database.

Copy the db2createdb.sh command file from /scripts in the installation media to a temporary directory on the DB2 server.

Ensure the user ID has execute privileges on the file and write privileges to the current directory.

From the shell window, run the db2createdb command.

db2createdb.sh name instance territory

installDir tririgaUser > outputfilename

The name parameter specifies the name of the database. The instance parameter specifies the instance that is associated with the database. The territory parameter designates the code that is used by the database manager internally to provide region-specific support. The installDir parameter specifies the installation location of DB2. The tririgaUser parameter specifies the TRIRIGA user ID used to access the database. The

outputfilename parameter specifies the file that is used to capture output from the command. The following example provides sample syntax for the db2createdb command.

./db2createdb.sh tririga triinst US /opt/ibm/db2/V10.5

tridata > db2createdb.log

If the command generates an exit return code of 0, the DB2 database is created and configured, and the message Database database name has been created successfully on instance name is displayed. If the command generated any return codes other than 0, examine the output of the command to determine the cause of the error. You can capture the output of the script to a file to evaluate the command results. Do not continue with the IBM TRIRIGA

Application Platform installation process until the db2createdb command completes successfully.

What to do next

Application Platform installation program. You may need to allow access to the port used by DB2 in the firewall.

Installing TRIRIGA Application Platform on a WebSphere

Application Server Liberty Core profile

TRIRIGA Application Platform can be installed on a Liberty profile and supported by a variety of database software. During the TRIRIGA Application Platform installation process, you can select the type of application server you want to use.

Before you begin

Check the IBM TRIRIGA product wiki for the latest information about deploying

IBM TRIRIGA on an Liberty profile.

IBM TRIRIGA application data must be stored on the same filesystem as the filesystem used by the Liberty profile host.

Overview of IBM TRIRIGA Application Platform installation on a

Liberty profile

Liberty profiles are dynamic and provision only the features needed by the application, which contributes to faster load speed and a smaller footprint.

The IBM TRIRIGA Application Platform installation program installs the Liberty profile components during the installation process.

Installing TRIRIGA Application Platform on a Liberty profile and

Microsoft SQL Server

After your database server is prepared, you can begin to install the TRIRIGA

Application Platform on a Liberty profile and Microsoft SQL Server.

Before you begin

Verify that Microsoft SQL Server is running and that you have administrative authority on the server. Ensure the Microsoft SQL Server database has been configured for TRIRIGA.

Chapter 2. Installing IBM TRIRIGA Application Platform

Procedure

Run the installer file. Follow the installation instructions.

Accept the licenses for both the application and the application platform.

Choose the Java Virtual Machine to use with the installation program. The

64-bit version of Java 7 is required.

Select the installation folder.

For the installation type, select New Database (data.zip required).

For the application server, select IBM WebSphere Liberty (Embedded). Specify the Liberty profile information in the next set of screens.

Specify the application context root for accessing the IBM TRIRIGA application. This path must begin with a slash (/).

Specify the minimum and maximum Java memory setting values in megabytes.

Specify HTTP and HTTPS ports used by the Liberty Profile.

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.

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. For example, if your database administrator pre-created the table space and schema, clear the first option. When you create the database, you must load data using the installation program.

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.

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.

Optional: Select the option to configure your database for multibyte language support. If you do not configure the database for multibyte language support, you can select this option during a future upgrade.

However, if you anticipate supporting multibyte languages in the future, you should configure the database for multibyte language support now.

Optional: Choose a collation for the Microsoft SQL Server database. This screen is displayed if you chose to configure your database for multibyte language support.

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.

Review the URL that the installer is using to test the data schema connection.

Review the results of the test. If the test fails, verify that Microsoft SQL

Server is running.

Specify the minimum and maximum 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.

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.

Optional: Install IBM Tivoli ® Directory Integrator.

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.

When the installation is complete, click Done.

Copy your license files into the tririga_root\config\licenses 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.

v On Windows servers, open a command prompt and run the command to start the Liberty profile. tririga_root\wlp\bin\run.bat

v 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.

What to do next

Verify that your installation is running properly.

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.

Before you begin

Verify that Oracle Database is running and that you have administrative authority on the server. Ensure the Oracle Database database instance and the database have been configured for TRIRIGA.

Procedure

Run the installer file. Follow the installation instructions.

Accept the licenses for both the application and the application platform.

Choose the Java Virtual Machine to use with the installation program. The

64-bit version of Java 7 is required.

Select the installation folder.

For the installation type, select New Database (data.zip required).

For the application server, select IBM WebSphere Liberty (Embedded). Specify the Liberty profile information in the next set of screens.

Specify the application context root for accessing the IBM TRIRIGA application. This path must begin with a slash (/).

Chapter 2. Installing IBM TRIRIGA Application Platform

Specify the minimum and maximum Java memory setting values in megabytes.

Specify HTTP and HTTPS ports used by the Liberty Profile.

For the database type, select Oracle. Consult with your Oracle Database administrator and specify the database information in the next set of screens.

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.

Specify the data schema user name and password. For example, tridata is a typical value for both fields.

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.

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.

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.

Review the URL that the installer is using to test the data schema connection.

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.

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.

Optional: Install IBM Tivoli Directory Integrator.

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.

When the installation is complete, click Done.

Copy your license files into the tririga_root\config\licenses 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

Restart IBM TRIRIGA using the appropriate method.

v On Windows servers, open a command prompt and run the command to start the Liberty profile. tririga_root\wlp\bin\run.bat

v 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.

What to do next

Verify that your installation is running properly.

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 licenses for both the application and the application platform.

Choose the Java Virtual Machine to use with the installation program. The

64-bit version of Java 7 is required.

Select the installation folder.

For the installation type, select New Database (data.zip required).

For the application server, select IBM WebSphere Liberty (Embedded). Specify the Liberty profile information in the next set of screens.

Specify the application context root for accessing the IBM TRIRIGA application. This path must begin with a slash (/).

Specify the minimum and maximum Java memory setting values in megabytes.

Specify HTTP and HTTPS ports used by the Liberty Profile.

For the database type, select IBM DB2. Consult with your IBM DB2 administrator and specify the database information in the next set of screens.

Chapter 2. Installing IBM TRIRIGA Application Platform

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.

Review the URL that the installer is using to test the data schema connection.

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.

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.

Optional: Install IBM Tivoli Directory Integrator.

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.

When the installation is complete, click Done.

Copy your license files into the tririga_root\config\licenses 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

Restart IBM TRIRIGA using the appropriate method.

v On Windows servers, open a command prompt and run the command to start the Liberty profile. tririga_root\wlp\bin\run.bat

v 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.

What to do next

Verify that your installation is running properly.

Installing TRIRIGA Application Platform on IBM WebSphere

Application Server

TRIRIGA Application Platform can be installed on IBM WebSphere Application

Server and supported by a variety of database software. During the TRIRIGA

Application Platform installation process, you can select the type of application server you want to use.

Before you begin

Check the IBM TRIRIGA product wiki for the latest information about deploying

IBM TRIRIGA on IBM WebSphere Application Server.

IBM TRIRIGA can be installed on IBM WebSphere Application Server Network

Deployment, but it does not support deployment into clustered environments. You must install IBM TRIRIGA on the default application server of a single Cell containing a single Node within IBM WebSphere Application Server Network

Deployment. IBM TRIRIGA application data must be stored on the same filesystem as the filesystem used by the IBM WebSphere Application Server host. IBM

TRIRIGA can be configured for high availability through the use of IBM

WebSphere Application Server sticky sessions.

Overview of IBM TRIRIGA Application Platform installation on

WebSphere

Before you begin the IBM TRIRIGA Application Platform installation, IBM

WebSphere Application Server must be installed locally or on a server.

Installation phases

Installing the platform on the WebSphere Application Server involves several phases: v Optionally create a WebSphere Application Server profile for IBM TRIRIGA. If you do not create a new WebSphere Application Server profile specifically for

IBM TRIRIGA, you must be prepared to specify information about an existing profile to use with IBM TRIRIGA during the installation process.

v Running the IBM TRIRIGA installation.

v Manually configuring WebSphere Application Server properties if the installer process fails to deploy the IBM TRIRIGA application.

Timeout property in WebSphere

The IBM TRIRIGA installation with the WebSphere Application Server might fail if the com.ibm.SOAP.requestTimeout property value is not increased. The property can be found in the soap.client.props file of the WebSphere Application Server properties directory. For example, in UNIX, the location might look like:

/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/soap.client.props

Setting the property value to 0 sets the timeout to unlimited.

com.ibm.SOAP.requestTimeout=0

Preparing WebSphere

A WebSphere Application Server profile is required to install IBM TRIRIGA. You can create a WebSphere Application Server profile specifically for IBM TRIRIGA if you do not want to use the default profile. If you do not create a new WebSphere

Application Server profile, you must be prepared to specify information about an

Chapter 2. Installing IBM TRIRIGA Application Platform

existing WebSphere Application Server profile to use with IBM TRIRIGA during the installation process. Refer to WebSphere Application Server product information for details about creating profiles.

Procedure

Enable all WebSphere Application Server profiles to use IBM Java 7.

/QIBM/ProdData/WebSphere/AppServer

/version/edition/bin/managesdk

-enableProfileAll

-sdkname 1.7_64

-enableServers

Set the SDK name that script commands are enabled to use when no profile is specified by the command and when no profile is defaulted by the command.

/QIBM/ProdData/WebSphere/AppServer

/version/edition/bin/managesdk

-setCommandDefault

-sdkname 1.7_64

What to do next

Install the platform with the Oracle Database, IBM DB2, or Microsoft SQL Server.

Installing IBM TRIRIGA Application Platform on WebSphere and

Oracle Database

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 Oracle Database.

Before you begin

Verify that the Oracle Database and IBM WebSphere Application Server are running and that you have administrative authority on the servers.

Procedure

Run the installer file. Follow the installation instructions.

Accept the licenses for both the application and the application platform.

Choose the Java Virtual Machine to use with the installation program. The

64-bit version of Java 7 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.

For the application server, select IBM WebSphere Application Server

(Standalone) . Specify the WebSphere Application Server information in the next set of screens.

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.

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.

Optional: Define an alternative application context path that accesses the

IBM TRIRIGA application. This path must begin with a slash (/).

Specify the minimum and maximum Java memory setting values in megabytes.

Specify the server host name.

For the database type, select Oracle. Consult with your Oracle Database administrator and specify the database information in the next set of screens.

Specify the data schema user name and password. For example, tridata is a typical value for both fields.

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.

Review the URL that the installer is using to test the data schema connection.

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.

Optional: Install IBM Tivoli Directory Integrator.

Review the pre-installation summary and click Install.

Click Next.

Chapter 2. Installing IBM TRIRIGA Application Platform

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.

When the installation is complete, click Done.

Copy your license files into the tririga_root\config\licenses 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

Restart IBM TRIRIGA by locating the WebSphere Application Server directory with the appropriate method.

v On Windows servers, start the WebSphere Application Server service IBM

WebSphere Application Server V8.5 - NODENAME from Control Panel >

Administrative Tools > Services.

v 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 .

v 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.

What to do next

Verify that your installation is running properly.

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.

Before you begin

Verify that the Microsoft SQL Server and IBM WebSphere Application Server are running and that you have administrative authority on the servers.