Setting up a DB2 database for Rational Engineering Lifecycle Manager and the Lifecycle Query Engine

Rational® Engineering Lifecycle Manager supports IBM® DB2® Enterprise Server Edition. You will need to create a database for Rational Engineering Lifecycle Manager, Jazz™ Team Server, Rational Engineering Lifecycle Manager, and the Configuration Management application.

Before you begin

This procedure requires that the following prerequisites are met. Consult your DB2 documentation or a DB2 database administrator (DBA) for help.
Important: If you install Jazz Team Server with Rational Engineering Lifecycle Manager or the Lifecycle Query Engine on either the same computer or distributed platforms, a separate database and a DB user who is associated with that database must be created for each application.

Run the following commands in the DB2 Command Window. You can open the Command window from the application Start menu under the DB2 Command Line Tools menu. To connect to a remote server, you can use Telnet or SSH. Ensure that you are connected as the db2inst1 user by running the su db2inst1 command.

Procedure

  1. Open a DB2 command window and create the database.
    For Rational Engineering Lifecycle Manager Jazz Team Server, create a database called RELMJTS with 8K pages and the UTF-8 code set.
    db2 create database RELMJTS using codeset UTF-8 territory en PAGESIZE 8192
    For the Rational Engineering Lifecycle Manager application, create a database called RELM with 8K pages and the UTF-8 code set.
    db2 create database RELM using codeset UTF-8 territory en PAGESIZE 8192
    For the Configuration Management application, create a database called VVC with 8K pages and the UTF-8 code set.
    db2 create database VVC using codeset UTF-8 territory en PAGESIZE 8192
    Tip: If the database is not running, the command db2start starts DB2.
    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,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM on database to user <user name>
    db2 disconnect <database name>
  2. To configure your databases connections and create database tables using IBM WebSphere® Application Server, see Setting up WebSphere Application Server for Rational Engineering Lifecycle Manager
    Note: If you create all databases (relm, relmjts, vvc) on the same database server, verify that the Max number of concurrently active databases is set to a number greater than 3. If this value is lower than the number of active databases, you will get the SQL Code 1041 error.
    1. To open the database manager configuration, from the DB2 command window run the following command:
      db2 get dbm cfg
    2. Look for the Max number of concurrently active databases line. If this number is lower than the installed databases, increase the number to 8 by issuing the following command:
      db2 update dbm cfg using numdb 8
    3. Stop and start the database manager for these changes to take effect by issuing these commands:
      db2stop
      db2start

Manually configuring a DB2 database

About this task

Running the setup wizard is the recommended method to configure the database connections and create the database tables. To run the setup wizard, follow the instructions in: Running the Jazz Team Server setup wizard for Rational Engineering Lifecycle Manager applications

If you prefer to do this procedure manually, use this topic to edit the teamserver.properties file to setup an IBM DB2 database connection and run the -createTables command to create database tables.

Procedure

  1. For each application, there is a separate teamserver.properties file that you must open and modify. These files are located in their own directories (relmjts, relm, and vvc) in the JazzInstallDir/server/conf directory. Open each teamserver.properties 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.
    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:
      # com.ibm.team.repository.db.vendor = DERBY
      # com.ibm.team.repository.db.jdbc.location=conf/jts/derby/repositoryDB
    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
    3. Edit the following values in thecom.ibm.team.repository.db.jdbc.location line:
      • //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 properties.
    5. 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.
    6. 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.
    7. 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.
  2. 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 you run the setup wizard.
    1. For the Jazz Team Server, go to the JazzInstallDir/server directory and run these commands:
      repotools-relmjts -createTables
    2. For the Rational Engineering Lifecycle Manager application, go to the JazzInstallDir/server directory and run these commands:
      repotools-relm -createTables 
    3. For the Configuration Management application , go to the JazzInstallDir/server directory and run these commands:
      repotools-vvc -createTables 

Feedback