Creating and populating database tables for assets in DB2 with batch files

Use batch files and database scripts to create and populate tables in IBM® DB2® for IBM Rational® Asset Manager.

Before you begin

If you are using IBM WebSphere® Application Server and will be using the server setup application on a supported operating system other than z/OS®, you can skip this task because the server setup application can create and configure the databases for you.

If you prefer to create the database and tables manually, see Creating database tables for assets in DB2 manually.

You can create the database and tables automatically by running batch files. DB2 must already be installed and running. Ensure that you know the location of the SQL scripts that are included in the installation media. The location is install_location\ram\DatabaseScripts\DB2 if you installed by using Installation Manager. You must also know the installation directory for DB2 (typically C:\Program Files\IBM\SQLLIB for Windows and opt/IBM/DB2/V10.1 for Linux, AIX®, or Linux for zSeries.

On Linux, AIX, or Linux for zSeries, log in as a user with sufficient privileges to create the database. For example, log in as the DB2 instance owner. The default user is db2inst1.

You will use the following scripts:

dbcreate_populate.bat
dbcreate_populate.sh
dbcreate_populate_zLinux.sh
dbcreate.sql
RAMSCHEMA_DB2.sql
bootStrap_DB2.sql

Procedure

If you are installing from the CD, then copy the SQL scripts to your local file system.
Check that you have write permission for the directory containing the SQL scripts.
In a command line, change to the directory containing the SQL scripts for DB2 (path to installation media\ db_scripts\DB).
Run the following batch file:
- dbcreate_populate.bat
- dbcreate_populate.sh
- dbcreate_populate_zlinux.sh
When prompted, enter the name of the database or press the Enter key to accept the default database name (RAMDB).
At the next prompt, enter the installation directory path for DB2, or press the Enter key to accept the default value (C:\Program Files\IBM\SQLLIB for Windows, and /opt/IBM/DB2/V10.1 for Linux, AIX, or Linux for zSeries.
The batch file runs. The script performs the following actions:
- A database with the name that you entered is created.
- Tablespace is configured for the database.
- Tables and schema for RAM are created in the database.
Note: When you run the batch file for the first time, you might see a number of SQL0204N error messages that name is an undefined name, and they will be similar to the following example:
```
** CLI error in executing the SQL statement:
(-204): [IBM][CLI Driver][DB2/NT] SQL0204N  "RAMSCHEMA.FORUM" is an undefined name.  SQLSTATE=42704
```
If you are running the batch file for the first time, then you can safely ignore these messages.
Verify that the tables were created. For example, start the DB2 Control Center and browse for the RAMDB database. Verify that the database and tables were created.

What to do next

If you do not already have an existing Rational Team Concert server create the database for lifecycle management. See Creating databases for asset lifecycles in DB2.
If you already have Rational Team Concert:
If you are using WebSphere Application Server:

If you have not deployed the server setup application, deploy it to your server or cluster. To do so, see deploying to a server or deploying to a cluster.
Restriction: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND).

If you are installing to a WebSphere Application Server cluster and you need to install Rational Team Concert™, you will also have to create a single application server instance for Rational Team Concert.

Then, use the server setup application to configure WebSphere Application Server to connect to your databases. If you have deployed the server setup application to your server or cluster, see Deploying and configuring application files by using the server setup application.

If you are using Apache Tomcat:

Configure Apache Tomcat and deploy the Rational Asset Manager application files. See Deploying the Rational Asset Manager server applications on Tomcat 6 or 7.

Feedback