This guide describes installing the Rational solution for Collaborative Lifecycle Management (CLM) and Design Management applications.
For information on installing the CLM applications on z/OS, see Special considerations for installing on z/OS.
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. | 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 the Network Time Protocol website |
![]() |
Learn about licensing. The licensing scheme for version 6 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 |
![]() |
Learn about query and search index management. These Deployment wiki articles discuss different CLM applications index query information and how it is realized in your CLM deployment. In addition, the second part discusses different administering tasks related to index management and index storage details. | Part 1: Query, search and indexing technologies in CLM Part 2: Indices storage and management (backup, recovery and recreation) |
Planning your environment is critical during the installation process, particularly if you plan to use this installation for departmental or enterprise development. See Examples: Installation process and topology to learn about different installation process and topologies.
Before you begin
Before starting the installation, make sure these tasks are completed:
* hard nofile 65536
* soft nofile 65536
* hard nproc 10000
* soft nproc 10000
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, add the command ulimit -n 65536 to the top of your startup script. This ensures that WebSphere Application Server is started with the correct file descriptor limit.
About this task
There are two ways to download and install CLM applications. 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:
Procedure
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. When you select Non-Administrator, the software packages will be installed in the user's directory and the package group will be named My IBM Collaborative Lifecycle Management. Also on Windows operating systems with User Access Control (UAC) enabled, the user who is installing the applications must be able to write to the installation directories.
If you do not have a supported version of Installation Manager, you can obtain it from Jazz.net or download the web installer, which includes Installation Manager.
.\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
.\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
<!--
<offering id='com.ibm.team.install.jfs.app.rtc'/>
-->
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:
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.
To create database tables, see Creating DB2 for z/OS database tables remotely.
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:
Procedure
db2 create database JTS using codeset UTF-8 territory en PAGESIZE 16384
db2 create database CCM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database QM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database RM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database DCC using codeset UTF-8 territory en PAGESIZE 16384
Note: The Lifecycle Query Engine database requires 32K pages.
db2 create database LQE using codeset UTF-8 territory en PAGESIZE 32768
Note: The Link Index Provider database requires 32K pages.
db2 create database LDX using codeset UTF-8 territory en PAGESIZE 32768
db2 create database GC using codeset UTF-8 territory en PAGESIZE 16384
db2 create database RELM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database DM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database DW using codeset UTF-8 territory en PAGESIZE 16384
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
Due to the parallel processing that Data Collection Component does with data, the database at a given collection will be very active. The following examples are just for guidelines. Adjust these settings accordingly depending on your data load initially and over time.
DB2 UPDATE DB CFG FOR DW USING MAXAPPLS 300
DB2 UPDATE DB CFG FOR DW USING LOCKLIST 20000
DB2 UPDATE DB CFG FOR DW USING LOGFILSIZ 20000
DB2 UPDATE DB CFG FOR DW USING LOGPRIMARY 50
DB2 UPDATE DB CFG FOR DW USING LOGSECOND 200
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 the number of databases you created. 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:
db2 get dbm cfg
db2 update dbm cfg using numdb 32
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
Planning checklistsection of this document.
The examples in this step are for one Oracle database with separate tablespaces and database users who are dedicated to each application.
Procedure
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.
Note: Setting character set to Unicode (AL32UTF8) enables you to store multiple language groups.
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 Rational Engineering Lifecycle Manager application, enter the following command. Replace RELM 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 RELM.DBF with the datafile name that you want to create.
CREATE TABLESPACE RELM
DATAFILE 'ORACLE_BASE/oradata/CLMDB/RELM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Rational Engineering Lifecycle Manager application, enter the following command. Replace RELM_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 RELM_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE RELM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/RELM_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 Requirements Management application, enter the following command. Replace RM 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 RM.DBF with the datafile name that you want to create.
CREATE TABLESPACE RM
DATAFILE 'ORACLE_BASE/oradata/CLMDB/RM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Requirements Management application, enter the following command. Replace RM_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 RM_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE RM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/RM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
To create a tablespace for the Design Management application, enter the following command. Replace DM 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 DM.DBF with the datafile name that you want to create.
CREATE TABLESPACE DM
DATAFILE 'ORACLE_BASE/oradata/CLMDB/DM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Design Management application, enter the following command. Replace DM_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 DM_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE DM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/DM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
To create a tablespace for the Data Collection Component application, enter the following command. Replace DCC 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 DCC.DBF with the datafile name that you want to create.
CREATE TABLESPACE DCC
DATAFILE 'ORACLE_BASE/oradata/CLMDB/DCC.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Data Collection Component application, enter the following command. Replace DCC_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 DCC_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE DCC_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/DCC_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
To create a tablespace for the Lifecycle Query Engine application, enter the following command. Replace LQE 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 LQE.DBF with the datafile name that you want to create.
CREATE TABLESPACE LQE
DATAFILE 'ORACLE_BASE/oradata/CLMDB/LQE.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Lifecycle Query Engine application, enter the following command. Replace LQE_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 LQE_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE LQE_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/LQE_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
To create a tablespace for the Link Index Provider application, enter the following command. Replace LDX 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 LDX.DBF with the datafile name that you want to create.
CREATE TABLESPACE LDX
DATAFILE 'ORACLE_BASE/oradata/CLMDB/LDX.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Link Index Provider application, enter the following command. Replace LDX_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 LDX_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE LDX_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/LDX_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
To create a tablespace for the Global Configuration application, enter the following command. Replace GC 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 GC.DBF with the datafile name that you want to create.
CREATE TABLESPACE GC
DATAFILE 'ORACLE_BASE/oradata/CLMDB/GC.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
To create a temporary tablespace for the Global Configuration application, enter the following command. Replace GC_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 GC_TEMP.DBF with the temporary file name that you want to create.
CREATE TEMPORARY TABLESPACE GC_TEMP
TEMPFILE 'ORACLE_BASE/oradata/CLMDB/GC_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;
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.
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 the 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 the Rational Engineering Lifecycle Manager application tablespace and to grant the required permissions, enter the following commands:
CREATE USER RELM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE RELM QUOTA UNLIMITED ON RELM TEMPORARY TABLESPACE RELM_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO RELM_DB_USER;
To create a user for the 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 Requirements Management application tablespace and to grant the required permissions, enter the following commands:
CREATE USER RM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE RM QUOTA UNLIMITED ON RM TEMPORARY TABLESPACE RM_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO RM_DB_USER;
To create a user for the Design Management application tablespace and to grant the required permissions, enter the following commands:
CREATE USER DM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE DM QUOTA UNLIMITED ON DM TEMPORARY TABLESPACE DM_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO DM_DB_USER;
To create a user for the Data Collection Component application tablespace and to grant the required permissions, enter the following commands:
CREATE USER DCC_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE DCC QUOTA UNLIMITED ON DCC TEMPORARY TABLESPACE DCC_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO DCC_DB_USER;
To create a user for the Lifecycle Query Engine application tablespace and to grant the required permissions, enter the following commands:
CREATE USER LQE_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE LQE QUOTA UNLIMITED ON LQE TEMPORARY TABLESPACE LQE_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO LQE_DB_USER;
To create a user for the Link Index Provider application tablespace and to grant the required permissions, enter the following commands:
CREATE USER LDX_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE LDX QUOTA UNLIMITED ON LDX TEMPORARY TABLESPACE LDX_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO LDX_DB_USER;
To create a user for the Global Configuration Management application tablespace and to grant the required permissions, enter the following commands:
CREATE USER GC_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE GC QUOTA UNLIMITED ON GC TEMPORARY TABLESPACE GC_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO GC_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.
To create the data warehouse without DBA permissions, see this deployment wiki article.
export ORACLE_JDBC_DRIVER_FILE =/Path_to_JDBC_dirver/ojdbc6.jar
Before you begin
This procedure requires that the following prerequisites are met:
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.
For Jazz Team Server
CREATE DATABASE jts
GO
For Change and Configuration Management
CREATE DATABASE ccm
GO
For Rational Engineering Lifecycle Manager
CREATE DATABASE relm
GO
For Quality Management
CREATE DATABASE qm
GO
For Requirements Management
CREATE DATABASE rm
GO
For Design Management
CREATE DATABASE dm
GO
For Data Collection Component
CREATE DATABASE dcc
GO
For Lifecycle Query Engine
CREATE DATABASE lqe
GO
For Link Index Provider
CREATE DATABASE ldx
GO
For Global Configuration
CREATE DATABASE gc
GO
For common data warehouse
CREATE DATABASE dw
GO
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 Rational Engineering Lifecycle Manager
CREATE LOGIN relmDBuser
WITH PASSWORD = 'relmDBpswd';
USE relm;
exec sp_changedbowner 'relmDBuser'
GO
For Quality Management
CREATE LOGIN qmDBuser
WITH PASSWORD = 'qmDBpswd';
USE qm;
exec sp_changedbowner 'qmDBuser'
GO
For Requirements Management
CREATE LOGIN rmDBuser
WITH PASSWORD = 'rmDBpswd';
USE rm;
exec sp_changedbowner 'rmDBuser'
GO
For Design Management
CREATE LOGIN dmDBuser
WITH PASSWORD = 'dmDBpswd';
USE dm;
exec sp_changedbowner 'dmDBuser'
GO
For Data Collection Component
CREATE LOGIN dccDBuser
WITH PASSWORD = 'dccDBpswd';
USE dcc;
exec sp_changedbowner 'dccDBuser'
GO
For Lifecycle Query Engine
CREATE LOGIN lqeDBuser
WITH PASSWORD = 'lqeDBpswd';
USE lqe;
exec sp_changedbowner 'lqeDBuser'
GO
For Link Index Provider
CREATE LOGIN ldxDBuser
WITH PASSWORD = 'ldxDBpswd';
USE ldx;
exec sp_changedbowner 'ldxDBuser'
GO
For Global Configuration
CREATE LOGIN gcDBuser
WITH PASSWORD = 'gcDBpswd';
USE gc;
exec sp_changedbowner 'gcDBuser'
GO
For common data warehouse
CREATE LOGIN DWuser
WITH PASSWORD = 'DWpswd';
USE dw;
exec sp_changedbowner 'DWuser'
GO
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 Rational Engineering Lifecycle Manager
ALTER DATABASE relm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Quality Management
ALTER DATABASE qm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Requirements Management
ALTER DATABASE rm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Design Management
ALTER DATABASE dm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Data Collection Component
ALTER DATABASE dcc COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Lifecycle Query Engine
ALTER DATABASE lqe COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Link Index Provider
ALTER DATABASE ldx COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For Global Configuration
ALTER DATABASE gc COLLATE SQL_Latin1_General_CP437_CS_AS
GO
For common data warehouse
ALTER DATABASE dw COLLATE SQL_Latin1_General_CP1_CS_AS
GO
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 Rational Engineering Lifecycle Manager
ALTER DATABASE relm SET READ_COMMITTED_SNAPSHOT ON
GO
For Quality Management
ALTER DATABASE qm SET READ_COMMITTED_SNAPSHOT ON
GO
For Requirements Management
ALTER DATABASE rm SET READ_COMMITTED_SNAPSHOT ON
GO
For Design Management
ALTER DATABASE dm SET READ_COMMITTED_SNAPSHOT ON
GO
For Data Collection Component
ALTER DATABASE dcc SET READ_COMMITTED_SNAPSHOT ON
GO
For Lifecycle Query Engine
ALTER DATABASE lqe SET READ_COMMITTED_SNAPSHOT ON
GO
For Link Index Provider
ALTER DATABASE ldx SET READ_COMMITTED_SNAPSHOT ON
GO
For Global Configuration
ALTER DATABASE gc SET READ_COMMITTED_SNAPSHOT ON
GO
SQLSERVER_JDBC_DRIVER_FILE =.:Path_to_JDBC_dirver/sqljdbc4.jar
Starting in version 6.0.1, Apache Tomcat is not provided as a default application server. However, Apache Tomcat is supported and you can use it. Complete the following steps to download and install Apache Tomcat.
The following method copies the Tomcat files to the Jazz Team Server installation directory and the examples show Apache Tomcat installed in this location: JazzInstallDir. If you install Tomcat in another location, change the installation path.
When you set up a new installation of CLM to run on Apache Tomcat, you must update some of the default Tomcat configuration files before you start the application server.
By default, all Tomcat port numbers are in the 8000 range. In CLM products, the default port numbers are in the 9000 range. If you want to change the default 8080 (HTTP) and 8443 ( HTTPS) port numbers, complete these steps:
If you want to use secure (HTTPS) connections, you must create or obtain a security certificate for SSL/TLS. You can either generate a self-signed certificate or obtain one from a certificate authority. For more information, see Installing a security certificate and SSL/TLS Configuration HOW-TO (apache.tomcat.org) .
In the following example, change my-ssl.keystore and my-ssl-password to the actual keystore file name and password. If you copy the .keystore file to TomcatHome, no path is required. Otherwise, provide a full path to the .keystore file.
After you create the .keystore file, make the following changes in the server.xml file:
<Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
<Connector SSLEnabled="true"
URIEncoding="UTF-8"
acceptCount="100"
algorithm="${jazz.connector.algorithm}"
ciphers="SSL_DHE_RSA_WITH_AES_128_CBC_SHA,SSL_DHE_DSS_WITH_AES_256_CBC_SHA,SSL_DHE_RSA_WITH_AES_256_CBC_SHA,SSL_DHE_RSA_WITH_AES_128_CBC_SHA256,SSL_DHE_DSS_WITH_AES_128_CBC_SHA256,SSL_DHE_RSA_WITH_AES_256_CBC_SHA256,SSL_DHE_RSA_WITH_AES_128_GCM_SHA256,SSL_DHE_DSS_WITH_AES_128_GCM_SHA256,SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA,SSL_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,SSL_ECDHE_RSA_WITH_AES_256_CBC_SHA,SSL_ECDHE_RSA_WITH_AES_128_GCM_SHA256,SSL_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,SSL_ECDHE_RSA_WITH_AES_256_GCM_SHA384,SSL_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA256,SSL_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,SSL_ECDHE_RSA_WITH_AES_256_CBC_SHA384,SSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,SSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_AES_128_CBC_SHA,SSL_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA"
clientAuth="false"
connectionTimeout="20000"
disableUploadTimeout="true"
enableLookups="false"
keystoreFile="my-ssl.keystore"
keystorePass="my-ssl-password"
maxHttpHeaderSize="8192"
maxThreads="150"
minSpareThreads="25"
port="9443"
protocol="HTTP/1.1"
scheme="https"
secure="true"
sslEnabledProtocols="${jazz.connector.sslEnabledProtocols}"/>
<Connector enableLookups="false"
port="9009"
protocol="AJP/1.3"
redirectPort="9443"
sslEnabledProtocols="${jazz.connector.sslEnabledProtocols}"/>
If you use Jazz Security Architecture single sign-on, Apache Tomcat does not authenticate users, so no configuration is required for the user registry.
If you install more than one CLM application on the same Tomcat instance, complete these steps to enable Tomcat single sign-on:
<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
If you use an LDAP user registry, follow the instructions in Manually configuring the Apache Tomcat web container to use LDAP to configure Tomcat to use your LDAP registry.
Complete the following steps to update the Tomcat user registry.
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml"
readonly="false"/>
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
digest="SHA-1"
digestEncoding="UTF-8"
resourceName="UserDatabase"/>
In previous releases of CLM, access logging was disabled by default to improve performance. If you do not use access logging, insert comment tags around the following section in the server.xml file:
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log." suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" />
-->
You must define the standard Jazz security roles and create an administrative user account. In previous releases, a predefined ADMIN user with the ADMIN password was used for the initial administrative login. Now, you can define any user name and password in the tomcat-users.xml file. To define Jazz security roles and create a default user, complete these steps:
<tomcat-users>
<role rolename="JazzUsers"/>
<role rolename="JazzAdmins"/>
<role rolename="JazzGuests"/>
<role rolename="JazzProjectAdmins"/>
<role rolename="manager-gui"/>
<user username="ADMIN" password="ADMIN" roles="JazzUsers,JazzAdmins,JazzProjectAdmins"/>
</tomcat-users>
The password must be entered in clear text in the tomcat-users.xml file, and then encrypted by completing the following steps.
cd JazzInstallDir/server\server
repotools-jts -convertTomcatUsers tomcatUsersPath=JazzInstallDir/server/tomcat/conf/\server\tomcat\conf\tomcat-users.xml
You are now ready to start the Apache Tomcat server.
server.startup.bat -tomcat
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.
Tip: To stop the server, you can enter server.shutdown.bat -tomcat
./server.startup -tomcat
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.
Tip: To stop the server, you can enter ./server.shutdown -tomcat
Before you begin
About this task
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
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.
You are ready to start the Liberty server.
cd JazzInstallDir\server
server.startup.bat
cd JazzInstallDir/server
./server.startup
The clm_was_config.py script configures WebSphere Application Server and sets up security options so that you can run CLM applications in a WebSphere environment.
Before you begin
Ensure you have completed the following tasks:
Procedure
createJVMCustomProperty(jvm, "DB2Z_JDBC", "/etc/jazz/server/db2z", "")
createJVMCustomProperty(jvm, "ORACLE_JDBC_DRIVER_FILE", "C:\app\user\product\11.2.0\dbhome_1\jdbc\lib\ojdbc6.jar", "")
createJVMCustomProperty(jvm, "ORACLE_JDBC_DRIVER_FILE", "/opt/app/user/product/11.2.0/dbhome_1/jdbc/lib/ojdbc6.jar", "")
createJVMCustomProperty(jvm, "SQLSERVER_JDBC_DRIVER_FILE", "C:\MSSQL\jdbc\sqljdbc4.jar", "")
createJVMCustomProperty(jvm, "SQLSERVER_JDBC_DRIVER_FILE", "/opt/mssql/jdbc/sqljdbc4.jar", "")
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the conf directory.
cd WAS_Profile_Dir\bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/Jazz_Install_Dir/server/was/clm_was_config.py C:/Jazz_Install_Dir/server/conf
cd WAS_Profile_Dir/bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /opt/Jazz_Install_Dir/server/was/clm_was_config.py /opt/Jazz_Install_Dir/server/conf
cd WAS_Profile_Dir\bin
stopServer.bat server1 -user WAS_USER -password WAS_PASSWORD
startServer.bat server1
cd WAS_Profile_Dir/bin
./stopServer.sh server1 -user WAS_USER -password WAS_PASSWORD
./startServer.sh server1
Before you begin
Ensure you have completed the following tasks:
Procedure
-Xmx4g -Xms4g -Xmn1g
-Xgcpolicy:gencon -Xnocompressedrefs
-XX:MaxDirectMemorySize=1G
-Xmx4g -Xms4g -Xmn1g
-XX:MaxPermSize=768M -XX:ReservedCodeCacheSize=512M -XX:CodeCacheMinimumFreeSpace=2M
-Xmx4g -Xms4g -Xmn1g
-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/4} with 1/4 of the total memory. For example, if -Xmx is set to 8g, -Xmn should be set to 2g.
-Xmx{N} -Xms{N} -Xmn{N/4}
For Rational DOORS Next Generation only: The -Xmn value should be 33% of the -Xms value. For example, if the -Xmx size is 4gb, the -Xmn should be 1365m. The following Deployment wiki document contains useful information about Rational DOORS Next Generation sizing and tuning: Sizing and tuning guide for Rational DOORS Next Generation 6.0: configuration management.
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.
To avoid problems, do not use spaces in file paths. You can use double quotation marks to enclose the path.
Step mand add these custom properties:
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.
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.
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.
You can use clm_deploy.py or clm_deploy_distributed.py in a distributed environment to deploy application WAR files. These scripts also map the appropriate security roles for JTS, CCM, and QM applications.
Before you begin
Ensure that WebSphere Application Server, Jazz Team Server, and CLM applications are installed prior to running the script.
Complete the following steps to map the security roles to your LDAP groups. Note that the groups must be setup on the LDAP server prior to completing this mapping.
# Example of how to set role/mapping for jts.war
AdminApp.edit('jts.war', '[-MapRolesToUsers [["JazzAdmins" No No "" admins]["JazzDWAdmins" No No "" admins]["JazzUsers" No No "" users]["JazzGuests" No No "" users]["JazzProjectAdmins" No No "" admins]]]')
AdminConfig.save()
Use the following examples to modify the role/mapping for the application:
# Set role/mapping for jts.war
AdminApp.edit('jts.war', '[-MapRolesToUsers [["JazzAdmins" No No "" cn=JazzAdmins,cn=members,o=ldap.server.com]["JazzUsers" No No "" cn=JazzUsers,cn=members,o=ldap.server.com]["JazzGuests" No No "" cn=JazzGuests,cn=members,o=ldap.server.com]["JazzProjectAdmins" No No "" cn=JazzProjectAdmins,cn=members,o=ldap.server.com]]]')
AdminConfig.save()
# Set role/mapping for ccm.war
AdminApp.edit('ccm.war', '[-MapRolesToUsers [["JazzAdmins" No No "" cn=JazzAdmins,cn=members,o=ldap.server.com]["JazzUsers" No No "" cn=JazzUsers,cn=members,o=ldap.server.com]["JazzGuests" No No "" cn=JazzGuests,cn=members,o=ldap.server.com]["JazzProjectAdmins" No No "" cn=JazzProjectAdmins,cn=members,o=ldap.server.com]]]')
AdminConfig.save()
# Set role/mapping for qm.war
AdminApp.edit('qm.war', '[-MapRolesToUsers [["JazzAdmins" No No "" cn=JazzAdmins,cn=members,o=ldap.server.com]["JazzUsers" No No "" cn=JazzUsers,cn=members,o=ldap.server.com]["JazzGuests" No No "" cn=JazzGuests,cn=members,o=ldap.server.com]["JazzProjectAdmins" No No "" cn=JazzProjectAdmins,cn=members,o=ldap.server.com]]]')
AdminConfig.save()
About this task
The clm_deploy.py script installs all application WAR files that are available in the webapps directory into a single WebSphere Application Server node.
The clm_deploy_distributed.py script can be used to install any application WAR files that are available in the webapps directory, if you specify them in your command argument as a comma-separated list.
Note: The web archive applications must have a .war extension.
Procedure
To deploy applications on a single WebSphere Application Server, complete this step:
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the webapps directory.
cd WAS_Profile_Dir\bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/Jazz_Install_Dir/server/was/clm_deploy.py nodeName server1 C:/Jazz_Install_Dir/server/webapps
cd cd WAS_Profile_Dir/bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /opt/Jazz_Install_Dir/server/was/clm_deploy.py nodeName server1 /opt/Jazz_Install_Dir/server/webapps
To deploy applications in a distributed WebSphere Application Server environment, complete this step:
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the webapps directory.
cd WAS_Profile_Dir\bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/Jazz_Install_Dir/server/was/clm_deploy_distributed.py nodeName server1 C:/Jazz_Install_Dir/server/webapps jts,ccm,clmhelp
cd cd WAS_Profile_Dir/bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /opt/Jazz_Install_Dir/server/was/clm_deploy_distributed.py /opt/Jazz_Install_Dir/server/webapps jts,ccm,clmhelp
cd WAS_Profile_Dir\bin
stopServer.bat server1 -user WAS_USER -password WAS_PASSWORD
startServer.bat server1
cd WAS_Profile_Dir/bin
./stopServer.sh server1 -user WAS_USER -password WAS_PASSWORD
./startServer.sh server1
Before you begin
Procedure
Depending on the CLM applications that you installed, the following web applications might be available for deployment:
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.
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.
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.
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.
For information about configuring the server, see Configuring the server on IBM i.
To configure your WebSphere Liberty to use an LDAP registry to authenticate users, see Configuring an LDAP connection.
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.
After installing the applications, databases, and starting the Jazz Team Server and other applications, 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 Liberty Basic User Registry. The wizard will detect and set up the applications that you have just installed.
Procedure
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 or an IP address.
The Custom setup wizard takes you through setting up your database, configuring email settings, configuring the user registry, and registering applications.
Before you begin
Set up the databasestep in this document.
Procedure
Tip: See Client access license management overview for information on how licenses can provide different levels of access to the capabilities in the applications in the current release.
Note: If you select J2EE for connection type, you must also set the resultSetHoldability property to 1 in WebSphere Application Server. By default, this property is set to 2. If you do not set this property to 1, some of the data warehouse collection jobs might fail. For more information about resultSetHoldability, see your WebSphere Application Server documentation.
If you do not configure the data warehouse, your applications will be functional but you will not be storing any reporting data and most reports will not work.
You can run the setup command from a command-line to set up databases, configure email settings, configure the user registry, and register any applications you have just installed.
The setup command is a repository tools command that allows you to set up a Jazz Team Server and associated applications without using the setup wizard. The command may be run in interactive mode to help capture the response file needed to drive future automated installations. See Repository tools command to configure the server for the explanation of each parameter that you can use with the command.
Before you begin
Prior to running the setup command, you must have installed the Jazz Team Server and any CLM applications, created your databases, and deployed and started the applications on your application server.
Note: If you are using a Derby database, before running the setup command, ensure that the location of the database and data warehouse in the Jazz_Install_Dir_6.0.1/server/conf/jts/teamserver.propertiesJazz_Install_Dir_6.0.1\server\conf\jts\teamserver.properties file is an absolute path. For example: com.ibm.team.repository.db.jdbc.location=Jazz_Install_Dir_6.0.1/conf/jts/derby/repositoryDB and com.ibm.team.datawarehouse.db.jdbc.location=Jazz_Install_Dir_6.0.1/conf/jts/derby/warehouseDB.
Procedure
cd Jazz_Install_Dir_6.0.1\server
repotools-jts.bat -setup repositoryURL=https://qulified.hostname.com:9443/jts adminUserID=ADMINWAS_ADMIN_ID adminPassword=ADMINWAS_ADMIN_PASSWORD
cd Jazz_Install_Dir_6.0.1/server
./repotools-jts.sh -setup repositoryURL=https://qulified.hostname.com:9443/jts adminUserID=ADMINWAS_ADMIN_ID adminPassword=ADMINWAS_ADMIN_PASSWORD
I understand that once the Public URI is set, it cannot be modified except with additional administrative commands, which can result in broken links from other applications that do not support changing URLs.
Choose Confirm Public URI:
[1] I understand
[2] Cancel and exit setup - default
[1] JDBC - Default
[2] J2EE
[1] Derby - default
[2] DB2
[3] SQL Server
[4] DB2 for z/OS
[5] DB2i
[6] Derby Net
[7] Oracle
For example:
conf/jts/derby/repositoryDB
//localhost:50000/JTS:user=db2admin;password={password};
thin:jtsDBuser/{password}@localhost:1521/CLMDB
//localhost:1433;databaseName=jts;user=jtsDBuser;password={password};
//ipAddress:ipPort/location:user=jtsDBuser;password={password};
[1] LIBERTY
[2] Tomcat
[3] LDAP
[4] Non-LDAP External Registry
If you selected LDAP, the logged in user information is imported. If you selected Non-LDAP, the password is not required.
[1] Disable - default
[2] Do Not Disable
Note: A local application is an application that is installed under the same application server as Jazz Team Server and its details can be discovered. A non-local application is either installed in a distributed environment or not installed in the same application server as Jazz Team Server and its details must be provided by the user.
The following table displays the applications that can be registered with Jazz Team Server with their context root and discovery URL:
Application Name | Context root | Discovery URL |
Change and Configuration Management Quality Management Requirements Management Rational Engineering Lifecycle Manager Global Configuration Management Design Management Link Index Provider Report Builder Data Collection Component Lifecycle Query Engine |
/ccm /rqm /rm /relm /gc /dm /ldx /rs /dcc /lqe |
https://server.example.org:9443/ccm/scr https://server.example.org:9443/rqm/scr https://server.example.org:9443/rm/scr https://server.example.org:9443/relm/scr https://server.example.org:9443/gc/scr https://server.example.org:9443/dm/scr https://server.example.org:9443/ldx/scr https://server.example.org:9443/rs/scr https://server.example.org:9443/dcc/scr https://server.example.org:9443/lqe/scr |
If the data warehouse has not been set up or a Derby database is being used then no password is required. Otherwise, enter a password for data warehouse. This step might take a few minutes.
The VVCMODEL.VERSION table in the following database is not indexed by the setup procedure. After you run the setup and create your database tables, you must run the following commands to create index files for the VVCMODEL.VERSION table to optimize the database.
ALTER TABLE VVCMODEL.VERSION ALTER COLUMN CONCEPT NVARCHAR(450) NOT NULL
ALTER TABLE VVCMODEL.VERSION ALTER COLUMN STORAGE NVARCHAR(450) NULL
CREATE INDEX VERSION_CONCEPT_DX ON VVCMODEL.VERSION (CONCEPT)
CREATE INDEX VERSION_STORAGE_DX ON VVCMODEL.VERSION (STORAGE)
For detailed instructions about activating configuration management and enabling project areas including a link to obtain an activation key, see Getting started for application administrators.
Related links
This Jazz.net article also provides useful information about configuration management.
After running the setup wizard and registering the LQE application, you must log on to the server and assign the required permission.
After you install and start the server, you can use Data Collection Component to collect data from the registered applications and load them into the data warehouse. For detailed instructions, see Collecting data with the Data Collection Component.
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.
After installing and setting up the Design Management server, you can install the components such as import engines, client extensions, sample projects and so on. For detail instructions, see Installing Rational Rhapsody components.
After installing and setting up the Design Management server, you can install the components such as import engines, client extensions, sample projects and so on. For detail instructions, see Installing Rational Software Architect components.
To configure Kerberos server and client single-sign-on authentication, see Configuring Kerberos single-sign-on authentication.