Deploy and configure IBM Rational ClearQuest 7.0 on Linux

Document options Document options requiring JavaScript are not displayed Rate this page Help us improve this content

Level: Intermediate

Haofeng Zhou (zhouhf@cn.ibm.com), Staff Software Engineer, IBM

05 Feb 2008

This guide explains how to install and configure IBM® Rational® ClearQuest® Version 7.0 on the Linux® platform. Although ClearQuest 7.0 provides comprehensive solutions for Linux, as well as for Microsoft® Windows®, deploying and configuring it on Linux is somewhat more difficult. Also, users must upgrade to the current version of ClearQuest to access the existing database. You will also learn how to deploy the ClearQuest Web component on IBM® WebSphere® Application Server rather than on the ClearQuest Web application and get troubleshooting tips for connecting to the database created or configured by previous versions of ClearQuest. This article is intended for readers who have some similar experience on Windows.

Getting started

The IBM® Rational® ClearQuest® Version 7.0 for Linux® installation package is somewhat different from the Microsoft® Windows® version. There are no administration tools, such as the Maintenance Tool, User Administration, and ClearQuest Designer, in the Linux installation package. Therefore, to deploy ClearQuest on Linux, it is necessary to set up a Windows platform for administration purposes.

For the backend database for ClearQuest, we set up an IBM® DB2® database on Linux to use in examples for this article. It is important to be aware that ClearQuest 7.0 includes a driver to access a DB2 server, rather than using the DB2 client that was mandatory in previous releases.

Setup used in these examples

The examples used in this article are based on this setup:

• Databases for ClearQuest 7.0 have been created on Linux and configured through the ClearQuest 7.0 administration tools within Windows. Table 1, which follows, shows the connection information.

• Two existing DB2 databases have been created, in Windows, and configured by the previous ClearQuest previous version, 2003.06.19. The connection information for those is also listed in Table 1.

• IBM WebSphere Application Server is installed on the same Linux machine where ClearQuest 7.0 will be deployed, in this directory:
  /opt/IBM/WebShphere

• The installation package was not unpacked into the /images/CQ7Install/linux_x86 location, where there are two subdirectories: clearquest and common

• A Rational License issue that existed previously has been resolved. Thus, in preparing examples for this article, we used the remote license server.

Back to top

Deploy ClearQuest 7.0 on Linux

First, set up the installation package in a release area using the command prompt.

Set up a release area

1. Navigate to this directory: /images/CQ7Install/linux_x86/clearquest/install
2. Issue this command: /site_prep
3. At the prompt for the ClearQuest license host, enter the license server address.
4. At the prompt for the HTTP port for Rational Web Platform, use the default value: 80
5. Leave the account name for Rational Web Platform as "nobody."
6. Leave the group name for Rational Web Platform as "nobody."
7. At the prompt to enable e-mail notification, select No.

Note:
The values set in Steps 4, 5 and 6 are not relevant in this article. Simply accept all the default ones to continue the process.

Install ClearQuest components

1. Navigate to /images/CQ7Install/linux_x86/clearquest/install , and issue the ./install_release command to begin installation.
2. At the prompt to choose installation methods, select 1: Local Install
3. Enter 1 to accept the license agreement.
4. At the prompt to choose installation operations or models, choose 2: Full-copy
5. Specify the installation folder: /opt/rational for examples in this article
6. Accept the default value for Pathname to the network-wide release directory, which should be the same as what had been set in the release area setup process.
7. At the prompt to select the components to install (see Figure 1), choose these items: 1. ClearQuest and 2. ClearQuest Server. Do not specify 3, ClearQuest Web Application, because you will configure IBM® WebSphere® Application Server for such functionality.

8. When you have completed the previous steps, you will see asterisks beside items 1 and 2 (see Figure 2) to indicate those items as your choices. Select f: finish selection.

9. Specify the License Server at the prompt.
10. At the prompt to enable e-mail notification, select No.
11. At the prompt, select Yes to continue installation.
12. Accept the default value for ClearQuest database registry directory. If it does not exist, just accept the default value to create it.
13. Wait until the installation is finished, without errors.

Modify environment variables

