Design Management interactive installation guide

This guide describes installing Design Management and the Rational solution for Collaborative Lifecycle Management (CLM) applications. (Jazz Team Server, Rational Software Architect Design Management or Rhapsody Design Managment, Rational Team Concert, Rational Requirements Composer, and Rational Quality Manager)

For information on installing the CLM applications on z/OS, see Special considerations for installing on z/OS.

Select the options that best describe your installation environment

Select one or more applications to install:
Select the operating system for your application server:
Select your installation method:
Select your database server:
Select your application server:
Select your user registry type:
Are you configuring a data warehouse?
Do you want to install Rational Reporting for Development Intelligence?

To install the Rational solution for CLM applications follow these steps:

Planning checklist

Before you install the Rational solution for Collaborative Lifecycle Management applications, ensure to review the information in the following planning checklist.

  Planning task More information
Verify that your hardware and software meet the minimum system requirements. There are new requirements for version 4.0.x like supporting only 64-bit server operating systems. System requirements
Get the product installation media. For local repository download, you need approximately five gigabytes (5 GB) of hard drive space to download and extract your product installation media. The server installation files can be downloaded from jazz.net
Review your installation topology. Whether you are trying out the CLM solution, or installing the solution in your production environment, click the link at the right to see and study different installation topology examples. The examples include: evaluation topology, departmental topology, and distributed enterprise topology. Installation process and topology examples
Synchronize the clocks on all machines. In a distributed environment, ensure that the clocks on all machines are synchronized using the Network Time Protocol (NTP). For more information about NTP, visit ntp.org
Learn about licensing. The licensing scheme for version 4 is role-based. When you purchase a role-based license, you will have read, write, and comment access to some or all of the capabilities of the Change and Configuration Management, Quality Management, and Requirements Management applications. Client access license management

Installation process example

Planning your environment is critical during the installation process, particularly if you plan to use this installation for departmental or enterprise development. The Installation process example topic includes a diagram that displays the main steps for the installation.

Install the server

Before you begin

Before starting the installation, make sure these tasks are completed:

  • If you used your environment to install a CLM product for trial or demo, you must uninstall and remove any CLM-related application directories before continuing a fresh installation. For more information see, Uninstalling Jazz Team Server and the Rational solution for Collaborative Lifecycle Management applications.
  • To install the servers and applications for the Rational solution for Collaborative Lifecycle Management (CLM), you must obtain the installation files. You can download either the Web Installer or the Installation Manager repository package for your platform form Jazz.net download section.
  • You must have IBM® Installation Manager 1.6 or later for your platform. The Web Installer downloads contain Installation Manager. The easiest way to proceed is to get the Web Installer download for your platform.
  • You must have an Installation Manager response file that is tailored for the to install. The Web Installer downloads contain sample response files for installing each of the available products.
  • You must have the Installation Manager repositories for each of the to install. These repositories are available in the All Downloads section of the product downloads page.
  • Extract the downloaded .zip file to a temporary directory. To avoid issues, do not use long paths and directories that have spaces in their names. Extract any other Installation Manager repository files that you download into the same directory as the Web Installer.

    Note: On IBM AIX® platforms, do not use the jar command to extract the package. Use the unzip command.

  • The response files contain an example command-line invocation that uses the -acceptLicense argument. Before attempting a command-line installation, review the license agreement that is included in the /license directory at the top-level of the product download. Use the -acceptLicense argument on the command-line to indicate acceptance of this license agreement.
  • Each response file contains a line that refers to the Installation Manager repository to be used during installation. Edit the repository location attribute to point to the repository.config file in the directory that you extracted the Installation Manager repository files to.
  • Before you can install and run CLM applications on your IBM AIX® system, you must increase the limit of open files:
    1. Start smit.
    2. Go to Security & Users > Users > Change/Show Characteristics of a User.
    3. Enter the User ID under which the Jazz Team Server is running.
    4. Enter a value of 65536 in the Soft NOFILE descriptors and Hard NOFILE descriptors fields.
    5. Enter a value of 10000 in the Soft NPROC per user and Hard NPROC per user fields.
    6. Logout and log back in to the system.
    7. Before starting Tomcat WebSphere Application Server, run ulimit -n to see if the configuration took effect. The output must be 65536.
    8. Also before starting Tomcat WebSphere Application Server, run ulimit -u to see if the configuration took effect. The output must be 10000.
  • Unless you plan to perform a silent installation, a supported browser is required to install the with a graphical user interface and IBM Installation Manager. You can download the Firefox browser for AIX at Download Firefox.
  • The browser must be included in the $PATH environment variable. If the launchpad.sh program for IBM Installation Manager cannot find the browser, an error message will be displayed.
  • To run WebSphere Application Server 8.0.0.3 on AIX 6.1 or 7.1, you must upgrade your AIX server with the following fixes:
  • Before you can install and run CLM applications on your Solaris system, you must increase the limit of open files and user processes. You can increase the limits within a running shell with this commands:

    ulimit -n 65536
    ulimit -u 10000

  • Start the launchpad program or IBM Installation Manager from the same shell to inherit the modified limits.
  • Before you can install and run CLM applications on your Linux system, you must increase the limit of open files and user processes:
    1. As a root user add the following lines to the /etc/security/limits.conf file:

      * hard nofile 65536
      * soft nofile 65536
      * hard nproc 10000
      * soft nproc 10000

    2. Restart the Linux system after the limits.conf file is modified.
  • If Security-Enhanced Linux (SELinux) is enabled, you must disable it or change the security context of the Java Runtime Environment (JRE) to allow text relocation. For more information, see Installing with Security-Enhanced Linux.
  • The CLM applications installation path names must not contain spaces. The startup script (JazzInstallDir/server/server.startup) and the repository tools script (JazzInstallDir/server/repotools-app.sh) detect and report this problem.
  • The Reports component requires that 32-bit X11 libraries be installed on the server. On Redhat Enterprise Linux 5, the required packages are libXp, libXinerama, mesa-libGL, and compat-libstdc++-33.
  • You must have the GTK x32 libraries available in your Linux system to be able to open the Installation Manager link from the launchpad program. For more information, see this article on jazz.net.
  • When running the CLM applications, there are logs and other files that can be modified and written in the installation directory. For all users to be able to write to the installation directory, you must manually grant write permissions to the JazzInstallDir.

