Manually configuring a DB2 database

Running the setup wizard is the recommended method to configure the database connections and create the database tables. If you prefer to do this procedure manually, use this topic to edit the teamserver.properties file to set up an IBM DB2 database connection and run the -createTables command to create database tables.

Procedure

To create a database, see Setting up a DB2 database.
For each application except for the Lifecycle Query Engine (LQE), there is a separate teamserver.properties file that you must open and modify. These files are located in their own directories (jts, ccm, rm, qm, dcc, relm, and gc) in the JazzInstallDir/server/conf directory. Open each teamserver.properties file, and specify the database and connection details. For the LQE application, go to the JazzInstallDir/server/conf/lqe/template directory. Copy dbconnection.properties to the /lqe directory, open the file and specify the database and connection details. The default connection specification connects to a DB2 database that connects to localhost on port 50000. The database is called JAZZ, and both the user name and password are db2admin.
Restriction: You cannot manually configure a database connection for the Link Index Provider (LDX) application.

The following example is for Jazz Team Server teamserver.properties file. Follow the steps for other installed applications. Substitute JAZZ with your database name, and the server address with your fully qualified host name.
1. Comment out the following lines under Derby Configuration by placing a number sign (#) before each line. The example is for Jazz Team Server teamserver.properties file:
```
# com.ibm.team.repository.db.vendor = DERBY
# com.ibm.team.repository.db.jdbc.location=conf/jts/derby/repositoryDB
```
```
# com.ibm.team.datawarehouse.db.vendor=DERBY
# com.ibm.team.datawarehouse.db.jdbc.location=conf/jts/derby/warehouseDB
# com.ibm.team.datawarehouse.db.net.port=1527
```
2. Uncomment the following lines under DB2 Configuration by removing the number sign (#) beside each line:
```
com.ibm.team.repository.db.vendor = DB2
com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
com.ibm.team.repository.db.jdbc.password=db2admin
```
```
com.ibm.team.datawarehouse.db.vendor = DB2
com.ibm.team.datawarehouse.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
com.ibm.team.datawarehouse.db.jdbc.password=db2admin
com.ibm.team.datawarehouse.db.base.folder = /jazzdw
com.ibm.team.datawarehouse.report.user = RPTUSER
```
3. Edit the following values in thecom.ibm.team.repository.db.jdbc.location and com.ibm.team.datawarehouse.db.jdbc.location lines:
  - //localhost:50000 type the fully qualified host name of the database server.
  - JAZZ Type the database name.
  - db2admin Type the user name
  Note: The DB2 user must have permissions to create tables, table spaces, and modify the database configuration. The operating system creates DB2 users.
  
  Note: Do not change the password={password} text in the com.ibm.team.repository.db.jdbc.location and com.ibm.team.datawarehouse.db.jdbc.location properties.
4. Specify the user password in the com.ibm.team.repository.db.jdbc.password and com.ibm.team.datawarehouse.db.jdbc.password properties.
5. Change the data warehouse base folder to a path on your database server. Note that you must manually create this folder. On Windows, if a new path is specified, it must be specified by using double backslashes. For example, com.ibm.team.datawarehouse.db.base.folder = C:\\jazzdw\\tempspace32k.
6. In com.ibm.team.datawarehouse.report.user = RPTUSER, enter the report user for whom the correct permission will be granted. The default entry is RPTUSER.
  Note: If you use the setup wizard, correct permission will be granted to the report user. If you want to manually grant permissions, this user must be able to do selects on the database to view a report.
7. If necessary, change the com.ibm.team.repository.db.db2.content.tablespace.location property to a path on your database server, where the main table space can be created.
  Note: If this value is not changed from the default of content_tablespace, the table space is created under the database storage location. On Windows, if a new path is specified, it must be specified by using double backslashes, for example, com.ibm.team.repository.db.db2.content.tablespace.location=c:\\db2\\jts\\content_tablespace.
8. Change the value of the com.ibm.team.fulltext.indexLocation=conf/jts/indices/workitemindex property to the full path location of the full text index. For example, type com.ibm.team.fulltext.indexLocation=c:/Progra~1/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex.
9. Change the value of the com.ibm.team.jfs.index.root.directory=indices property to the full path location of Jazz Foundation Service (JFS) index root directory. For example, type com.ibm.team.jfs.index.root.directory=c:/Progra~1/IBM/JazzTeamServer/server/conf/jts/indices.
10. Optional: To store index data in a separate tablespace instead of the database tables, add the following property and assign an existing tablespace such as clm_indexes as its value: com.ibm.team.repository.db.db2.index.tablespace.name=clm_indexes
11. Optional: To store large objects in a separate tablespace instead of the database tables, add the following property and assign an existing tablespace such as clm_lobs as its value: com.ibm.team.repository.db.db2.lob.tablespace.name=clm_lobs
After each database is created, run a repository tools command to create database tables.
Important: Run the createTables command only if this is a new installation.

Note: When you run the repotools command, the teamserver.properties file will be updated and the original file with the original content will be saved in the same directory. You might also see a warning that the Public URI has not been set. You can ignore this warning at this time because the Public URI will be set when Running the setup by using Custom setup in the setup wizard.
1. For the Jazz™ Team Server, go to the JTSInstallDir/server directory and run these commands:
```
repotools-jts -createTables
```
```
repotools-jts -createWarehouse 
```
2. For the Change and Configuration Management application, go to the CCMInstallDir/server directory and run these commands:
```
repotools-ccm -createTables 
```
3. For the Rational Engineering Lifecycle Manager application, go to the RELMInstallDir/server directory and run these commands:
```
repotools-relm -createTables 
```
4. For the Quality Management application , go to the QMInstallDir/server directory and run these commands:
```
repotools-qm -createTables 
```
5. For the Requirements Management application , go to the RMInstallDir/server directory and run these commands:
```
repotools-rm -createTables 
```
6. For the Data Collection Component application , go to the DCCInstallDir/server directory and run these commands:
```
repotools-dcc -createTables 
```
7. For the Global Configuration Management application , go to the GCInstallDir/server directory and run these commands:
```
repotools-gc -createTables 
```
8. For CLM Server Monitoring, go to the CSMInstallDir/server directory and run these commands:
```
repotools-csm -createTables 
```
Note: The tables for the Lifecycle Query Engine application database will be created automatically when you first run the application.

video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog