IBM Rational ProjectConsole

Installation and Upgrade Guide

Tables

1. Servers used with Rational ProjectConsole
2. Software requirements for Rational ProjectConsole features
3. Supported vendor databases for Windows platforms
4. Supported databases running on Linux or a UNIX system
5. Preserved user data
6. Requesting and installing IBM license keys
7. Installation checklist
8. Rational ProjectConsole Web client installation checklist
9. Case-sensitivity properties of vendor databases
10. Upgrade paths to version 7.0.x
11. Databases compatible with supported versions of Rational ProjectConsole
12. DB2 connection parameters for version 2003.06.15
13. DB2 connection parameters for version 7.0.x

About this book

This book provides requirements and instructions for installing, configuring, and licensing IBM^(R) Rational^(R) ProjectConsole^(TM).

Who should read this book

This book is intended for administrators of Rational ProjectConsole or users who want to install Rational ProjectConsole version 7.0.2.

Contacting IBM Customer Support for Rational software products

If you have questions about installing, using, or maintaining this product, contact IBM Customer Support as follows:

The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support Home page for Rational products can be found at http://www.ibm.com/software/rational/support/.

Voice Support is available to all current contract holders by dialing a telephone number in your country (where available). For specific country phone numbers, go to http://www.ibm.com/planetwide/.

You can submit a support request electronically. Click the Report Problems tab at http://www.ibm.com/software/rational/support/

Downloading the IBM Support Assistant

The IBM Support Assistant (ISA) is a locally installed serviceability workbench that makes it both easier and simpler to resolve software product problems. ISA is a free, stand-alone application that you download from IBM and install on any number of machines. It runs on AIX, (RedHat Enterprise Linux AS), HP-UX, Solaris, and Windows platforms.

ISA includes these features:

• Federated search
• Data collection
• Problem submission
• Education roadmaps

For more information about ISA, including instructions for downloading and installing ISA and product plug-ins, go to the ISA Software Support page.

IBM Support Assistant: http://www.ibm.com/software/support/isa/

Planning the Installation

This chapter provides a high-level guide to planning the installation of IBM Rational ProjectConsole. Both administrators and users of the product should read this chapter before beginning the installation.

Beginning with release 7.0.2, Rational ProjectConsole uses the IBM Installation Manager for installation. IBM Installation Manager is a program for installing, updating, and modifying packages. The program helps you manage the IBM applications, or packages, that it installs on your computer. Installation Manager does more than install packages - it helps you keep track of what you have installed, determine what is available for you to install, and organize installation directories. For more information, see the IBM Installation Manager Information Center.

For the most current information about features and known issues, see the IBM Rational ProjectConsole Release Notes.

Upgrading from a previous version

If you are upgrading from a previous version of the product, review the upgrade information before you install the current version.

If you are upgrading from a previous version of Rational ProjectConsole that was installed with the MSI installer, you must uninstall your product before beginning this installation. Beginning with version 7.0.2, installation is done with IBM Installation Manager.

For upgrade information, see Upgrading Rational ProjectConsole.

Installing the Rational ProjectConsole integration with IBM Rational Portfolio Manager

If you are installing Rational ProjectConsole integration with Rational Portfolio Manager as part of the metrics enablement feature for Rational Portfolio Manager, you must be sure to select the integration option from the Custom Setup menu for the Rational ProjectConsole installation.

Installing the integration installs a modified version of the Rational ProjectConsole Designer, which can be accessed from the Start menu. This version of the Designer authenticates against Rational Portfolio Manager and is not intended for use with a stand-alone version of Rational ProjectConsole.

For information about setting up the integration with Rational Portfolio Manager, see the IBM Rational Portfolio Manager IBM Rational ProjectConsole Integration Guide from the Rational Portfolio Manager documentation set.

Planning your server and client environment

To help you plan your environment, determine which computers will be servers. Servers need to be highly available and might need extra memory and disk space. Table 1 describes the types of servers you might need.

Installing this product with other IBM Rational products

In this release, the products formerly offered as part of IBM Rational Suite^(R) can only be installed individually. You can no longer install a collection of Rational products as a single Rational Suite. The products are installed separately to support patching and upgrading.

If you are installing Rational products for the first time, follow the instructions in the installation guide for each product that you install.

If you have previously installed a Rational product that was a part of Rational Suite, review the upgrade section of this guide carefully. Version 7.0.2 is a major release that includes changes to installation and other operating processes, dependencies between products, and interoperability with product integrations. In some cases, tasks must be performed in a specific sequence, for example, upgrading server components before upgrading clients.

As of version 7.0.2, all Rational products installed on a computer must be the same version. Before installing Rational products with Installation Manager, you must use the rationaluninstalltool.exe tool to uninstall previous versions of Rational products that were installed with the MSI based installation technology. For more information about uninstalling Rational products, see Uninstalling Rational products in Upgrading Rational ProjectConsole.

Change to search order for license keys

In releases prior to 7.0.x, when a product from Rational Suite was installed, the Rational License Key Administrator (LKAD) application tried to find a license key that corresponded to Rational Suite. If such a key was not available, LKAD searched for a key that corresponded to the product itself.

In version 7.0.x, LKAD looks for the product-specific license key first. You can still use the License Usage Mapper in LKAD to change this search order or have the application not search for a Rational Suite key. For more information about licensing, see the IBM Rational License Management Guide.

System requirements

This section presents hardware and software system requirements for installation in addition to a list of supported vendor databases and server platforms.

Hardware requirements

The following list provides information about the hardware requirements for server installations of Rational ProjectConsole.

• 500 MHz or higher
• 512 MB RAM; more memory generally improves performance; required memory depends on the number of concurrent users, amount of data being requested, and the size of the database.
• The recommended swap space is twice the physical memory.
• The Rational ProjectConsole repository requires more than 1 GB of disk space.

Software requirements

These features include:

• Rational ProjectConsole server
• Rational ProjectConsole collection agents and report servers
• Template Builder
• Rational Web Platform

Supported vendor databases and server platforms

Supported vendor databases and server platforms for Windows