Important: If you use a system startup script such as /etc/init.d/was or /etc/rc.*/SXXWebSphere to start WebSphere® Application Server at system boot up time, init.d invokes the startup scripts with the maximum number of file descriptors set to 1024 instead of the system default value that is set in /etc/security/limits.conf (65536). To avoid this problem, after a system boot up, manually run /etc/init.d/was restart from a root shell. This will ensure that WebSphere Application Server is restarted with the correct file descriptor limit.

About this task

There are two ways to download and install CLM . The first installation method is a web-based installation that includes a smaller download and connects to the Internet during the installation to get the repository files. If you must install the server in an environment without Internet access, use the second installation method: download and extract the repository files to a local computer to install the server.

If you do not have User Interface libraries installed on your server or just prefer to use the command-line installation method, you can use an IBM Installation Manager response file to install Rational Collaborative Lifecycle Manager . This method is also referred to as silent installation.

There are two sample response files provided to install Jazz Team Server and CLM applications:

  • silent-install-server.xml: Use this script to produce an installation of the Rational Solution for CLM applications in the C:\tmp\silent-install\JazzTeamServer/tmp/silent-install/JazzTeamServer directory that can be compressed and relocated on the file system, or to other computers with the same operating system and architecture. To use this script, you must have Installation Manager installed on your server.
  • silent-install-server2.xml: Use this script to install the Rational Solution for CLM applications in the default installation location. If you do not have Installation Manager, this script will install Installation Manager on your server before continuing with the CLM installation.

In addition to the server sample response files, these additional component sample response files are also included:
  • silent-install-buildsystem.xml: Installs Build System Toolkit
  • silent-install-cc-connector.xml: Installs Rational ClearCase Synchronizer
  • silent-install-client.xml: Installs Rational Team Concert - Client for Eclipse IDE
  • silent-install-cq-connector.xml: Installs Rational ClearQuest Synchronizer
  • silent-install-jazz-msscci.xml: Installs Rational Team Concert MS-SCCI provider
  • silent-install-vs-client.xml: Installs Rational Team Concert - Client for Microsoft Visual Studio
  • silent-install-windows-shell-client.xml: Installs Rational Team Concert Windows Explorer Shell

Procedure

  1. Extract the downloaded .zip file to a temporary directory. To avoid issues, do not use long paths and directories that have spaces in their names.
  2. Install by using either the web installer or the Installation Manager repository package.
    • To install by using the web installer:
      1. Open the directory that you extracted the .zip file to, and run the launchpad executable file. The launchpad opens.

        Note: If you want to install the product as a non-root usernon-administrator user, from the Select user mode for Installation Manager list, select Non-Administrator.

      2. Follow the steps in the launchpad to continue the installation. As you follow the steps in the launchpad, Installation Manager opens to install the software packages.
    • To install by using the Installation Manager repository package:
      1. Start Installation Manager.

        If you do not have Installation Manager version 1.6 or later, you can obtain it from Jazz.net or download the web installer, which includes Installation Manager version 1.6.

      2. Click File > Preferences, and then select Add Repository.
      3. To specify the repository location, browse to the directory where you downloaded the .zip file and open the repository.config file.
      4. Click OK, and then click Install to start the installation process.
      5. Follow the instructions in Installation Manager to complete the installation.

What to do next

Verify that the Start the Jazz Team Server and Stop the Jazz Team Server menu options are available from the Windows Start menu. To check for the menu options, click Start > All Programs > IBM Collaborative Lifecycle Management.

Verify that the Start the Jazz Team Server and Stop the Jazz Team Server menu options are available from the Applications menu of your Linux distribution.

  1. Open a command prompt and change to the ExtractedDir\im\win32.win32.x86 directory.
  2. Open a command shell and change to the ExtractedDir/im/linux.gtx.x86 directory.
  3. Open a command shell and change to the ExtractedDir/im/linux.gtx.ppc directory.
  4. Open a command shell and change to the ExtractedDir/im/linux.gtx.s390 directory.
  5. Open a command shell and change to the ExtractedDir/im/solaris.gtk.sparc directory.
  6. Open a command shell and change to the ExtractedDir/im/aix.motif.ppc directory.
  7. To install as an administrator into a shared area, use the installc variant in the following command:

    .\installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini

    ./installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini

  8. To install into a user-specific location use the userinstc variant in the following command:

    .\userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini

    ./userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini

  9. To remove an application from being installed, search for the application name and comment out or delete the line. For example, if you do not want to install Change and Configuration Management application, search for rtc and delete or comment out the offering line:

    <!--
    <offering id='com.ibm.team.install.jfs.app.rtc'/>
    -->

Installing the server on IBM i

The following is the overview of the installation sequence for a new installation using IBM i authentication and WebSphere Application Server V7 or V8:

  1. Restore the CLM 4.0.3 licensed program.
  2. Run CL command QJTS403/CFGJAZZSVR to configure and start the Jazz Team Server. By default, the Jazz Team Server application is deployed to the WebSphere Application Server V7.1 server and the URL for server admin page is https://[example.com]:29443/jts/admin. Use JTSADMIN/JTSADMPWD to access this page.

For step-by-step instructions for new installations of Jazz Team Server, see Installing Jazz Team Server and CLM applications on IBM i.

For detailed instructions for installing the Build System Toolkit and the context-aware search engine, see the following resources:

Set up the database

If you are using the included Derby database, no additional setup is necessary. Proceed with the next step.

Note: Although a Derby database is included in the default configuration and requires no installation, this database is limited to 10 users. To enable more users, install a supported enterprise database such as DB2, Oracle, or SQL Server.

Note: The Requirements Management application uses the same database as Jazz Team Server.

The Rational solution for Collaborative Lifecycle Management products support IBM DB2 Enterprise Server Edition. For platforms that do not support Enterprise Server Edition, you can use IBM DB2 Workgroup Server Edition. You can obtain a trial download of one these DB2 editions or the free DB2 Express Server edition for deployments of 50 developers or fewer from ibm.com.

Before you begin

This procedure requires that the following prerequisites are met:

  • The databases are not partitioned. Partitioned databases are not supported in this release and must not be used.
  • You have the correct user password. In the UNIX systems, get the password for the DB2 instance owner, which is typically the db2inst1 user.
  • You have reviewed the DB2 documentation to verify that your system meets the requirements and is configured correctly.
  • DB2 is installed and running on a computer to be used as the database server. This computer can be different from the one that the Jazz Team Server runs on.

Procedure

  1. Open a DB2 command window.
  2. Enter this command to create a database for Jazz Team Server called JTS with 16K pages and the UTF-8 code set:

    db2 create database JTS using codeset UTF-8 territory en PAGESIZE 16384

  3. Enter this command to create a database for Change and Configuration Management application called CCM with 16K pages and the UTF-8 code set:

    db2 create database CCM using codeset UTF-8 territory en PAGESIZE 16384

  4. Enter this command to create a database for Quality Management application called QM with 16K pages and the UTF-8 code set:

    db2 create database QM using codeset UTF-8 territory en PAGESIZE 16384

  5. Enter this command to create a database for your data warehouse called DW with 16K pages and the UTF-8 code set:

    db2 create database DW using codeset UTF-8 territory en PAGESIZE 16384

  6. Note: If you are creating the database with a user other than the user specified in the teamserver.properties file, you must grant DBADM authority to that user:

    db2 connect to database name
    db2 grant dbadm on database to user user name
    db2 disconnect database name

Verify

If you create all CLM databases on the same database server, verify that the Max number of concurrently active databases is set to a number greater than 4. If this value is lower than the number of active databases, you will get the SQL Code 1041 error.

Do these steps to verify and increase the number if necessary:

  1. Open a DB2 command window and enter this command to display the database manager configuration:

    db2 get dbm cfg

  2. Look for the Max number of concurrently active databases line. If this number is lower than the installed databases, increase the number to 8 by entering this command:

    db2 update dbm cfg using numdb 8

  3. Stop and start the database manager for these changes to take effect by entering these commands:

    db2stop
    db2start

To create and set up an Oracle database, it is assumed that the user who is preparing the database has database administration authority over the database and that the database, tablespace storage, and appropriate storage configuration is created by a user with system administration authority.

Before you begin

  • The required Java Database Connectivity (JDBC) driver for both Oracle 10g and 11g is ojdbc6.jar.
  • For a list of supported database versions, see the system requirements link in the Planning checklist section of this document.
  • The configuration parameters and tablespace options used in this step are examples and might not entirely apply to your environment. For example, if you cannot use the AUTOEXTEND setting, then the files must be large enough to allow for growth. Or if you cannot use the UNLIMITED size quota for the Jazz Team Server database user, then make sure to allow enough space for rapid growth.
  • If you install the Rational solution for Collaborative Lifecycle Management (CLM) applications on the same computer or distributed platforms, you can either create separate databases for each application or you can use the same database for all applications. However, you must create a separate tablespace and a database user who is associated with that tablespace for each application.

    The examples in this step are for one Oracle database with separate database users who are dedicated to each application.

  • The database that you create for the Jazz Team Server and all CLM applications must be formatted to use UTF-8 as the character set. By default, Oracle does not create a database with the UTF-8 character set. When you create a new database, ensure that you select AL32UTF8 in the Oracle DB setup.

