Manually configuring an SQL Server database

Edit online

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 SQL Server database connection and run the -createTables command to create database tables.

Procedure

To create a database, see Setting up an SQL Server 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, vvc, rm, qm, dcc, and gc) in the JazzInstallDir/server/conf directory. Open each teamserver.properties file, and specify the database and connection details. For the Lifecycle Query Engine 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.
Note: You cannot manually configure a database connection for the Link Index Provider (LDX) application.

Note: 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 SQL Server Configuration by removing the number sign (#) before each line:
```
com.ibm.team.repository.db.vendor = SQLSERVER
com.ibm.team.repository.db.jdbc.location=//localhost:1433;databaseName=jazz;user=jazzDBuser;password={password}
com.ibm.team.repository.db.jdbc.password=jazzDBpswd
```
```
com.ibm.team.datawarehouse.db.vendor = SQLSERVER
com.ibm.team.datawarehouse.db.jdbc.location=//localhost:1433;databaseName=jazz;user=jazzDBuser;password={password}
com.ibm.team.datawarehouse.db.jdbc.password=jazzDBpswd
com.ibm.team.datawarehouse.db.base.folder = /jazzdw
com.ibm.team.datawarehouse.report.user = RPTUSER
```
3. Edit the following values in the com.ibm.team.repository.db.jdbc.location and com.ibm.team.datawarehouse.db.jdbc.location properties:
  - //localhost:1433: Type the fully qualified host name of the database server.
    Note: You must manually set the static port to 1433 by using the SQL Server Configuration tool.
  - JAZZ: Type the database name.
  - jazzDBuser: Type the user name
  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.
  
  Note: The password you use for the JDBC connection cannot contain the open curly bracket ({) and semicolon (;) characters.
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. On the com.ibm.team.datawarehouse.report.user = RPTUSERline, enter the report user for whom the proper permission will be granted. The default is RPTUSER.
  Note: If you use the setup wizard, proper 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. Change the value of the com.ibm.team.fulltext.indexLocation=conf/jts/indices/workitemindex line to the full path location of the full text index. For example, enter com.ibm.team.fulltext.indexLocation=c:/Progra~1/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex.
8. Change the value of the com.ibm.team.jfs.index.root.directory=indices line to the full path location of Jazz Foundation Service index root directory. For example, enter com.ibm.team.jfs.index.root.directory=c:/Progra~1/IBM/JazzTeamServer/server/conf/jts/indices.
After each database is created, you must 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 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 IBM Engineering Lifecycle Optimization - Engineering Insights, go to the ENIInstallDir/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 
```
Note: The tables for the Lifecycle Query Engine application database will be created automatically when you first run the application.