Table 3 lists the supported vendor databases for each server platform.

Supported vendor database platforms for Linux and UNIX

You can use vendor databases running on Linux^(R) and the UNIX system with Rational ProjectConsole. Table 4 lists supported vendor databases for these platforms.

Installing Rational ProjectConsole

This chapter describes the procedure for installing Rational ProjectConsole components.

Uninstalling Rational products

The following products, which were installed with MSI based install technology, must be uninstalled:

• Rational ClearQuest
• Rational ClearCase
• Rational RequisitePro
• Rational Project-Console
• Rational Test Manager
• Rational Robot
• Rational SoDA

The rationaluninstalltool.exe tool has two uninstall scenarios; a clean uninstallation and a user data preserved uninstallation.

The clean uninstallation completely removes the Rational installation directory in addition to Rational Software registry keys under both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER.

The user data preserved uninstallation does not remove files that are used to customize the environment. Use this method if you want to save customizations from your current deployment for your Installation Manager deployment. The following table identifies the files that are preserved for each of the products by this uninstallation method.

The rationaluninstalltool.exe tool removes all Rational products listed above at the same time. It does not need to be rerun for each product.

To remove Rational products with the rationaluninstalltool.exe tool:

1. Download the uninstallation program rationaluninstalltool.exe and save it to the hard disk.
2. Run the Windows command prompt (Click Start -> Run, enter cmd, and press Enter).
3. Navigate to the directory where the uninstallation program is saved.
4. Run the rationaluninstalltool.exe command. See the command reference below.

Synopsis

rationaluninstalltool.exe <log file name> [ -c ]

Description

Use the rationaluninstalltool.exe command with the following subcommands:

• <log file name> Specify the name and location of the log file in which you want to store the logging information.
• [ -c ] Requests that everything is removed. The clean uninstallation completely removes the Rational installation directory and the Rational Software registry keys under both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER.
  Note:
  If you want to run a user-data preserved uninstallation, do not invoke the -c option. The rationaluninstalltool.exe command automatically preserves the data previously specified when this option is not used.

Configuring deployment

Configuring deployment of your software product requires that you understand the types of deployment methods available for your product. You can then select the appropriate deployment type for your users and you can configure your software for the selected deployment method.

If you are installing a Rational ProjectConsole server, read Configuring the IBM Rational ProjectConsole server before proceeding.

If you are installing a Rational ProjectConsole client, read Setting up the IBM Rational ProjectConsole client before proceeding.

Licensing your software

In all cases, you need a license key to start the product. Your license administrator can tell you which license key to use and where to obtain it.

The License Key Administrator (LKAD) is a tool that imports license keys to your license server. LKAD provides a wizard to simplify the process.

The Setup wizard installs LKAD with each IBM product. If the product is not already licensed, you can start the LKAD wizard when the installation process is finished. You can also start LKAD by clicking StartPrograms  > IBM Rational  > Rational License Key Administrator. The LKAD main window and wizard page open simultaneously. For more information, see the LKAD Help.

If you do not see the License Key Administrator (LKAD) start at the end of the installation, your product is already licensed.

Follow the instructions in Table 6 to license your product.

Licensing Web clients

The Web server (Rational ClearQuest Web Application server or Rational Web Platform) requests a license key from the Rational License Server for each Web client. You do not have to install a license key on your desktop to use the Web client.

Licensing products on Windows Terminal Servers

To use Rational products that support hosted development on Windows Terminal Servers, you must have floating licenses.

Configuring the IBM Rational ProjectConsole server

This chapter explains how to install and set up Rational ProjectConsole software on the Web server, report server, and collection agent computers. This information is intended for administrators who are responsible for setting up for use by the entire development team.

For the latest Rational ProjectConsole and Template Builder installation information, see the IBM Rational ProjectConsole Release Notes.

Use the checklist in Table 7 to help you set up and perform the required postinstallation tasks.

Setting up the Rational ProjectConsole server

When you install the Rational ProjectConsole Web server components, the Rational ProjectConsole data warehouse, collection agent and report server, Template Builder, and Rational Web Platform (RWP) are also installed.

To set up the server:

1. Install the Web server components.
2. To use the server to collect data, configure the report server and collection agent software on the server computer. Setting up additional computers as report servers and collection agents is optional.

   A collection agent gives the server access to project data from products, Microsoft Project, and delimited text files. It collects artifacts from these data repositories and stores the artifacts in a data warehouse.

Setting up additional report servers and collection agents

To set up and run an additional computer as a report server and collection agent:

1. Install the report server and data collection agent software. You can install these features as a stand-alone product by clearing all other features in the Setup wizard.
2. Configure the collection agent software. Configuring the Rational ProjectConsole services.

Setting up the Rational ProjectConsole data warehouse

You must set up a Rational ProjectConsole data warehouse in preparation for creating a Rational ProjectConsole data repository. The data repository is used to store metadata about the data warehouse and the security database. The Rational ProjectConsole security database is used to store the navigation tree structure information and user and group authentication and authorization information.

The security database is created from IBM Cloudscape^(TM) version 10.1.2 software. Cloudscape is installed with the Rational ProjectConsole server components and requires no additional configuration or setup. It contains information about navigation tree structure and authentication information for all users and groups for Rational ProjectConsole.

The database requirements and configuration information for the Rational ProjectConsole data warehouse are described in Configuring vendor databases.

Preparing the data warehouse

Create the repository only after you install the Rational ProjectConsole server and create your data warehouse. The data warehouse is the database server in which data collected from software development tools and other Rational products is stored. You manage the data warehouse with the Rational ProjectConsole Maintenance Tool.

If you want to start using Rational ProjectConsole in a production environment, create a new data warehouse by using SQL Server, Oracle, or IBM DB2. Microsoft Access (runtime files only) is provided for demonstration purposes. Microsoft Access is not suitable for use as an enterprise data warehouse; use of quickly exceeds the capabilities of Microsoft Access. SQL Server, Oracle, and DB2 are more robust and better suited for an enterprise-scale data warehouse.

Creating a secure connection

General instructions for configuring secure access for Rational ProjectConsole are in Appendix A on the Rational Web Platform. In addition to the procedures described there, you must import the key that is created in the IBM keystore into the Java keystore.

Setting up the IBM Rational ProjectConsole client

This section describes how to set up a Rational ProjectConsole client on your desktop and how to install the Rational ProjectConsole Template Builder. This section is intended for team members who want to access the Rational ProjectConsole Web site from a Web browser to view current project information.

For the most current information about Rational ProjectConsole features and known issues, see the IBM Rational ProjectConsole Release Notes.

Setting up a Rational ProjectConsole Web client and the Template Builder

Use the checklist in Table 8 to help you set up the Rational ProjectConsole Web client and the Rational ProjectConsole Template Builder on your desktop. The procedures are in the sections following the checklist. There are no postinstallation tasks for the Rational ProjectConsole Web client.

Setting the screen area for your monitor

To use the Rational ProjectConsole Web site, set the screen area for your monitor to at least 1024 x 768 pixels. Otherwise, you might have problems accessing key Rational ProjectConsole components.

Enabling cookies

To use the Rational ProjectConsole Web site, enable cookies in your Web browser. For information about how to enable cookies, see the Help in your Web browser.

Logging in to the Rational ProjectConsole Web site

To log in to the Rational ProjectConsole Web site for the first time:

1. Ask your administrator for the Rational ProjectConsole Web server name.
2. Start your Web browser, and then type the following:

   http://server-name/ProjectConsole 

   where server-name is the name of the Rational ProjectConsole server.

3. Press Enter.
4. On the Rational ProjectConsole Logon page, in the Username field, type admin, the default administrator username.
5. In the Password field, type changeit, the default administrator password.
6. Click Logon.

Installing the Java plug-in

The first time you log in to the Rational ProjectConsole Web site and run either the Dashboard or Designer applet, you are prompted to install the required Java plug-in, if it is not already installed on your computer.

To install the Java plug-in, follow the instructions that are displayed on your screen for installing the plug-in.

After you install the Java plug-in, close all browser windows and log in to the Rational ProjectConsole Web site. If you are prompted to install the Java plug-in again the next time you attempt to run either of the Rational ProjectConsole applets, you might need to restart your system.

Installing Rational ProjectConsole Template Builder

You can install Template Builder on any computer on which you want to create or modify Rational ProjectConsole report templates. You can install the Rational ProjectConsole Template Builder on a computer regardless of whether other Rational ProjectConsole components are installed on that computer.

The Rational ProjectConsole Template Builder is an add-in for Microsoft Word. To run Template Builder, a supported version of Microsoft Word must be installed on the Template Builder computer.

All Rational ProjectConsole report templates must reside on the Rational ProjectConsole Web Server. If you install and run the Rational ProjectConsole Template Builder on another machine, you must copy the generated report templates to the proper location on the Rational ProjectConsole Web server.

Configuring vendor databases

Rational Project Console schema and database use is based on the model used by Rational ClearQuest. As such, Rational Project Console schema repositories and user databases are types of databases that are physically managed by a database management system. Depending on your platform, these systems might include Microsoft Access, Microsoft SQL Server, Oracle RDBMS, IBM DB2, or the set of DB2 functionality available as part of IBM DB2 UDB components for Rational

For information about configuring vendor databases for use with Rational ProjectConsole, see the Vendor database topics at the Rational ClearQuest Information Center at IBM Installation Manager Information Center For information about upgrading databases, see Upgrading data warehouse connections

Guidelines for choosing vendor databases are available in Choosing a vendor database and When to use Microsoft Access

Choosing a vendor database

You must consider what platforms support the vendor database you plan to use for your databases.

The following databases are supported:

• IBM DB2
• IBM DB2 UDB Express

  DB2 Express is provided at no cost on a separate CD. If you are planning on deploying a DB2 Express data warehouse, you must install the DB2 Express software on your database server. This software is not installed with .

• Microsoft Access (not recommended for production use)
• Microsoft SQL Server
• Oracle

To choose the vendor database that best meets your needs, follow these general guidelines:

• For initial testing and evaluation, or for small groups (fewer than five users), you can use the IBM DB2 UDB Express database or the Microsoft Access runtime files.
  Note:
  Microsoft Access is not supported for production databases.
• For small- to medium-sized groups (5 to 20 users), you can use a mid-level database, such as DB2 Express.
• For larger groups (over 20 users), large amounts of data, or to achieve better performance, use a database such as DB2, Oracle, or Microsoft SQL Server.

When to use Microsoft Access

Do not use Microsoft Access databases for production use. The runtime files are supplied solely for evaluation purposes. These runtime files are not the full version of Microsoft Access.

If you choose to use Microsoft Access for evaluation purposes, when you first run Rational ProjectConsole and are prompted to create a schema repository, specify the path to the shared directory and provide a file name for the schema repository. The appropriate Microsoft Access databases in the shared directory are then created and initialized.

Database case-sensitivity

Database case-sensitivity settings must be consistent when you are moving a database to a different vendor database.

Table 9 summarizes the case-sensitivity properties of the supported vendor databases.

After installation: Configuring Rational ProjectConsole

This chapter explains how to configure the Rational ProjectConsole software after installation. It describes how to set up Rational ProjectConsole on the Rational ProjectConsole Web server (including report server and collection agent software), the data repository, and, optionally, on separate report server and collection agent computers.

The sections that follow assume that you have completed the following tasks:

• Set up the data warehouse using the procedures in the section.
• Installed the Rational ProjectConsole server, report server, and data collection agent on the server computer.

Viewing Microsoft Access sample data

When the Rational ProjectConsole server components are installed, the Rational Setup wizard creates two Microsoft Access Rational ProjectConsole sample database files that are part of the Rational ProjectConsole repository:

• InstallDir\ProjectConsole\DataRepository\PjC Demo\DataWarehouse.mdb
• InstallDir\ProjectConsole\DataRepository\PjC Demo\SchemaRepository.mdb

