Forcing an SSL connection with Change Management Server (CM Server) for ClearQuest Web

Technote (FAQ)


Question

How do you force an SSL connection with Change Management Server (CM Server) for ClearQuest Web?

Cause

There are incorrect path specifications and incomplete information in the ClearCase and ClearQuest 7.1 and 7.1.0.1 help and Information Centers on how to force an SSL connection with Change Management Server for ClearQuest Web.


Answer


Forcing an SSL connection with CM Server for ClearQuest Web
You can force the Change Management Server (CM Server) to process non-SSL requests as SSL requests.

The following variables are used in path names in this topic:

yourServerName
CM Server host name

RATIONAL_COMMON
Directory where the Rational common files are installed

To force CM Server to process non-SSL requests as SSL requests:

1. Edit the file httpd.conf, which is located in the following directory:


    On Windows®:
    drive :%RATIONAL_COMMON%\IHS\conf

    On the UNIX® system and Linux®:
    $RATIONAL_COMMON/IHS/conf

    a. Add or modify the VirtualHost settings to include the following commands. Replace yourServerName with the name of your CM Server host, and RATIONAL_COMMON with the path specification where the Rational common files are installed. Ensure that the commands are placed above the line # WinNT MPM so that they run before the WebSphere® Application module and the WebSphere Plug-in module:

    On Windows:
    <VirtualHost *:80>
    ServerName
    yourServerName
    RewriteEngine on
    RewriteCond %{SERVER_PORT} !^443$
    RewriteRule ^(.*)$ https://
    yourServerName $1 [R]
    RewriteLogLevel 0
    RewriteLog "
    drive :\%RATIONAL_COMMON%\IHS\logs\rewrite.log"
    </VirtualHost>


    On the UNIX system and Linux:
    <VirtualHost *:80>
    ServerName
    yourServerName
    RewriteEngine on
    RewriteCond %{SERVER_PORT} !^443$
    RewriteRule ^(.*)$ https://
    yourServerName $1 [R]
    RewriteLogLevel 0
    RewriteLog "$RATIONAL_COMMON/IHS/logs/rewrite.log"
    </VirtualHost>


    b. Include the file ssl.conf by adding the following command:

    # include ssl information
    Include conf/ssl.conf


    c. Save your changes and close the file.

2. Edit the file ssl.conf to provide the correct SSL certificate path information for the key database file name. The file ssl.conf is located in the following directory:
    On Windows:
    drive :\%RATIONAL_COMMON%\IHS\conf

    On the UNIX system and Linux:
    $RATIONAL_COMMON/IHS/conf
    For example, for the default installation directory on Windows, the keyfile is located here:
    KeyFile "C:/PROGRA~1/IBM/RATION~1/common/IHS/key.kdb"

      Run the IBM HTTP Server Key Management utility if you are unsure of the key database file location.

      Save your changes and close the file.



    3. Edit the file cqServerConn.properties, which resides in the following directory:

      On Windows:
      drive :\%RATIONAL_COMMON%\CM\profiles\ profileName \installedApps\ nodeName CMProfileNode01Cell\RationalClearQuestWeb.ear\CQWebModule.war\WEB-INF\classes
      On the UNIX system and Linux:
      $RATIONAL_COMMON/CM/profiles/ profileName /installedApps/ nodeName CMProfileNode01Cell/RationalClearQuestWeb.ear/CQWebModule.war/WEB-INF/classes

      a. Change the value of the parameter HELP_SERVER_URL from this:
      HELP_SERVER_URL=http://localhost

      to this:
      HELP_SERVER_URL=https://localhost

      b. Save your changes and close the file.

    4. Restart the IBM HTTP Server.

    Cross reference information
    Segment Product Component Platform Version Edition
    Software Development Rational ClearCase CM Server Linux, Solaris, Windows 7.1, 7.1.0.1

    Rate this page:

    (0 users)Average rating

    Document information


    More support for:

    Rational ClearQuest
    CM Server

    Software version:

    7.1, 7.1.0.1

    Operating system(s):

    Linux, Solaris, Windows

    Reference #:

    1377601

    Modified date:

    2013-09-16

    Translate my page

    Machine Translation

    Content navigation