Procedure

  1. As a system administrator, create a database with UTF-8 encoding for the Jazz Team Server and all applications.
    1. Start the Database Configuration Assistant wizard and on the Welcome page click Next.
    2. On the Operations page, select Create a Database and then click Next.
    3. On the Templates page, select Custom Database and click Next.
    4. In both the Global Database Name and SID fields, enter a name for the content storage database, for example, CLMDB. Click Next.
    5. To configure the database control, enter the required information for alert notification and optionally enable the daily disk backup schedule. To continue without database control configuration, clear the check box next to Configure Enterprise Manager and then click Next.
    6. On the Database Credentials page, choose an option for your user account, and then click Next.

      Note: Oracle password complexity policy requires that passwords should have minimum of 8 characters in length. In addition, the password must contain at least one upper-case character, one lower-case character, and one digit.

    7. On the next page, select a storage type and location for database files. Click Next.
    8. On the next page, choose a recovery option for the database, and then click Next.
    9. On the next page, specify whether or not to add the Sample Schemas to your database. Click Next.
    10. On the next page, click the Character Sets tab and select Use Unicode (AL32UTF8). Click Next.

      Note: Setting character set to Unicode (AL32UTF8) enables you to store multiple language groups.

    11. On the Database Storage page verify or change the database objects and click Next.
    12. On the next page click Finish to create the database.
    13. On the Confirmation window that opens, optionally save the page as an HTML file, and then click OK. A progress bar is displayed to show the database creation progress.
  2. Open an SQL *Plus window and log in as SYSTEM or SYSDBA.

    To create a tablespace for Jazz Team Server, enter the following command. Replace JTS with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and JTS.DBF with the datafile name that you want to create.

    CREATE TABLESPACE JTS
    DATAFILE 'ORACLE_BASE/oradata/CLMDB/JTS.DBF'
    SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

    To create a temporary tablespace for Jazz Team Server, enter the following command. Replace JTS_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and JTS_TEMP.DBF with the temporary file name that you want to create.

    CREATE TEMPORARY TABLESPACE JTS_TEMP
    TEMPFILE 'ORACLE_BASE/oradata/CLMDB/JTS_TEMP.DBF'
    SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

    To create a tablespace for the Change and Configuration Management application, enter the following command. Replace CCM with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and CCM.DBF with the datafile name that you want to create.

    CREATE TABLESPACE CCM
    DATAFILE 'ORACLE_BASE/oradata/CLMDB/CCM.DBF'
    SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

    To create a temporary tablespace for the Change and Configuration Management application, enter the following command. Replace CCM_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and CCM_TEMP.DBF with the temporary file name that you want to create.

    CREATE TEMPORARY TABLESPACE CCM_TEMP
    TEMPFILE 'ORACLE_BASE/oradata/CLMDB/CCM_TEMP.DBF'
    SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

    To create a tablespace for the Quality Management application, enter the following command. Replace QM with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and QM.DBF with the datafile name that you want to create.

    CREATE TABLESPACE QM
    DATAFILE 'ORACLE_BASE/oradata/CLMDB/QM.DBF'
    SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

    To create a temporary tablespace for the Quality Management application, enter the following command. Replace QM_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and QM_TEMP.DBF with the temporary file name that you want to create.

    CREATE TEMPORARY TABLESPACE QM_TEMP
    TEMPFILE 'ORACLE_BASE/oradata/CLMDB/QM_TEMP.DBF'
    SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

    To create a tablespace for the common data warehouse, enter the following command. Replace DW with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and DW.DBF with the datafile name that you want to create.

    CREATE TABLESPACE DW
    DATAFILE 'ORACLE_BASE/oradata/CLMDB/DW.DBF'
    SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

    To create a temporary tablespace for the common data warehouse, enter the following command. Replace DW_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with the database name you created in step a, and DW_TEMP.DBF with the temporary file name that you want to create.

    CREATE TEMPORARY TABLESPACE DW_TEMP
    TEMPFILE 'ORACLE_BASE/oradata/CLMDB/DW_TEMP.DBF'
    SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

  3. In the Oracle Enterprise Manager Database Control, click Server > Tablespaces and verify that the tablespaces you created are displayed and accessible. Also ensure that the default Oracle tablespace named USERS already exist. If this tablespace does not exist in your Oracle database, create it.

  4. Create an Oracle database user for each new tablespace.

    After the tablespaces are created, a special Oracle user must be created for each application to use the Oracle database. For multiple Jazz servers that run on one Oracle database, an Oracle database user must be created for each application. The Oracle database user must be able to create database objects in its tablespace (either unlimited or with a space quota) with privileges to create session, table, procedure, and views.

    To create a user for Jazz Team Server tablespace and to grant the required permissions, enter the following commands:

    CREATE USER JTS_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE JTS QUOTA UNLIMITED ON JTS TEMPORARY TABLESPACE JTS_TEMP;

    GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO JTS_DB_USER;

    To create a user for Change and Configuration Management application tablespace and to grant the required permissions, enter the following commands:

    CREATE USER CCM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE CCM QUOTA UNLIMITED ON CCM TEMPORARY TABLESPACE CCM_TEMP;

    GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO CCM_DB_USER;

    To create a user for Quality Management application tablespace and to grant the required permissions, enter the following commands:

    CREATE USER QM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE QM QUOTA UNLIMITED ON QM TEMPORARY TABLESPACE QM_TEMP;

    GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO QM_DB_USER;

    To create a user for common data warehouse tablespace and to grant the required permissions, enter the following commands:

    CREATE USER DW_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE DW QUOTA UNLIMITED ON DW TEMPORARY TABLESPACE DW_TEMP;

    GRANT DBA TO DW_USER;

    Note: The creation of the data warehouse on Oracle requires more permissions as compared to other databases. When you specify the database user in the connection spec for data warehouse, ensure that the database user has DBA permissions. You can change this permission after the data warehouse is created. For more information, see Completing the installation.

  5. Create an environment variable named ORACLE_JDBC_DRIVER_FILE and point to the ojdbc6.jar JDBC driver. The location can vary depending on the Oracle product and operating system. You can download the supported Oracle JDBC driver (ojdbc6.jar) from www.oracle.com.
    1. Click Start > Control Panel > System.
    2. Click the Advanced tab, and then click Environment Variables.
    3. In the System variables list, click New.
    4. In the Variable name enter ORACLE_JDBC_DRIVER_FILE, and in the Variable value enter C:\Path_to_JDBC_dirver\ojdbc6.jar.
    1. Open a shell window.
    2. Enter the following environment variable declaration:

      ORACLE_JDBC_DRIVER_FILE =.:Path_to_JDBC_dirver/ojdbc6.jar

Before you begin

This procedure requires that the following prerequisites are met:

  • The service is started.
  • The Java Database Connectivity (JDBC) driver is installed. To download the JDBC driver, go to Microsoft JDBC Driver 4.0 for SQL Server.
  • The TCP protocol is enabled for SQL Server.
  • The user who creates the database table must be a member in the sysadmin fixed server role, or an owner of the database (dbo).
  • Ensure that your server security is in mixed mode. You can verify the mode by checking the server security. It should be set to SQL Server and Windows Authentication Mode.

Procedure

Set up the SQL Server database by using the sqlcmd command line tool, which is provided with the SQL Server installation. You can also use a visual tool, such as SQL Server Studio Management.

Important: If you install Rational solution for CLM applications either on the same computer or distributed platforms, a separate database and a database user who is associated with that database must be created.

  1. Enter the following command to create a database for each application:

    For Jazz Team Server

    CREATE DATABASE jts
    GO

    For Change and Configuration Management

    CREATE DATABASE ccm
    GO

    For Quality Management

    CREATE DATABASE qm
    GO

    For common data warehouse

    CREATE DATABASE dw
    GO

  2. Create a user and password and change the ownership of the database by entering these commands:

    For Jazz Team Server

    CREATE LOGIN jtsDBuser
    WITH PASSWORD = 'jtsDBpswd';
    USE jts;
    exec sp_changedbowner 'jtsDBuser'
    GO

    For Change and Configuration Management

    CREATE LOGIN ccmDBuser
    WITH PASSWORD = 'ccmDBpswd';
    USE ccm;
    exec sp_changedbowner 'ccmDBuser'
    GO

    For Quality Management

    CREATE LOGIN qmDBuser
    WITH PASSWORD = 'qmDBpswd';
    USE qm;
    exec sp_changedbowner 'qmDBuser'
    GO

    For common data warehouse

    CREATE LOGIN DWuser
    WITH PASSWORD = 'DWpswd';
    USE dw;
    exec sp_changedbowner 'DWuser'
    GO

  3. Change the collation of the databases. From the command line tool, type this command:

    For Jazz Team Server

    ALTER DATABASE jts COLLATE SQL_Latin1_General_CP437_CS_AS
    GO

    For Change and Configuration Management

    ALTER DATABASE ccm COLLATE SQL_Latin1_General_CP437_CS_AS
    GO

    For Quality Management

    ALTER DATABASE qm COLLATE SQL_Latin1_General_CP437_CS_AS
    GO

    For common data warehouse

    ALTER DATABASE dw COLLATE SQL_Latin1_General_CP1_CS_AS
    GO

  4. Change the row version system for the database. From the command line tool, run this command:

    Note: Ensure that the connection to the database is open before running this command.

    For Jazz Team Server

    ALTER DATABASE jts SET READ_COMMITTED_SNAPSHOT ON
    GO

    For Change and Configuration Management

    ALTER DATABASE ccm SET READ_COMMITTED_SNAPSHOT ON
    GO

    For Quality Management

    ALTER DATABASE qm SET READ_COMMITTED_SNAPSHOT ON
    GO

  5. Create an environment variable named SQLSERVER_JDBC_DRIVER_FILE and point to the sqljdbc4.jar JDBC driver. The location of the driver varies depending on your installation.
    1. Click Start > Control Panel > System.
    2. Click the Advanced tab, and then click Environment Variables.
    3. In the System variables list, click New.
    4. In the Variable name enter SQLSERVER_JDBC_DRIVER_FILE, and in the Variable value enter C:\Path_to_JDBC_dirver\sqljdbc4.jar.
    1. Open a shell window.
    2. Enter the following environment variable declaration:

      SQLSERVER_JDBC_DRIVER_FILE =.:Path_to_JDBC_dirver/sqljdbc4.jar

