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.
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 |
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.
Before you begin
Before starting the installation, make sure these tasks are completed:
Note: On IBM AIX® platforms, do not use the jar command to extract the package. Use the unzip command.
ulimit -n 65536
ulimit -u 10000
* 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, 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:
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.
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.
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.
.\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'/>
-->
The following is the overview of the installation sequence for a new installation using IBM i authentication and WebSphere Application Server V7 or V8:
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.
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:
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 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
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:
db2 get dbm cfg
db2 update dbm cfg using numdb 8
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 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 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;
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 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.
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 Quality Management
CREATE DATABASE qm
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 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
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
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
SQLSERVER_JDBC_DRIVER_FILE =.:Path_to_JDBC_dirver/sqljdbc4.jar
You are now ready to start the Apache Tomcat server.
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.
server.shutdown.bat
./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.
./server.shutdown
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:
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 the 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 the Set up the database
step.
In a clustered environment updates the following settings:
Procedure
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
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.
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
wsadmin.bat -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy.py nodeName serverName JazzInstallDir/server/tomcat/webapps/
./wsadmin.sh -language jython -user WAS_username -password WAS_password -f path_to_the_script/clm_deploy.py nodeName serverName JazzInstallDir/server/tomcat/webapps/
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
./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
./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/
./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:
Note: 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.
Before you begin
Ensure you have completed the following tasks:
Procedure
-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}
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 nand 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.
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.
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.
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 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
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.
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
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.
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.
com.ibm.team.repository.db.jdbc.location=JazzInstallDir/server/conf/jts/derby/repositoryDB
com.ibm.team.datawarehouse.db.jdbc.location=JazzInstallDir/server/conf/jts/derby/warehouseDB
com.ibm.team.fulltext.indexLocation=JazzInstallDir/server/conf/jts/indices/workitemindex
com.ibm.team.jfs.index.root.directory=JazzInstallDir/server/conf/jts/indices
com.ibm.team.repository.db.jdbc.location=JazzInstallDir/server/conf/ccm/derby/repositoryDB
com.ibm.team.datawarehouse.db.jdbc.location=//localhost\:1527/JazzInstallDir/server/conf/jts/derby/warehouseDB
com.ibm.team.fulltext.indexLocation=JazzInstallDir/server/conf/ccm/indices/workitemindex
com.ibm.team.jfs.index.root.directory=JazzInstallDir/server/conf/ccm/indices
com.ibm.team.repository.db.jdbc.location=JazzInstallDir/server/conf/qm/derby/repositoryDB
com.ibm.team.datawarehouse.db.jdbc.location=//localhost\:1527/JazzInstallDir/server/conf/jts/derby/warehouseDB
com.ibm.team.fulltext.indexLocation=JazzInstallDir/server/conf/qm/indices/workitemindex
com.ibm.team.jfs.index.root.directory=JazzInstallDir/server/conf/qm/indices
log4j.appender.file.File=JazzInstallDir/server/logs/jts.log
log4j.appender.etl.File=JazzInstallDir/server/logs/jts-etl.log
log4j.appender.etlDriver.File=JazzInstallDir/server/logs/jts-etl-driver.log
log4j.appender.etlfilter.File=JazzInstallDir/server/logs/etl-filter.log
log4j.appender.file.File=JazzInstallDir/server/logs/admin.log
log4j.appender.file.File=JazzInstallDir/server/logs/ccm.log
log4j.appender.etl.File=JazzInstallDir/server/logs/ccm-etl.log
log4j.appender.file.File=JazzInstallDir/server/logs/qm.log
log4j.appender.etl.File=JazzInstallDir/server/logs/qm-etl.log
log4j.appender.rmLog.File=JazzInstallDir/server/logs/rm.log
log4j.appender.rmPerfLog.File=JazzInstallDir/server/logs/rmPerfLog.log
log4j.appender.rmPerfSnap.File=JazzInstallDir/server/logs/rmPerfSnapshots.log
log4j.appender.rrdg.File=JazzInstallDir/server/logs/rrdg.log
log4j.appender.rmFilter.File=JazzInstallDir/server/logs/rmfilter.log
Note: If you do not provide paths for the log files, the log files will be written to JazzInstallDir\server\tomcat\bin\logs.
Procedure
cd JazzInstallDir\server\tomcat\bin
sc query tomcat7
If the service is installed, uninstall it by entering this command:
sc delete tomcat7
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
JazzInstallDir\server\jre\bin\j9vm\jvm.dll
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
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.
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.