After installing the Rational ProjectConsole Web server components, you can log in to the Rational ProjectConsole Web site without rebooting. If you cannot log in to the Rational ProjectConsole Web site, see another section.

You can log in to the Rational ProjectConsole Web site from a Rational ProjectConsole client and start browsing the sample repository data. For information about how to log in to the Rational ProjectConsole Web site from a client, see Logging in to the Rational ProjectConsole Web site.

Setting up users and groups

After you install and set up the Rational ProjectConsole server, log in as a Rational ProjectConsole administrator by typing admin in the User ID field and changeit in the Password field. To ensure Rational ProjectConsole Web site security, set up users (with user IDs and passwords) and groups for your development team immediately after you set up the Rational ProjectConsole server. Change the password on the admin account immediately after you log in to the Rational ProjectConsole site for the first time.

For information about setting up users and groups and managing site security, see the Rational ProjectConsole Help.

Configuring the Rational ProjectConsole services

This section describes how to use the Rational ProjectConsole Maintenance Tool to configure Rational ProjectConsole software on the Rational ProjectConsole server and on any separate computers on which you installed the report server and collection agents.

• For more information about the Web Platform (RWP) and the Rational ProjectConsole Web server components, see Appendix A, Rational Web Platform
• For information about the options available in the Rational ProjectConsole Maintenance Tool, see Rational ProjectConsole Maintenance Tool Help.

Configuring the Rational ProjectConsole server, additional report servers, and collection agents

To configure the Rational ProjectConsole services on the server or on an additional report server and collection agent:

1. Click Start > Programs > IBM Rational ProjectConsole > IBM Rational ProjectConsole Maintenance Tool.
2. Select the Configure the ProjectConsole services check box. Click Next.
3. In the Web server name field, type the name of the Rational ProjectConsole server.
4. In the Web server port field, if the Rational ProjectConsole Web server uses a port other than the default port (80 for HTTP and 443 for HTTPS), clear the default port number and type the correct number.
5. To ensure secure data transactions, next to Web server protocol, click HTTPS.

   After you click HTTPS, the value displayed in the Web server port field changes from 80 to 443. Your Web server must be configured to accept HTTPS connections for Rational ProjectConsole applications to connect by using the HTTPS protocol.

6. If the Rational ProjectConsole server is running behind a firewall, and the name of this server computer is not visible outside the firewall, perform the following steps. Otherwise, skip to Step 7.
   1. In the RMI server name field, type the Rational ProjectConsole server host name or IP address for the RMI server to send in RMI connection reply messages.

      If you install the ProjectConsole Web server behind a firewall, you should set the RMI server name to a hostname or IP address that can be resolved from outside the firewall, and ensure that your firewall software forwards incoming requests to the Rational ProjectConsole Web server machine.

   2. In the RMI server port field, type the port number on the Rational ProjectConsole server that the RMI server should use instead of a dynamic client connection port. If your Rational ProjectConsole Web server is installed behind a firewall, you might need to set the RMI server port and open that port on the firewall.

      These values are set in the server.ini file.

   3. Configure the firewall to route requests on both the static Rational ProjectConsole RMI server port and the dynamic RMI server port to the Rational ProjectConsole server computer.
   4. Configure the firewall to route requests on the HTTP (or HTTPS) listening port to the Rational ProjectConsole server.

      After you complete this procedure, HTTP requests are routed to the Rational Web Platform server components on the Rational ProjectConsole server, and RMI connections to the Dashboard and Designer are correctly routed to the Rational ProjectConsole server.

7. In the Connection retry interval field, type the number of minutes for the report server and collection agents to wait after failing to connect to the Web server before trying to connect again.
8. To control the debug information that the Web server (and any report servers and collection agents) generate and save to the log files, in the Trace level list, select a trace level value:
   • Tracing is disabled: Logged information excludes errors and diagnostic messages.
   • Trace errors only: Logged information includes errors, but excludes messages.
   • Trace errors and warnings: Logged information includes both errors and messages.
   • Trace all messages: Logged information includes all diagnostic messages.
   • Trace all messages (with call stack): Logged information includes all diagnostic messages and a call stack to help trace the sources of errors.
9. In the Log file directory field, leave the default directory path for generated log files (C:\Programs\Rational\ProjectConsole\logs ) or enter a different directory for log files.
10. In the Text template directory field, leave the default value (C:\Programs\Rational\ProjectConsole\templates\Designer ) or enter a different directory for text templates.
11. In the Artifact repository field, use the default setting (C:\Classics\Projects\Webshop ) or enter a different directory for storing development artifacts.
12. Click Finish.

Creating a Rational ProjectConsole repository

This section explains how to create a Rational ProjectConsole repository based on Microsoft Access, SQL Server, Oracle, and DB2 database types.

The Rational ProjectConsole Maintenance Tool helps you create a repository for each supported database type.

To create a Rational ProjectConsole repository:

1. Start the Maintenance Tool. Click Start -> Programs -> IBM Rational Software -> IBM Rational ProjectConsole -> ProjectConsole Maintenance Tool.
2. Create or copy a Rational ProjectConsole repository and click Next.
3. Under Rational ProjectConsole repository information, from the Copy from repository list, select a repositories to initialize your new repository:
   • PjC Sample Site: This repository contains all elements of the ClassicsCD.com sample Rational ProjectConsole Web site. These elements include sample users and groups and a Web site navigation tree, in addition to source templates, mappings, target tables, scheduled tasks, metric panels, and collected sample measurement data.

     If you use the PjC Sample Site to initiate a new repository, you can modify it for use with your own data later.

   • PjC Empty Site: This repository contains an empty Rational ProjectConsole site with an empty Web site navigation tree, minimal users and groups, and an empty data warehouse.

     You can use the PjC Empty Site as a starting point for building a Rational ProjectConsole Web site.

   • PjC Demo: The PjC Demo is the Rational ProjectConsole Sample Site. After the installation is complete, this is the site to which Rational ProjectConsole is connected.

   The three repositories in the Copy from repository list that are preconfigured for the software are read-only and can be used only as starting points for a new repository.

   For information about dimension tables and measure tables, see Rational ProjectConsole Designer Help. For information about metrics displays, see Rational ProjectConsole Dashboard Help.