Start the Apache Tomcat server

You are now ready to start the Apache Tomcat server.

  1. To start the server, open a command prompt and change to the JazzInstallDir\server directory.
  2. Enter this command:

    server.startup.bat

    Note: A separate Apache Tomcat console window opens. If you close this window, the server stops. Depending on your installation options, the server startup might take a few minutes. After the server is started, the startup time in millisecond is displayed in the Tomcat window. For example, a line like this might be displayed: Server startup in 203645 ms.

    Important: If the server is installed in the default Program Files directory, to be able to write to this directory, you must run the startup program as an administrator in Windows Server 2008 R2 or Windows 7.

  3. To stop the server, enter this command:

    server.shutdown.bat

  1. To start the server, open a command shell and change to the JazzInstallDir/server directory.
  2. Enter this command:

    ./server.startup

    Note: A separate Apache Tomcat console window does not open. You can check the server startup progress by viewing the JazzInstallDir/server/logs/jts.log file.

    After you access the server for the first time, the logs directory under JazzInstallDir/server is created.

  3. To stop the server, enter this command:

    ./server.shutdown

Set up WebSphere Application Server by using Jython

Before you begin

Make sure WebSphere Application Server is installed, a profile is created, and the server is started prior to running clm_was_config.py.

About this task

The clm_was_config.py Jython script performs the following tasks:

In a clustered environment updates the following settings:

Procedure

  1. To setup WebSphere Application Server, open a command windowshell and change the directory to WASInstallDir\AppServer\profiles\profile_name\binWASInstallDir/AppServer/profiles/profile_name/bin. If you have more than one profile under the profiles directory, select the profile that you want to be used for the CLM installation.
  2. Enter the following command substituting WAS_username with the WebSphere Application Server admin username, WAS_password with the admin user password, path_to_the_script with the location of the script, for example, C:/Progra~1/IBM/JazzTeamServer/server/was/clm_was_config.py opt/JazzTeamServer/server/was/clm_was_config.pyand JazzInstallDir/server/conf with the path to the Jazz Team Server installation configuration directory. To avoid problems, do not use spaces in the path. You can use double quotation marks for paths with spaces.

    Note: On Windows platforms, you must use forward slashes for the path to the installation configuration and the script directories. For example, C:/Progra~1/IBM/JazzTeamServer/server/conf.

    wsadmin.bat -language jython -user WAS_username -password WAS_password -f Path_to_the_script/clm_was_config.py JazzInstallDir/server/conf

    ./wsadmin.sh -language jython -user WAS_username -password WAS_password -f Path_to_the_script/clm_was_config.py JazzInstallDir/server/conf

Manage federated file-based user registry

Jazz Team Server uses J2EE container managed authentication for login and system permissions. For application server to work, you must configure a realm with the application server. The file-based user registry is useful for testing or evaluation, because Jazz Team Server does not support importing users or mapping user roles. For the full application functionality, including viewing system user roles and importing users, Jazz Team Server supports an LDAP realm.

Configure the federated repositories

  1. In the WebSphere Integrated Solutions Console, click Security > Global security.
  2. Make sure Enable administrative security and Enable application security check boxes are selected.
  3. From the Available realm definitions select Federated repositories and click Configure.
  4. In the Primary administrative user name field, type the WebSphere Application Server administrative ID.
  5. Under Server user identity, make sure Automatically generated server identity is selected. Click OK and then save.
  6. Set Federated repositories as the current realm definition by clicking Set as Current.
  7. Stop and restart the WebSphere Application Server.

Setting up groups and users

To be able to run Jazz Team Server, you need to define groups and users in the WebSphere Application Server repository and map them to Jazz groups. Before Installing any CLM applications, you must create the user groups.

  1. In the WebSphere Integrated Solutions Console, click Users and Groups > Manage Groups.
  2. Click Create and create the following group names:
    • JazzAdmins
    • JazzDWAdmins
    • JazzProjectAdmins
    • JazzUsers
    • JazzGuests
  3. In the Users and Groups section, click Manage Users.
  4. Click Create and enter a name in the User ID field to create a user in the JazzAdmins group.
  5. Click Group Membership and then click Search.
  6. Select JazzAdmins from the Available window and then click Add, to add JazzAdmins to the Mapped To window.
  7. Click Close and in the Create a User page fill in the remaining required fields. Click Create.
  8. Click Create Like and create other users and assign them to the appropriate Jazz group membership.

Deploy web applications by using Jython

Before you begin

About this task

The Jython script files install the following CLM applications, if available:

There are two Jython script files that you can use to deploy web applications:

Procedure

  1. Open a command prompt and change the directory to WASInstallDir/AppServer/profiles/profile_name/bin. If you have more than one profile under the profiles directory, select the profile that you want to be used for the CLM installation.
  2. For a single application server deployment, enter this command:

    wsadmin.bat -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy.py nodeName serverName JazzInstallDir/server/tomcat/webapps/

  3. For a single application server deployment, enter this command:

    ./wsadmin.sh -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy.py nodeName serverName JazzInstallDir/server/tomcat/webapps/

  4. For multiple application servers deployment, enter this command:

    wsadmin.bat -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy_distributed.py nodeName serverName JazzInstallDir/server/tomcat/webapps/ jts,qm,ccm

  5. For multiple application servers deployment, enter this command:

    ./wsadmin.sh -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy_distributed.py nodeName serverName JazzInstallDir/server/tomcat/webapps/ jts,qm,ccm

  1. Open a command prompt and change the directory to WASInstallDir/AppServer/profiles/profile_name/bin. If you have more than one profile under the profiles directory, select the profile that you want to be used for the CLM installation.
  2. For a single application server cluster, enter this command:

    ./wsadmin.sh -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy_cluster.py nodeName clusterName JazzInstallDir/server/tomcat/webapps/

  3. For multiple application servers cluster, enter this command:

    ./wsadmin.sh -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy_cluster_distributed.py nodeName clusterName JazzInstallDir/server/tomcat/webapps/ jts,qm,ccm

Where:

Set up the WebSphere Application Server

Before you begin

Ensure you have completed the following tasks:

  • WebSphere Application Server is already installed and running.
  • You have the administrative username and password.
  • Verify or update the WebSphere Application Server level. For a list of supported versions and fix packs, see the Detailed System Requirements page.
  • On Unix systems, ensure that the Open File Limit value is properly set. For more information, see Planning to install on UNIX and Linux systems.
  • The database is created. If you use the default Derby database for evaluation purposes, ensure the location to the database in the teamserver.properties file is an absolute path.

Procedure

  1. Open a browser and login to WebSphere Integrated Solutions Console at https://hostname.example.com:9043/ibm/console/logon.jsp.
  2. The Java 2 Security option must be turned off. If this option is turned on in WebSphere Application Server, the web application will not start.
    1. Click Security > Global security.
    2. Under Java 2 security, clear the check box for Use Java 2 security to restrict application access to local resources.
    3. Ensure that the Enable administrative security and Enable application security check boxes are selected.
  3. To ensure that the LTPA cookies are secure, enable the Requires SSL setting:
    1. Click Security > Global security > Web and SIP security > Single sign-on(SSO).
    2. Click the Requires SSL check box.
    3. Click OK and Save directly to the master configuration.
  4. Also ensure that the Use available authentication data when an unprotected URI is accessed application server security setting is selected.
    1. Click Security > Global security > Web and SIP security > General settings.
    2. Click the Use available authentication data when an unprotected URI is accessed check box.
    3. Click OK and Save directly to the master configuration.
  5. Add the following session management custom property to avoid SESN0008E error message when a user logs out without terminating the session:
    1. Click Servers > Server Types > WebSphere application servers.
    2. Click server1 and then in the Container Settings section, click Session management.
    3. In the Additional Properties section, click Custom properties.
    4. Click New and enter the following information:
      • Name: InvalidateOnUnauthorizedSessionRequestException
      • Value: true
    5. Click Apply and save directly to the master configuration.
  6. To improve performance of the operating procedures, change the WebContainer thread pool size settings:
    1. Click Servers > Server Types > WebSphere application servers.
    2. Click server1 and then in the Additional Properties section, click Thread pools.
    3. In the Thread pools page, click WebContainers.
    4. Enter 200 in the Minimum Size and Maximum Size fields.
    5. Click OK and save directly to the master configuration.
  7. Jazz Team Server requires several specific settings on the Java Virtual Machine in which it runs. To set these properties, click Servers > Server Types > WebSphere application servers > server1.
  8. Under Server Infrastructure, click Java and Process Management > Process definition.
  9. Under Additional Properties, click Java Virtual Machine.
  10. Add the value 4096 to Initial Heap.
  11. Add the value 4096 to Maximum Heap Size.
  12. In the Generic JVM arguments field, type the following line:

    -Xmx4g -Xms4g -Xmn512m
    -Xgcpolicy:gencon -Xnocompressedrefs
    -XX:MaxDirectMemorySize=1G

    -Xmx4g -Xms4g -Xmn512m
    -XX:MaxPermSize=768M -XX:ReservedCodeCacheSize=512M -XX:CodeCacheMinimumFreeSpace=2M
    -XX:MaxDirectMemorySize=1G

    -Xmx4g -Xms4g -Xmn512m
    -Xgcpolicy:gencon -Xcompressedrefs
    -Xgc:preferredHeapBase=0x100000000
    -XX:MaxDirectMemorySize=1G

    Tip: If you need more heap size, then you can use the following setting, replacing {N} with the amount of memory to be used and {N/8} with 1/8 of the total memory. For example, if -Xmx is set to 8g, -Xmn should be set to 1g.

    -Xmx{N} -Xms{N} -Xmn{N/8}

  13. Click Apply, and then click Save directly to the master configuration.
  14. One of the custom properties you must add is JAZZ_HOME, a system property that specifies where to find certain configuration files. This property uses a URL rather than a simple path, so specify the value as a file-style URL: file:///file_path. Under Java Virtual Machine > Additional Properties, click Custom properties. You must use three forward slashes (///) after file:.

    In a distributed environment, when you are using a separate application server for each web application, you must add these custom properties for each instance of the WebSphere Application Server.

  15. Click New, enter JAZZ_HOME in the Name field, and enter file:///JazzInstallDir/server/conf in the Value field. Substitute JazzInstallDir with the location of Jazz Team Server installation directory. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer/server/conf if the server is installed in /opt/IBM, enter file:////opt/IBM/JazzTeamServer/server/conf.

    To avoid problems, do not use spaces in file paths. You can use double quotation marks to enclose the path.

  16. Click OK.
  17. Repeat Step n and add these custom properties:
    • Name: java.awt.headless Value: true
    • Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin Value: true
    • Name: ORACLE_JDBC_DRIVER_FILE Value: Absolute_path_to_the_JDBC_driver/ojdbc6.jar

      Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:///). For more information about Oracle Java Database Connectivity (JDBC) connections, see Set up the database step.

    • Name: SQLSERVER_JDBC_DRIVER_FILE Value: Absolute_path_to_the_JDBC_driver/sqljdbc4.jar

      Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:///). For more information about SQL Server JDBC connections, see Set up the database step.

    • Name: startup_log4j.configuration Value: file:///JazzInstallDir/server/conf/startup_log4j.properties

      The settings that the startup_log4j.properties file contains are used at the early stages in the startup process to pass messages to the WebSphere Application Server SystemOut.log file. After the early stages, each Jazz application switches to using the application-specific settings from the JazzInstallDir/server/conf/app_context/log4j.properties file.

  18. Click Save directly to the master configuration.
  19. For changes to take effect, restart the application server.