1. Before running ClearQuest, it is necessary to add the entries shown in Listing 1 to the Linux login environment in the /root/.bashrc file.

                
#ClearQuest
export TZ=PRC
export LD_ASSUME_KERNEL=2.4.19
export LD_LIBRARY_PATH=/opt/rational/clearquest/linux_x86/shlib
export MOZILLA_FIVE_HOME=/nowhere
. /opt/rational/clearquest/cq_setup.sh

2. Log out and log in again to make those variables effective, and then issue the clearquest command to launch ClearQuest on Linux.

Back to top

Configure the database connection on the ClearQuest client

1. In ClearQuest client, click File > Database > Manage Connections to display the ClearQuest Connection Management panel (Figure 3).

2. In the ClearQuest Connection Management panel (Figure 3), click Add Database Set to launch the New ClearQuest Database Set options shown in Figure 4.
3. Type the connection name in the Name field (DB4CQ in this example), and, from the drop-down menu, choose DB2 as vendor.
4. Then click Next.

5. In the next window of the New ClearQuest Database Set wizard, specify the server name or IP address for Server field, the schema repository database name for the Database field, the database access account and password, and, essentially, the port option for DB2 connection mentioned in the Assumption section, previously. For this example, as Figure 5 shows, we used these entries:
• Server: 192.068.0.34 (selected from the drop-down menu)
• Database: DB4CQSHR (selected from the drop-down menu)
• User Name: db2inst2
• Password: *******
• Connect Option: port=500001
6. Then click Finish to complete creation of the database set.

7. Now, set the connection to user database by highlighting the database set that you just created (DB4CQ in the example that Figure 6 shows), and then clicking Add Connection .

8. Leave the Schema Repository name as it shows (which is the same as Database Set name), click Next, and then specify your User ID to access the user database, which is defined in the ClearQuest User Administration tool.
9. Click Finish (see Figure 7).

10. Next, choose the user database from the drop-down menu, and type the correct password to log in to the repository (Figure 8).

Now you are ready to work on the selected user database within ClearQuest.

Back to top

Deploy and configure the ClearQuest Web client on WebSphere Application Server

In the ClearQuest packages, you can use the Web application included, as the option 3 indicated in Figure 3. However, you might prefer to deploy and configure ClearQuest Web on IBM WebSphere Application Server (WebSphere for short hereafter) for various reasons, such as unified architecture, scalable performance, and so on. For that alternative, follow these steps:

1. Launch the WebSphere Application Server Administration Console on Linux from the main menu, and log in.
2. Under Applications in the directory tree on the left, click Install New Application, as shown as Figure 9.
3. In the Full path field in the middle panel, enter this EAR file name:
   /opt/rational/clearquest/cqweb/cqwebws.ear
4. Click Next to proceed.

5. Accept all of the default settings (no action required), and click Step 3, Summary (see Figure 10).
6. Then click the Finish button at the bottom of the Summary page.

7. Next, click "Save directly to the master configuration" (see Figure 11).

8. In the command console where WebSphere Application Server is installed, navigate to the Classes directory:
   /opt/IBM/WebSphere/AppServer/profiles /AppSrv01/installedApps/localhostNode01Cell/RationalClearQuestWeb.ear/CQWebModule.war/WEB-INF/classes
9. Modify the common.properties file to specify the properties shown in Listing 2.

                
CQ_WEB_SERVER_NAME=localhost
PROPERTIES_DIR=/opt/IBM/WebSphere/AppServer/profiles/AppSrv01
		/installedApps/localhostNode01Cell/RationalClearQuestWeb.ear
		/CQWebModule.war/WEB-INF/classes
UPLOAD_DIR=/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps
		/localhostNode01Cell/RationalClearQuestWeb.ear/CQWebModule.war
		/htdocs/cqattachments
DOWNLOAD_DIR=/cqweb/htdocs/cqattachments
CHTRPT_DOWNLOAD_DIR=/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps
		/localhostNode01Cell/RationalClearQuestWeb.ear/CQWebModule.war
		/htdocs/cqchtrpts
CHTRPT_DOWNLOAD_URL=/cqweb/htdocs/cqchtrpts

10. Return to the administration console.
11. Click OK on the Update global Web Server Plug-In Configuration view of the WebSphere administrative console (Figure 12) to regenerate the plug-in configuration.