4. In the New repository name field, type a name for the new repository.
5. Under Data warehouse information, from the Database type list, select the vendor for the databases in your new Rational ProjectConsole repository.
6. The information that you must enter next under Data warehouse information depends on the database type you selected.
   • Microsoft Access databases:

     Leave the SchemaRepository and DataWarehouse fields blank. A pair of new databases are created in your Rational ProjectConsole data repository folder.

   • DB2 databases:
     1. Under Schema repository information, type the name of the DB2 schema repository that you created.
     2. Under Schema repository information, type the user name required to log in to the schema repository in the Username field.
     3. Under Schema repository information, type the password required to log in to your schema repository in the Password field.
     4. Under Data warehouse information, type the name of the DB2 data warehouse that you created in the Data warehouse field.
     5. Under Data warehouse information, type the user name required to log in to the data warehouse in the Username field.
     6. Under Data warehouse information, type the password required to log in to the data warehouse in the Password field.
   • Oracle databases:
     1. Under Schema repository information, type the SQL*Net Alias that points to the Oracle schema repository that you created.
     2. Under Schema repository information, type the Oracle login that you created for the schema repository in the Username field.
     3. Under Schema repository information, type the password for the Oracle login that you created in the Password field.
     4. Under Data warehouse information, type the SQL*Net Alias that points to the Oracle data warehouse that you created in the Data warehouse field.
     5. Under Data warehouse information, type the Oracle login that you created for the data warehouse in the Username field.
     6. Under Data warehouse information, type the password for the Oracle login that you created in the Password field.
     7. In the Connect options field, type the Oracle versions installed on the database server and on the client machine using the following format:

        SERVER_VER=X.X

        CLIENT_VER=X.X

        If the database server is a machine other than the Rational ProjectConsole server, the Rational ProjectConsole server is the client.

        Note:
        Rational ProjectConsole supports Oracle versions 9.2 and 10.0.
   • SQL Server databases:
     1. In the Database server field, type the name of the SQL Server database server.
     2. Under Schema repository information, type the name of the SQL Server database you created for the schema repository in the Schema repository field.
     3. Under Schema repository information, type the database owner (DBO or Administrator) login you created for the schema repository in the Username field.
     4. Under Schema repository information, type the password for the database owner login in the Password field.
     5. Under Data warehouse information, type the name of the SQL Server data warehouse you created in the Data warehouse field.
     6. Under Data warehouse information, type the SQL Server user name that you set up to log in to the data warehouse as db_owner in the Username field.
     7. Under Data warehouse information, type the password that you set up to log in to the data warehouse as db_owner in the Password field.
7. Click Finish.

   When the repository is created, you see the message: Operation complete. (This can take some time depending on whether you are creating an empty repository or one that contains data.)

8. To close the Maintenance Tool, click Exit. To return to the first screen, click Done.

Viewing Rational ProjectConsole server startup error information

If an error occurs, examine one of the following log files to find the source of the error. Open the log file in a text editor that allows you to access files that can be opened by another application such as Notepad:

installdir\Rational\Common\rwp\EmbeddedExpress\profiles\profile1\logs\ProjectConsole.log

installdir\Rational\Common\rwp\EmbeddedExpress\profiles\profile1\logs\profile1\systemOut.log  

Upgrading Rational ProjectConsole

This chapter describes the process for upgrading to the current version of Rational ProjectConsole.

Changes in this release

Version 7.0.x of the IBM Rational Team products contains some significant changes to consider when upgrading to this release:

• Products are now installed using Installation Manager. Versions installed with MSI technology must be uninstalled using rationaluninstalltool.exe, as described in Uninstalling Rational products.
• These products are no longer delivered as a Rational Suite. If you are using Rational ProjectConsole to collect metrics and generate reports from various IBM Rational products, you must install each product independently on the Rational ProjectConsole Web server and on each Rational ProjectConsole collection server.
• The Rational Web Platform (RWP) has been upgraded in this release to use IBM HTTP server 6.1.0.13 and IBM WebSphere^(R) Application Server 6.1.0.15.
• SQL Anywhere is no longer a supported database for any IBM Rational products. 
• Rational ProjectConsole uses Cloudscape as its security database. This change was introduced in version 2003.06.15 of Rational Suite. You must migrate your security database to Cloudscape before upgrading to release 7.0.x.
• There have been changes to the data warehouse related to updates to supported database versions and connection options to vendor databases.

Version 7.0.1 of Rational ProjectConsole also includes a required upgrade to feature level 6 for Rational ProjectConsole databases and schemas. The upgrade is done through the Rational ProjectConsole Maintenance Tool. The tool detects whether an upgrade is needed. See Help for the Rational ProjectConsole Maintenance Tool for more information.

The rest of this chapter describes the process of preparing for your upgrade, performing the upgrade, and verifying the upgrade.

Upgrade paths

Table 10 provides instructions for upgrading from earlier releases of Rational ProjectConsole.

If you are upgrading from release earlier than 2003.06.15, you must convert your security database to use IBM Cloudscape. The tool to do this is available from the Rational ProjectConsole Maintenance Tool in the 2003.06.15 release. To upgrade from a release earlier than 2003.06.15:

1. Upgrade to version 2002.06.15 of Rational ProjectConsole.
2. Run the Rational ProjectConsole Maintenance Tool to upgrade your security databases.
3. Upgrade to version 7.0.x of Rational ProjectConsole.

Upgrade preparation and planning

Before upgrading Rational ProjectConsole (and other IBM Rational products), plan the upgrade process carefully.

• Review the upgrade, installation, and release note documentation for all products that you intend to install. Because you are upgrading the Rational ProjectConsole servers, you are likely to be upgrading several other IBM Rational products.
• Determine whether any prerequisites must be met; for example, operating system versions, database software versions, hardware requirements, other required software, and so on.
• Save any information from the current deployment that must be manually preserved. Examples include license server locations and database connect options and parameters.
• Determine whether any special requirements apply; for example, changing the database vendor from SQL Anywhere to another vendor, or converting an Oracle database from using the LONG data type to using the CLOB data type.
• Prepare a checklist for the upgrade procedure as it applies to your site. The list consists of the tasks that the site administrator must perform.