Deploy web applications (.WAR files)

Before you begin

  • Make sure WebSphere Application Server is installed and started.
  • You have access the .WAR files. If you used IBM Installation Manager to install the CLM applications and during the installation cleared the check box for Install Tomcat 7, by default, the web application files (.WAR) are copied into the JazzInstallDir/server/webapps directory. If during installation you selected Install Tomcat 7, the web application files (.WAR) are copied into the JazzInstallDir/server/tomcat/webapps directory.
  • If WebSphere Application Server is installed in a non-root environment, the user who deploys the CLM applications must have read and write access to the installation directory and all subdirectories.
  • Uninstall WebSphere Application Server default applications (DefaultApplication, ivtApp, and query) if they are installed with the profile. Jazz Team Server and CLM applications do not use these applications and for security and performance reasons they can be removed.

Procedure

  1. Open a browser and login to WebSphere Integrated Solutions Console at https://hostname.example.com:9043/ibm/console/logon.jsp.
  2. Click Applications > New Application > New Enterprise Application.
  3. On the Path to the new application page, select Remote file system and browse for the application.war file. Click Next.

    Depending on the CLM applications that you installed, the following web applications might be available for deployment:

    • jts.war
    • admin.war
    • clmhelp.war
    • ccm.war
    • qm.war
    • rm.war
    • converter.war

  4. Select Fast Path, and then click Next.
  5. Click Next to accept all default options until you reach the Map context roots for web modules page.
  6. In the Map context roots for web modules, set Context Root for Jazz Team Server to /jts, for Lifecycle Project Administration to /admin, for Information Center to /clmhelp, for Change and Configuration Management application to /ccm, for Quality Management application to /qm, for Requirements Management application to /rm, for Converter application to /converter, and then click Next.
  7. Click Finish.
  8. Verify that your application was installed correctly and then click Save directly to the master configuration.

Map security roles to a user or repository group

The jts_war, qm_war, and ccm_war applications must have the same authentication methods for their users and use the same security group mapping.

  1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
  2. For Jazz Team Server, click the jts_war application to open it for editing.
  3. For Change and Configuration Management, click the ccm_war application to open it for editing.
  4. For Quality Management, click the rqm_war application to open it for editing.
  5. In the Detail Properties section, click Security role to user/group mapping.
  6. Select a specific repository group, such as JazzAdmins or JazzUsers, and click Map groups.

    These repository groups are associated with every Jazz implementation and must be mapped to a particular group that contains the authorized users. If you are using LDAP, these groups must be set up on the LDAP server prior to completing this mapping. If you are mapping these repository groups to individual users, select the repository group and click Map Users.

  7. Enter a search string to return your users or group names. Click Search to run the query.
  8. From the list of available users or groups that is returned, select the particular user or group and move it to the Selected column.
  9. Click OK to map the users or groups to the Jazz repository groups.
  10. Save the changes.

Note: If in the future there will be changes to the LDAP configuration level, you must remap the security roles to the user or repository group for JTS and other installed applications.

Start the server

  1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
  2. Select the check box next to these applications, and then click Start:
    • jts_war
    • admin_war
    • clmhelp_war
    • ccm_war
    • qm_war
    • rm_war
    • converter_war

    A green arrow should appear that indicates the application is successfully started.

    Note: The Converter application is supported only on Windows and Linux. For installation instructions on other unsupported platforms, see the Delegated Configuration section of Requirements Management Converter Application Configuration and Troubleshooting Guide.

Configure the server on IBM i

For information about configuring the server, see Configuring the server on IBM i.

Deploy a clustered environment

A clustered environment enables you to configure a group of alike servers, and to load balance client requests across those servers.

Note: Due to complexity of setting up and testing clustering topologies, only clustering with WebSphere Network Development (ND) is supported in this release. The WebSphere eXtreme Scale (WXS) is included and installed to support clustering, but it may be necessary to buy additional WXS licenses to support larger clusters or multi-datacenter topologies.

To deploy a clustered environment, see Deploying a clustered environment with WebSphere Application Server ND.

Manage users by configuring LDAP

To configure your Apache Tomcat to use an LDAP registry to authenticate users, see the topics under Managing users by using LDAP.

To configure your WebSphere Application Server to use an LDAP registry to authenticate users, see Enabling LDAP on WebSphere Application Server.

Run the setup wizard

After installing the applications, databases, and starting the servers, you can login to the Jazz Team Server (jts/setup) page and run the setup wizard to configure the servers.

The Express setup is a simplified version of the wizard that lets you set up the default Derby database and Tomcat User Registry. The wizard will detect and set up the applications that you have just installed.

Procedure

  1. Point your web browser to the following address: https://hostname.example.com:9443/jts/setup.
  2. Type ADMIN (case-sensitive) in both the User ID and Password fields. Click Log In.
  3. On the Welcome page, select Express Setup. Click Next.
  4. On the Configure Public URI page, provide a Public URI that is of the form https://[fully qualified hostname]:9443/jts and select the check box to confirm that you have read and understood the recommendations on this page. Click Test Connection. After the test is successful, click Next.

    Important: A [fully qualified hostname] is the host name along with the DNS domain reference of the machine on which the Jazz Team Server is installed. An example of a good [fully qualified hostname] is hostname.example.com. Examples of bad [fully qualified hostname] are localhost and an IP address.

  5. On the Create Administrative User page, create an administrative user by providing a user ID, full name, password, and email address. This new administrative user ID will replace the default ADMIN user. Click Next.
  6. The Setup Progress page is open and displays each step of the progress. A green check mark denotes that the step was successful. After setting up the application is 100% complete, click Next.
  7. On the Assign Licenses page, if necessary, click Activate Trial for the required licenses. This opens the License Agreement page for a selected license. Read and accept the license agreement, and then click Finish.
  8. After activating the required licenses, click Finish. This opens the Server Administration page where you can perform additional administrative and project management tasks such as, managing the server, users, and licenses. For more information, see Administering Rational solution for Collaborative Lifecycle Management servers.