12. Now, restart WebSphere Application Server, and then start the Rational ClearQuest Web application.
13. Verify the Rational ClearQuest Web application deployment on WebSphere by entering the following Web address in your browser, similar to what Figure 18 shows:
    http://localhost:9080/cqweb/login

Back to top

Connect to IBM DB2 databases created by previous versions of ClearQuest

When you want to add a connection that is based on the Connection Set to an IBM® DB2® database that was created and configured by a previous version of ClearQuest (2003.06.19, for example), that connection might fail. The reason is that, before ClearQuest 7.0, the database connection in ClearQuest depended on a DB2 client, where the database information was cataloged to a local machine for connecting. It is not a problem that the server name information in the Repository Schema for both master and user databases are the same as their corresponding database names. However, ClearQuest 7.0 no longer needs a DB2 client, because it accesses DB2 database directly, based on the connection information installed in schema repository, including the server name. Thus, the name of that server is essential to the connection.

Therefore, when you use ClearQuest 7.0, use the ClearQuest Maintenance Tool and ClearQuest Designer to update server information for both the schema repository and user database. Such updating will not affect users of previous versions of ClearQuest.

Update the schema repository

1. Launch the ClearQuest Maintenance Tool in Windows, and create a new connection to the Repository Schema for the database in the previous version of ClearQuest, as shown in Figure 14. You will need to complete these fields:
• Vendor
• Server
• Database
• User Name
• Password
• Connect Options (if any, or leave blank)

2. When you have finished creating the new connection, notice that the server name for the connection has changed from 9.181.112.59 to s_cqtm, as shown in Figure 15.

3. From the menu, select Schema Repository > Update > Selected Connection.
4. Change the server name from s_cqtm to the IP address or server name where the database is located (in this example: 9.181.112.59), as Figure 16 shows.
5. Click Next.

6. Enter the super user name and password (admin for this example), as Figure 17 shows, to proceed.

7. Click Done to finish.
8. Now, verify that the server information is correct under Existing Connections (see Figure 18).

Update the user database

1. Launch ClearQuest Designer in Windows, and choose the connection that you just created in the ClearQuest Maintenance Tool (CQ2003DB in this example).
2. Log in with correct user account and password.
3. From the ClearQuest Designer menu, select Database > Update User Database Properties, choose the user database (logical database) to update, and then click the Properties button.
4. Change the Server name from ur_cqtm to the IP address or server name where the database is located (9.181.112.59 in Figure 19).
5. Click Update.

You can verify that the server information is correct, and you can now access the database from the ClearQuest 7.0 client.

Share this... Digg this story Post to del.icio.us Slashdot it!

Resources

• To learn more about ClearQuest, try taking one of IBM's ClearQuest courses.
  
  
• Online documentation for ClearQuest users and administrators is available at the IBM Software Information Center.
  
  
• In the Rational area on developerWorks, get the resources you need to advance your skills in the Rational arena.
  
  
• Read the article: Configuring ClearQuest to use DB2 as your backend RDBMS, IBM developerWorks (November 2005)
  
  
• Read the datasheet for IBM Rational ClearQuest.
  
  
• Browse the technology bookstore for books on these and other technical topics.
  
  

• ClearQuest users and administrators can find more resources in the ClearQuest section of the developerWorks Rational zone, including hooks, Eclipse plug-ins, product documentation, articles and whitepapers.
  
  
• Download IBM product evaluation versions and get your hands on application development tools and middleware products from DB2®, Lotus®, Rational®, Tivoli®, and WebSphere®.

• Check out the ClearQuest discussion forum on developerWorks Rational.
  
  
• Check out developerWorks blogs and get involved in the developerWorks community.
  
  

About the author

		Haofeng Zhou is a Staff Software Engineer at the IBM Shanghai Globalization Lab, located in Shanghai, China. He works on STG Information Center testing projects and is interested in testing, globalization, and databases.

Rate this page

Please take a moment to complete this form to help us better serve you. Did the information help you to achieve your goal? Yes No Don't know   Please provide us with comments to help improve this page:   How useful is the information? 1 2 3 4 5 Not useful Extremely useful

Back to top