Configuring databases by using the server setup application

The server setup application is a browser-based web application for IBM® WebSphere® Application Server that helps you deploy the other Rational® Asset Manager applications and configure the database, security, performance, and repository settings. You can use the server setup application to later modify these settings instead of using the Administration pages within Rational Asset Manager web client.

Before you begin

Procedure

In Section 2, Part 1, either create new databases or connect to existing databases:
1. Select whether to create new databases or use existing databases.
  - To create and populate new Assets and Lifecycles databases, select You need to Create all three databases and then click Next. Go to step 12.b.
  - To create new Lifecycle databases and use an existing Assets database, select You need to Create both RTC's CCM and JTS databases and then click Next. Go to step 12.b.v.
  - To use an existing Assets and Lifecycles databases (for example, if you are upgrading from a previous version of Rational Asset Manager), select You have already created all three databases and want to modify the settings and then click Next. Go to step 13.
2. Create a database.
  - For DB2® running on supported operating systems except for z/OS®, you can use a Java™ applet to create the database. For DB2 running on z/OS, you must create the database manually.
    - To use the Java applet:
      1. After the applet loads, it searches for an instance of DB2 on the local computer. The browser that you run the server setup application on must be on the computer on which DB2 is installed. If the applet finds an instance of DB2, the location of the DB2 installation and its version are displayed. If the applet does not find an instance, you are prompted to enter the location.
      2. To use a different installation of DB2, click Change install location.
      3. Type the User ID and Password for the DB2 administrator. DB2 administrators are managed by the operating system.
      4. After you select the appropriate location, in the Create a database for Assets field, type a name for the asset database (for example, RAMDB).
      5. If you are installing a new Rational Team Concert, in the Create a database for RTC'S CCM field, type a name for the Change and Configuration Management (CCM) lifecycle management database (for example, CCMDB). In the Create a database for RTC'S JTS field, type a name for the Jazz™ Team Server (JTS) lifecycle management database (for example, JTSDB). If you are using an existing Rational Team Concert, you do not need to create a new database.
      6. Click Create Database(s). This will also populate the tables for the database for assets.
    - To manually create and configure the DB2 database, click View instructions on how to manually create the DB2 DATABASE(s) and follow the displayed instructions.
  - For Oracle or SQL Server, follow the instructions to create and populate the database.
  The instructions displayed in the server setup application are identical to those at Creating the database for assets.
In Section 2, Part 2, specify the database connection properties:
1. In the Database server text field, type the host name or IP address of the database server; for example, servername.example.com. (Do not use localhost).
2. In the Port field, type the port number. For example, the default value for DB2 is 50000.
3. Type the user ID and password of a user with administration authority for the database application.
4. Select to either provide the location of the archive file or files required by the database on the server, or upload them to the server. Your database vendor can provide these files.
  - To enter the location of the archive files on the server, type the full path to the folder that contains them; for example, C:\Program Files\IBM\SQLLIB\java.
  - To upload the files to the server, select that option and browse to the file or files on the local computer. By default, these are available in Rational_Asset_Manager_install_root\ram\was\universalDriver\lib on the local computer. When uploaded to the server, they will be placed in WebSphere_install_directory\profiles\profile_name\config\cells\cell_name\ram_jdbc
    Note: Replace back slashes ("\") in the directory paths with forward slashes ("/").
    
    Note: For Oracle, you can download the appropriate .jar files from Oracle. For Microsoft SQL Server, you can download the appropriate .jar file from Microsoft.
    
    Important: If you must run WebSphere Application Server or Apache Tomcat as a non-root user, then you must set the appropriate permission on the database Java archive files that you upload. Refer to the instructions in Enabling database connectivity for non-root users (Linux and AIX).
5. In the Database name for RAM field, type the name of the main Rational Asset Manager database; for example, RAMDB. Then, type the User ID and Password for a database administrator.
6. In the Database name for RTC's CCM field, type the name of the CCM Lifecycle management database; for example, CCMDB. Then, type the User ID and Password for a database administrator.
7. In the Database name for RTC's JTS field, type the name of the JTS Lifecycle management database; for example, JTSDB. Then, type the User ID and Password for a database administrator.
8. Click Test Connection. The server setup application reports whether the server could connect to the databases.
9. If the connection test was successful, click Next.
In Section 2, part 3, populate the databases :
1. For Step 5: Populate Rational Asset Manager Core Database, click Populate the database if the database configured with errors.
2. Click OK to continue configuring the database. This process can take a few minutes.
3. For Step 6: Populate Rational Asset Manager Lifecycle Databases, click Populate the databases if the databases configured with errors.
4. Click OK to continue configuring the databases. This process can take a few minutes.
5. After the databases are configured, click Next.
In Section 2, Part 4, if you use DB2, you can configure database settings to optimize the performance of Rational Asset Manager. If you are using Oracle or SQL, you cannot configure database settings here.
1. If you are using DB2, configure your database settings. Suggested values and current values for the following parameters are listed. To change all parameters to the recommended values, select Use recommended values. Changes to database settings take effect when you restart the database server.
  - LOCKLIST: to specify the amount of storage that is allocated to the lock list, type a number between 4 and 60000, inclusive.
  - LOCKTIMEOUT: To specify the number of seconds that an application waits to obtain a lock, type a number between 1 and 30000. Setting this property helps avoid global deadlocks for applications. If the value is -1, lock timeout detection is turned off.
  - LOGFILSIZ: To specify the size of each primary and secondary log file, type a number. The size of these log files limits the number of log records that can be written to them before they become full and a new log file is required. If the database has a large number of update, delete, or insert transactions running, which will fill the log file quickly, increase the value of LOGFILSIZ.
    Note: Changing the LOGFILSIZ parameter from the default is necessary only when there are a large number of assets in the repository (for example, tens or hundreds of thousands).
  - MAXAPPLS: type a number that is greater than the number of expected concurrent connections.
  - MAXLOCKS: To specify the percentage of the lock list that is reached when the database manager escalates, from row to table, the locks that the application holds, type a number between 1 and 100. Although the escalation process does not take much time, locking entire tables versus individual rows decreases concurrency, and potentially decreases overall database performance for subsequent attempts to access the affected tables.
2. Click Next.
In Section 2, Summary, the server setup application will prompt you to restart the server. If you plan to continue through other sections of the server setup application, you can wait to restart the server until you have finished those sections.
- If you are finished specifying your configuration settings (for example, if you are using the server setup application to make changes to an existing setup), restart the server now. To restart the server, click Tools > Restart the server.
- To continue without restarting the server, click Next.

What to do next

Feedback