The Custom setup wizard takes you through setting up your database, configuring email settings, configuring the user registry, and registering applications.

Before you begin

  • For new installations, if you do not want to use the default port numbers, you must change them before you use the setup wizard. For more information, see Changing the port numbers for the application server.
  • Databases must be created before running the setup wizard. Make sure that you performed the Set up the database step in this document.
  • On a single server topology, the wizard detects and allows you to set up the applications that you have just installed. In a distributed environment, first install and start Jazz Team Server and all applications on each individual server and make note of the applications discovery URL. Then, run the setup wizard on the server where Jazz Team Server is installed and on the Register Applications page provide the discovery URL of the applications that are installed on the other servers.

Procedure

  1. Point your web browser to the following address: https://hostname.example.com:9443/jts/setup.
  2. Type ADMIN (case-sensitive) in both the User ID and Password fields. Click Log In.
  3. Log in with your WebSphere Administrative ID that is a member of JazzAdmins user group.
  4. Log in as an LDAP registered user who has JazzAdmins privileges. Note that the LDAP user or group must be mapped to the repository group.
  5. Follow the instructions in the setup wizard to complete the installation. For more information, see Running the setup by using Custom setup in the setup wizard.

Register applications with Jazz Team Server

If you did not register your application during the Jazz Team Server setup wizard, you can login to the Administration page to register them. For detailed information, see Registering applications with Jazz Team Server.

Configure Apache Tomcat server to run as a Windows service

To run Jazz Team Server as a Windows service, you must configure tomcat7.exe that ships with Jazz Team Server.

Before you begin

Note: To avoid problems, do not use spaces in file paths. For example, for the Program Files directory you can use PROGRA~1 or for Program Files (x86) directory you can use PROGRA~2. Also make sure to use forward slashes (/) in the properties files.

Prepare the following .properties files by providing absolute paths. In these steps, JazzInstallDir refers to the location where the Rational solution for Collaborative Lifecycle Management applications are installed.

Procedure

  1. Set the CATALINA_HOME variable by following these steps:
    1. From Windows Control Panel, open the System Properties window.
    2. Click the Advanced tab, then click Environment Variables.
    3. Under System variables, click New.
    4. In Variable name enter CATALINA_HOME and in Variable value enter JazzInstallDir\server\tomcat.
  2. Open a command prompt and check that the service is not installed by entering this command:

    cd JazzInstallDir\server\tomcat\bin
    sc query tomcat7

    If the service is installed, uninstall it by entering this command:

    sc delete tomcat7

  3. Restart your system for the CATALINA_HOME variable to take effect and to finish removing the tomcat7 service if you deleted it in the previous step.
  4. Open a command prompt and install the new service by entering this command:

    Note: On Windows operating systems that have User Account Control (UAC) such as Windows 7, the command prompt must be run as an administrator.

    cd JazzInstallDir\server\tomcat\bin
    service.bat install tomcat7

  5. Run the JazzInstallDir\server\tomcat\bin\tomcat7w.exe program to configure the service.
  6. Click the Java tab, and clear the Use default check box.
  7. Add the following path to the Java Virtual Machine. You can also click the ellipsis icon to browse for the jvm.dll file.

    JazzInstallDir\server\jre\bin\j9vm\jvm.dll

  8. Add the following lines at the end of the Java Options text field:

    Important: The path to -DJAZZ_HOME and -Dlog4j.configuration must be a URL path. Note the three forward slashes (///) after file: and forward slashes in the path. The path to the tempDir location must be an absolute file path.

    -DJAZZ_HOME=file:///JazzInstallDir/server/conf
    -Djava.awt.headless=true
    -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true
    -Dcom.ibm.team.repository.tempDir=JazzInstallDir\server\tomcat\temp
    -Djazz.connector.sslProtocol=SSL_TLS
    -Djazz.connector.algorithm=IbmX509
    -Dlog4j.configuration=file:///JazzInstallDir/server/conf/startup_log4j.properties
    -Xgcpolicy:gencon
    -Xcompressedrefs
    -Xgc:preferredHeapBase=0x100000000
    -XX:MaxDirectMemorySize=1G
    -Xmx4G
    -Xms4G
    -Xmn512M

    If your Jazz Team Server is installed on a Windows platform, but you are using the DB2 for z/OS database server, add this line substituting the path with the driver location. The path to the driver location must be a file path and note the forward slash.

    -DDB2Z_JDBC=JazzInstallDir/server/db2z

    If you are using the Oracle database, add this line substituting the path with the driver location. The path to the Oracle JDBC driver location must be an absolute file path.

    -DORACLE_JDBC_DRIVER_FILE=OJDBCLocation\ojdbc6.jar

    If you are using the SQL Server database, add this line substituting the path with the driver location. The path to the SQL Server JDBC driver location must be an absolute file path.

    -DSQLSERVER_JDBC_DRIVER_FILE=SQLJDBCLocation\sqljdbc4.jar

    If you are using the Oracle Java Runtime Environment 6.0, you must also add the following lines:

    -XX:+UnlockDiagnosticVMOptions
    -XX:+UnsyncloadClass

  9. In both Initail memory pool and Maximum memory pool, change the pool size value to 4096.
  10. On the Startup and Shutdown tabs, make sure that jvm is selected for the Mode setting.
  11. Click the General tab and change the Startup type to Automatic to start the service automatically when Windows starts.
  12. After the service starts, verify that the server is running by logging on to the server from your browser.

Install the Rational Team Concert client for Eclipse IDE

After installing and setting up the server, you can install the Rational Team Concert Eclipse client to connect to the server. To install the client for Eclipse IDE by using IBM Installation Manager, see Installing the Rational Team Concert Eclipse client by using Installation Manager.

Install Rational Reporting for Development Intelligence

The reporting capabilities can be used to measure and monitor software or systems delivery capabilities using metrics. Implementing measures improves the management's ability to visualize and communicate the affect of changes in an organization or development lifecycle. For a list of system requirements for data warehouse and the report server, see Hardware and software requirements.

To install Rational Reporting for Development Intelligence, see the Rational Reporting for Development Intelligence interactive installation guide.