Configuring CM Server

These topics describe how to configure and customize CM Server.
CM Server is installed with a default configuration, which is suitable for most sites. Some sites might need to modify the CM Server configuration after installation to accommodate various host- or site-specific requirements. For example:

The Administration console that is included with WebSphere® Application Server supports managing SSL certificates. You can connect to the console and find more information on using it at this location: http://hostname:12060/ibm/console.

If you are currently using Open SSL certificates and are upgrading your point product, see the procedures in Converting Open SSL certificates to IBM SSL. For more information on managing SSL certificates with WebSphere Application Server, see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp.

Some attributes in configuration files can be viewed or set as CM Server MBean parameters. See Setting available MBean attributes for more information.

Do not modify any CM Server configuration files other than those described in this user assistance. Some of the configuration options cannot be changed without adversely affecting the operation of CM Server.

Default values for CM Server

There are default values for ports:
  • Port 12080 for the CM Server URL. The CM Server URL is http://server-host:12080/TeamWeb/services/Team
  • Port 12060 for the Administration console that is included with WebSphere Application Server. The WebSphere Application Server Administration console URL is: http://server-host:12060/ibm/console
Note: WebSphere Application Server administrative security is not enabled by default. For information on how to enable it, see: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp. For more information on WebSphere Application Server administrative security, see: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp.

Setting up a CM Server host to provide access to ClearQuest functionality

To enable use of Rational ClearQuest by Rational ClearQuest Web clients and Rational ClearCase remote clients either for accessing ClearQuest databases or for accessing the ClearCase-ClearQuest UCM integration, you must install and configure Rational ClearQuest with the CM Server for ClearQuest Web feature on the CM Server machine.

To install and configure Rational ClearQuest on the CM Server:
  1. Install Rational ClearQuest with the CM Server for ClearQuest Web feature on the CM Server.
  2. Create connections to Rational ClearQuest schema repositories. You use the Rational ClearQuest Maintenance Tool to create connections to your Rational ClearQuest schema repositories. For more information, see Creating connections to ClearQuest schema repositories from a CM Server.
The following restrictions apply when using a CM Server host.
  • On Windows

    When your CM Server host is running Windows, operations that are subject to Rational ClearCase permissions checking are not supported when run from within Rational ClearQuest hooks. These operations run with the identity of the local system account (NT AUTHORITY/System), which may not have the Rational ClearCase permissions required to perform them.

  • On Linux or the UNIX system

    You must provide approximately 100 MB of swap space per active Rational ClearQuest user. There must be sufficient physical memory to accommodate approximately ten percent of this swap space.

    If Rational ClearQuest is not installed in the default location on the server, you must specify the location where Rational ClearQuest is installed by setting the ccrcUnixCqHome MBean value to the full path name to the directory where Rational ClearQuest is installed on the server. For more information about setting MBean values, see Setting available MBean attributes.

    If the Rational ClearQuest database type is DB2, you must modify the Rational ClearQuest startup script (installed in /opt/ibm/RationalSDLC/clearquest/bin/clearquest on Linux, and in /opt/IBM/RationalSDLC/clearquest/bin/clearquest on UNIX) on the Rational ClearCase server for remote clients. Add two lines near the end of the startup script, just above the line that reads: # exec into program binary with any options:
    echo setting up DB2 environment
      . DB2-profile-path
    In the preceding example, DB2-profile-path is the full pathname to the db2profile file, typically found in the DB2 instance owner directory, DB2-instance-dir/sqllib on the Rational ClearCase server (/home/db2inst/sqllib/db2profile, for example).
    Note: You must begin the pathname to the db2profile file with a dot and a space.

Creating connections to ClearQuest schema repositories from a CM Server

On a CM Server machine where ClearQuest is installed (regardless of whether this is done to support accessing ClearQuest functionality from the Rational ClearQuest Web client or from the Rational ClearCase Remote Client), one required setup step is to create connections to the Rational ClearQuest schema repositories that are going to be accessed from a client or clients.

On a Windows CM Server machine, when using the Rational ClearQuest Maintenance Tool to create these connections, it is important to follow these rules:
  • The Rational ClearQuest Maintenance Tool should be run only when the user is logged into a local user account (not a domain user account) and it should be a local user account that is part of the local admin group.
  • Each time the Rational ClearQuest Maintenance Tool is used to create a connection, it should be run from the same user account.
If these rules are not followed, some users, when logged into the Rational ClearQuest Web client or the Rational ClearCase Remote Client, may not be able to access all Rational ClearQuest schema repositories for which connections were created.
Related concepts
CM Server architecture
CM Server deployment models
Monitoring CM Server
Using CM Server with an existing installation of IBM WebSphere Application Server
Related reference
CM Server hardware and software requirements
CM Server installation directory

Comentarios