Creating databases for asset lifecycles in Oracle

These are the instructions for creating databases for lifecycle management in Oracle for IBM® Rational® Asset Manager. These databases are used by the included version of IBM Rational Team Concert™.

Before you begin

If you are using an existing Rational Team Concert server, you can skip this task because Rational Team Concert already have the databases.

Oracle must already be installed and running.

You must create the databases for asset lifecycles on the same host as the database for assets.

Procedure

To set up the Oracle databases for asset lifecycles:

  1. Using the Oracle Database Configuration Assistant, follow the steps in the wizard to create a new database.
    1. The database must be on the same host as the database that you created for assets.
    2. Use global database name ccmdb, and a system identifier (SID) ccmdb. The global database name and the system identifier must be the same.
    3. On the Character Sets page, select Use Unicode (AL32UTF8).
    4. Also on the Character Sets page, for National Character Set, select UTF8 - Unicode 3.0 UTF-8.
    5. Complete the other pages in the wizard, accepting the default values.
  2. Create a tablespace. The tablespace must have the following properties:
    • A name other than oracle_tbs;
    • A location in a different directory than the oracle_tbs tablespace;
    • A size of at least 1 GB; for larger installations, you might need more space.
    The following command for a Windows computer shows a sample create statement:
    CREATE BIGFILE TABLESPACE jazz_tbs DATAFILE 'D:\jazz_tbs\jazz_tbs.dbf' SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    Note: In the above command, the directory D:\jazz_tbs\ must exist. The use of BIGFILE is not required, but recommended.
  3. Create a database user:
    1. Open Database Control.
    2. Navigate to the Users page. (In Oracle 10.2(g), click Administration, then Users; in Oracle 11(g), click Server, then in the Security section click Users.)
    3. Create a user that meets the following qualifications:
      • You can use any valid user name. Unlike the database for assets, a specific user name is not required.
      • The user has the RESOURCE and CONNECT roles.
      • The user's quota setting is unlimited.
      • The default tablespace for the user is the tablespace that you created in step 2.
      • The user must have the following permissions:
        • CREATE PROCEDURE
        • CREATE SESSION
        • CREATE TABLE
        • CREATE VIEW
      Tip: Oracle provides a default user named "Scott" that has many of the appropriate permissions. You can use this default user as the basis for your new user account.
  4. Repeat the above steps to create a database named jtsdb.

What to do next

For WebSphere: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