Manually configuring an Oracle 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 Oracle database connection and run the -createTables command to create database tables.

Procedure

To create a database, see Setting up an Oracle 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, relm, 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.

The following example is for Jazz Team Server teamserver.properties file. Follow the steps for other installed applications.
1. Comment out the following lines under Derby Configuration by placing a number sign (#) before each line.
```
# 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 Oracle Configuration by removing the number sign (#) beside each line:
  Note: There are 2 lines for database location provided for each of the repository and data warehouse databases. One for local systems and one for database servers on remote systems. Only uncomment a line that applies to your environment. The examples here are for a remote server with 2 forward slashes before the server URL, @//oracleserver.example.com:1521/ORCL.
```
com.ibm.team.repository.db.vendor = ORACLE
com.ibm.team.repository.db.jdbc.location=thin:jtsDBuser/{password}@//oracleserver.example.com:1521/ORCL
com.ibm.team.repository.db.jdbc.password=jtsDBpswd
```
```
com.ibm.team.datawarehouse.db.vendor = ORACLE
com.ibm.team.datawarehouse.db.jdbc.location=thin:jazzDBuser/{password}@//oracleserver.example.com:1521/ORCL
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 lines:
  - //oracleserver.example.com:1521: Type the fully qualified host name of the database server.
  - jtsDBuser: Type the database user.
  - jazzDBuser: Type the data warehouse database user. Must be a DBA.
  - ORCL: Type the Oracle service name. When connecting to an Oracle DB, ensure that the ORCL service name exists on the server computer.
  Remember: Oracle location URLs can take several forms. The examples here work under most circumstances. Consult the Oracle JDBC documentation for more details.
  
  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. On the com.ibm.team.datawarehouse.report.user = RPTUSER line, enter the report user for whom the correct permission will be granted. The default is RPTUSER.
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, type 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, type com.ibm.team.jfs.index.root.directory=c:/Progra~1/IBM/JazzTeamServer/server/conf/jts/indices.
9. 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.oracle.index.tablespace.name=clm_indexes
10. 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.oracle.lob.tablespace.name=clm_lobs
After the 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: The user who runs the -createWarehouse command must have DBA permissions. For more information about creating and using data warehouse, see Completing the 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. To create the database tables for Jazz Team Server and data warehouse, 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 this command:
```
repotools-ccm -createTables
```
3. For the Rational Engineering Lifecycle Manager application, go to the RELMInstallDir/server directory and run this command:
```
repotools-relm -createTables
```
4. For the Quality Management application, go to the QMInstallDir/server directory and run this command:
```
repotools-qm -createTables 
```
5. For the Requirements Management application, go to the RMInstallDir/server directory and run this command:
```
repotools-rm -createTables 
```
6. For the Data Collection Component application, go to the DCCInstallDir/server directory and run this command:
```
repotools-dcc -createTables 
```
7. For the Global Configuration Management application, go to the GCInstallDir/server directory and run this command:
```
repotools-gc -createTables 
```
8. For CLM Server Monitoring, go to the CSMInstallDir/server directory and run this command:
```
repotools-csm -createTables 
```
Note: The tables for the Lifecycle Query Engine tablespace 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