Preparing a plan is important because the upgrade process can be complex, with a number of dependencies among tasks. The plan allows you to sort out these dependencies so that you can upgrade your environment smoothly and efficiently.

Meeting upgrading prerequisites

Every IBM Rational product has prerequisites that must be met before the product can run properly. These prerequisites include specific operating systems and versions, database vendors and versions, and other software and hardware. It usually makes sense to install these products or to upgrade to these versions before you upgrade the IBM Rational product. This approach allows you to perform the upgrade process in a series of smaller steps rather than all at once. Upgrading in phases allows you to control the risks of the upgrade process better and makes it easier to diagnose and fix problems that arise.

For Rational ProjectConsole, verify that these prerequisites have been met before you upgrade your installation.

• Check supported operating systems for version 7.0.x. Ensure that your Rational ProjectConsole Web server and collection servers are running on supported operating systems. Rational Team products no longer support the Microsoft Windows NT^(R) operating system. If you are using Windows NT, you will need to upgrade your server(s) to a supported Windows server operating system.
• If you use SQL Anywhere, migrate to a supported database. If you are using SQL Anywhere for your Rational ProjectConsole data warehouse, change to a supported database vendor. Before upgrading, you must convert any Rational ProjectConsole data warehouses to a supported vendor (Oracle, Microsoft SQL Server, or IBM DB2). A copy of the IBM DB2 express database is distributed with Rational ProjectConsole as an alternative to SQL Anywhere.
• Upgrade your Rational ProjectConsole security databases from SQL Anywhere to IBM Cloudscape. In the 2003.06.xx releases of Rational ProjectConsole, an embedded SQL Anywhere security database is used for authentication and authorization. The code required to migrate the security database from SQL Anywhere to Cloudscape is included in version 2003.06.15 of the IBM Rational Suite. If you are upgrading from a version earlier than 2003.06.15, you must install version 2003.06.15 on your Rational ProjectConsole Web server and use the Rational ProjectConsole Maintenance Tool to convert your security databases. (Note that there is a menu option on the Maintenance Tool that can be used to convert all of your security databases at once.)
• Convert LONG data type to CLOB in Oracle databases. The LONG data type is no longer supported in this release and is being phased out by Oracle. IBM provides a tool to help perform this operation. You can change one database at a time, which means that you can spread this task out over time if convenient for you.
• Uninstall 2003.06.xx versions of Rational products installed on the Rational ProjectConsole Web server as needed. The installation of version 7.0.x of any of the IBM Rational Team products uninstalls the 2003.06.xx version of that Rational product. Because Rational ProjectConsole was previously available only as part of one of the IBM Rational Suite, this means that the installation of one product in the Suite (such as Rational ProjectConsole) uninstalls all products in that suite and forces you to reinstall all the products you want to use on that system, one at a time. However, if you have some Rational products originally installed individually (not as part of the Suite) on your Rational ProjectConsole Web server, then installing a new version of Rational ProjectConsole does not uninstall the old version of that product. You must manually uninstall any IBM Rational products that were individually installed before installing this release of Rational ProjectConsole on your Web server.
• Uninstall 2002.05.xx versions of Rational products installed on the Rational ProjectConsole Web server. The installation of the 7.0.x version of IBM Rational Team products does not uninstall release 2002.05.xx or earlier version of products. Therefore, you must manually uninstall release 2002.05.xx and earlier versions of all IBM Rational products installed on the Rational ProjectConsole Web server before installing this version.

Testing the upgrade plan

When you have an upgrade plan and you have met the external requirements, test your upgrade plan. Test the plan on test systems with copies of your Rational ProjectConsole databases. Testing is the best way to see how long the process takes, to identify any problems in the plan, and to ensure that the plan is accurate before you upgrade your production databases.

System shutdown and backup

After you meet the product requirements and test your upgrade plan, you are ready to start the upgrading process.

Before you begin, shut down the Rational ProjectConsole Web server and back up all databases and other repositories. This precaution allows you to restore your systems to the original state if something goes wrong. If multiple Rational ProjectConsole Web servers are deployed in your organization, you must backup each server. Perform the following steps:

1. Announce to your users that Rational ProjectConsole (and the other IBM Rational products you are upgrading) will not be available as of a specified shutdown time.
2. Check in all data warehouse schemas. This must be done using the Rational ProjectConsole Designer. If you have multiple Rational ProjectConsole data repositories that you test with, check in the schema on each data repository.
3. Shut down your Rational ProjectConsole Web Server.
4. Shut down the Rational ProjectConsole databases. The procedure for this is database-vendor specific, but every database has a way to shut down the database service. With Oracle, for example, you shut down the Oracle instance for that database. With DB2, you stop the database manager instance. Shutting down the databases ensures that they are not locked.
5. Shut down any other IBM Rational products running on the Rational ProjectConsole Web server.
6. Create a full backup of your Rational ProjectConsole data and repositories. This includes backing up the following directories:
   • ..\rational\ProjectConsole
   • ..\rational\common\rwp\webapps\projectconsole (version 2003.06.xx only)
   • ..\rational\jakarta-tomcat\webapps\ProjectConsole (version 2002.05.xx only)
7. Backup each Rational ProjectConsole data warehouse database. The procedure for this task is database-vendor specific. Your database administrator has instructions for backing up your Rational ProjectConsole databases.

Upgrading the Rational ProjectConsole Web server

The 2002.05.xx. version of all Rational products must be uninstalled manually before you upgrade to version 7.0.x. If you are upgrading from version 2003.06.xx of the Rational Suite, you might want to uninstall it manually before upgrading. If you do not uninstall version 2003.06.xx, the version 7.0.x installation automatically uninstalls this version.

To upgrade your Rational ProjectConsole Web server:

1. If your Rational ProjectConsole Web Server was previously used as your license server, you must first install the IBM Rational License Manager on your Rational ProjectConsole Web Server.
2. Install version 7.0.x of Rational ProjectConsole on your Web Server. Select all available Rational ProjectConsole options. The installation requires at least one system reboot. See Installing Rational ProjectConsole.
3. Skip this step if you are upgrading from the 2003.06.xx release of Rational ProjectConsole.

   Migrate any data from 2003.05.xx repositories. Migrate your Rational ProjectConsole data from the old repositories to the new repositories. This task includes migrating the users and groups that were stored previously in the Rational ProjectConsole data warehouse into the new security database. It also includes migration of the Rational ProjectConsole explorer tree into the new security database.

   To migrate the data:

   1. Open the Rational ProjectConsole Maintenance Tool. Click Start > Programs > IBM Rational > IBM Rational ProjectConsole > ProjectConsole Maintenance Tool.
   2. Select Migrate data from Rational ProjectConsole version 2002.05.00.
4. Migrate any data from the 2003.06.xx repositories. If you are upgrading from the 2002.05.xx release of Rational ProjectConsole, skip this step.

   This release of Rational ProjectConsole includes changes to the Rational Web Platform. The most visible change is the location to which the Rational ProjectConsole Web application is deployed. In version 2003.06, the Rational ProjectConsole Web application was stored in:

   ..\rational\common\rwp\webapps\ProjectConsole 

   In version 7.0.x, the Rational ProjectConsole Web application is stored in:

   ..\rational\common\rwp\EmbeddedExpress\Profiles\
         InstalledApps\defaultNode\PJCWASAPP.ear\PJCWeb.war

   The installation process moves your Rational ProjectConsole security database to the new folder, restoring the Rational ProjectConsole explorer tree. However, you must manually relocate all of the following items:

   • Icons, Web pages, or other related information
   • Cached reports
   • Published charts

     In this release, the PublishedViews folder has been moved to the installdir\Rational\ProjectConsole\webfiles folder. This move was required to accommodate the extended path name prefix for the new version of Rational Web Platform (RWP).

   • Path names to static Web pages
     1. Copy or move any updated or stored any information, such as icons, Web pages, and so on, in the Rational ProjectConsole webapps folder, to the new location in the PJCWeb.war folder.
     2. Copy or move to the new location any cached artifact reports generated by Rational ProjectConsole that you want to keep. To copy the reports, move the generated folder hierarchy from the previous Web application folder to the PJCWeb.war folder. If you do not move the old report cache, a new cache is generated the next time an artifact report is requested.
     3. To keep published charts, copy the published views folder hierarchy from the previous Web application folder to the ...\installdir\Rational\ProjectConsole\webfiles folder. If you do not move your previous published charts, the chart is regenerated the next time a Rational ProjectConsole published chart task runs.
     4. If you have updated the Rational ProjectConsole explorer tree with physical path names to static Web pages in the Rational ProjectConsole Web application folder, those references must be updated manually. The easiest way to accomplish this is to browse through the Rational ProjectConsole tree after completing the upgrade, and verify that all tree nodes are still working.
5. Upgrade any required Rational ProjectConsole data warehouse connections, Upgrading data warehouse connections
   • DB2 data repositories. If your Rational ProjectConsole data warehouse is configured to use a DB2 data repository, you must manually re-establish the connection to the data warehouse by using the Rational ProjectConsole Maintenance Tool. This task is required because the ODBC drivers used to access DB2 databases changed in version 7.0. If you are using a remote DB2 database server, you are no longer required to have a DB2 client installed on the Rational ProjectConsole Web server.

     Therefore, the connection parameters stored for your DB2 database must be updated. When you run the Rational ProjectConsole Maintenance Tool and select Connect to a Data Repository, there is a check box that enables you to change the database configuration settings. You must obtain the updated parameters from your DB2 administrator.

   • Oracle data repositories. If your Rational ProjectConsole data warehouse is configured to use an Oracle data repository, you might also need to manually re-establish the connection to the data warehouse. If you had previously upgraded to the 2003.06.15 release, you might have performed this step.
6. In version 7.0.x, the names of the ProjectConsole services that are installed have changed. The following table lists the previous name and new name of each service. If you had previously configured any Rational ProjectConsole service to log in using a domain account, you must change the login parameters for the newly installed services to use the same domain login parameters that you used for version 2003.06.15 of the services. Use the Windows services applet to reconfigure the login parameters of your Rational ProjectConsole services.

   2003.06.15 service name	7.0.x service name
   Rational ProjectConsole Collection Server	IBM Rational ProjectConsole Collection Server
   Rational ProjectConsole Dashboard Server	IBM Rational ProjectConsole Dashboard Server
   Rational ProjectConsole Report Server	IBM Rational ProjectConsole Report Server

7. When the Rational ProjectConsole installation is complete, upgrade any other Rational products that were previously installed on the Rational ProjectConsole Web server.  For instructions, see the installation and upgrade documentation for each product.
8. Verify that you can log in to the Rational ProjectConsole Web site, navigate through the Rational ProjectConsole tree, and run the Dashboard and Designer applets.

Upgrading the Rational ProjectConsole collection server

Upgrading the Rational ProjectConsole collection server is a simpler process than upgrading the Rational ProjectConsole Web Server. The version 2002.05.xx release of all Rational products must be uninstalled manually before upgrading to version 7.0.x. If you are upgrading from version 2003.06.xx of Rational Suite, you might want to uninstall it manually before upgrading to version 7.0.x. If you do not uninstall version 2003.06.xx, the version 7.0.x, installation automatically uninstalls this version.

To upgrade your Rational ProjectConsole collection servers:

1. Upgrade your Rational ProjectConsole Web Server before upgrading the Rational ProjectConsole Collection servers.
2. Install the new version of Rational ProjectConsole on your Web Server.

   Accept the default install options. Do not install the Rational ProjectConsole Web server components.

3. In version 7.0.x, the names of the ProjectConsole services that are installed have changed. The following table lists the previous name and new name of each service. If you had previously configured any Rational ProjectConsole service to log in using a domain account, you must change the login parameters for the newly installed services to use the same domain login parameters that you used for version 2003.06.15 of the services.

   2003.06.15 service name	7.0.x service name
   Rational ProjectConsole Collection Server	IBM Rational ProjectConsole Collection Server
   Rational ProjectConsole Dashboard Server	IBM Rational ProjectConsole Dashboard Server
   Rational ProjectConsole Report Server	IBM Rational ProjectConsole Report Server

4. Upgrade any other Rational products that were previously installed on the Rational ProjectConsole Web server.
5. Log in to the Rational ProjectConsole Web server and verify that metric collections and artifact reports can be generated on the upgraded Rational ProjectConsole collection server.

System restart and verification

After the Rational ProjectConsole Web server and Rational ProjectConsole collection servers are upgraded, restart the Web server and each collection server to verify that they are working properly.

After you restart the systems, log in to the Rational ProjectConsole Web server and verify that you can display your Rational ProjectConsole tree nodes, use the Designer and Dashboard applets, generate artifact reports, and run metrics collections.

Announcing server availability

After all Rational ProjectConsole servers and all applicable IBM Rational products are restarted, you can announce the availability of Rational ProjectConsole and the other products to your users. It should now be possible to access all upgraded databases using both version 7.0.x and earlier client versions.

Upgrading data warehouse connections

The supported database vendors and versions have changed. See Table 11 for a complete list of the database vendors and versions for version 7.0.x. In some cases, the version of the database that you are using might no longer be supported.

One upgrade requirement is to upgrade to version 2003.06.15 first to convert the embedded SQL Anywhere security database to the IBM Cloudscape format. For every supported database vendor, there is a version supported by both version 2003.06.15 and version 7.0.x.

Upgrade your database to the version supported by both the 2003.06.15 and 7.0.x release while you still have the 2003.06.15 release installed. After you upgrade the database version, make sure that your 2003.06.15 version of Rational ProjectConsole is working properly before upgrading to the 7.0.x release.

DB2 data repositories

The ODBC drivers used to connect to DB2 in the 2003.06 have been replaced. One benefit of using the new drivers is that DB2 client software is no longer required to connect to a DB2 database hosted on a remote DB2 server. However, to connect to the DB2 database using the new drivers, the connection parameters must be changed. Refer to Table 12 and Table 13 for a mapping between the connection parameters used in the 2003.06.15 release and the connection parameters used version 7.0.

After installing version 7.0.x, you must run the ProjectConsole Maintenance Tool and reconnect to your DB2 data repository. The connection screen of the ProjectConsole Maintenance Tool is populated with parameters used to connect to the 2003.06.15 version for the old ODBC driver. You must select the Edit Warehouse Information button and update the connection parameters to match the parameters given to you by your database administrator.

Microsoft Access data repositories

Although Rational ProjectConsole does not support Microsoft Access for production use, many people use it to create demos or for proof of concept. In the 2003.06.15 release of Rational ProjectConsole, when you created a Microsoft Access data repository, it was based on a Microsoft Access 97 schema. Beginning with version 7.0, Microsoft Access 97 is no longer supported, and you are required to upgrade your databases to a Microsoft Access 2000 (or later) file format.

All new ProjectConsole data repositories created in version 7.0.x are automatically generated in the Microsoft Access 2000 format.

If you have any Microsoft Access data repositories, you have the following upgrade options.

• Before you upgrade to version 7.0.x, you can use the ProjectConsole Maintenance Tool to upgrade your Microsoft Access data repositories to another supported vendor (DB2, Oracle, or SQL Server). A copy of DB2 Express^(TM) is included in the 2003.06.15 release.
• Another option is to convert your Microsoft Access databases from the Access 97 format to Access 2000. To do this, you need a copy of Microsoft Access 2000 or a later version.

Converting databases from Access 97 to Access 2000

You must have Microsoft Access 2000 or a later version installed to use this procedure.

1. Stop the Rational ProjectConsole Dashboard Server service.
2. Start Microsoft Access 2000 (or a later version).
3. Open the file datawarehouse.mdb in your data repository. (The data repositories are located in the folder ...\Rational\ProjectConsole\DataRepository).
4. Click Tools > Database Utilities > Convert Database to convert the database. Rename the database when prompted.
5. Open the file schemarepository.mdb.
6. To convert the database, click Tools > Database Utilities > Convert Database. When prompted, rename the database.
7. Close Microsoft Access.
8. Replace the existing files datawarehouse.mdb and schemarepository.mdb with the converted versions.
9. Repeat for each data repository.
10. After all data repository files are converted, restart the Rational ProjectConsole Dashboard Server service.

Microsoft SQL Server Data Repositories

If you are using a version of Oracle supported by both the 2003.06.15 release and version 7.0.x, no changes are required in to connect to your SQL Server databases.

Oracle data repositories

If you are using a version of Oracle supported by both the 2003.06.15 release and version 7.0, no changes are required in 7.0 to connect to your Oracle databases.

Sybase SQL Anywhere data repositories

SQL Anywhere is no longer supported. If you are using SQL Anywhere for your Rational ProjectConsole data warehouse, you must convert each of your data repositories from SQL Anywhere to a supported database vendor.

Appendix. Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service might be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right might be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing 
IBM Corporation North Castle Drive 
Armonk, NY 10504-1785 
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing 
2-31 Roppongi 3-chome, Minato-ku 
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM might make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM might use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation 
Department BCFB
20 Maguire Road
Lexington, MA 02421 
U.S.A. 

Such information might be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments might vary significantly. Some measurements might have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement might have been estimated through extrapolation. Actual results might vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(c) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (c) Copyright IBM Corp. _enter the year or years_. All rights reserved.

Additional legal notices are described in the legal_information.html file that is included in your Rational software installation.

Trademarks

ClearCase, ClearQuest, DB2, DB2 Universal Database, IBM, Passport Advantage, ProjectConsole, Rational, Rational Portfolio Manager, Rational Suite, SoDA, SP1, and SP2, are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product or service names might be trademarks or service marks of others.