Configuring mod_proxy support for Apache

To configure an instance of Apache HTTP Server to support proxy access to RWP, you must configure the Apache HTTP Server with proxy support supplied by the Apache mod_proxy module. Detailed information about how to do this is available at http://www.apache.org/. The following is a summary of the steps you will need to take:
  1. Configure the Apache HTTP Server to load the mod_proxy module and the other modules upon which it depends. This typically requires you to uncomment various LoadModule directives related to mod_proxy support in the Apache httpd.conf file. For example:
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_http_module modules/mod_proxy_http.so 
  2. Uncomment the ProxyRequests On directive in the <IfModule mod_Proxy.c> block in httpd.conf:
    <IfModule mod_proxy.c>
    ProxyRequests On
    </IfModule>

    If you are configuring reverse proxy support, change the ProxyRequests parameter value from On to Off. For forward proxy support, leave this parameter set to On. Setting ProxyRequests to Off does not disable use of ProxyPass directives.

  3. Add the appropriate ProxyPass and ProxyPassReverse directives within the <IfModule mod_proxy.c> block in httpd.conf. ProxyPass and ProxyPassReverse directives are application specific.

    In this example, the hostname is the name of the RWP server host and port is an optional port number, which you must specify if you have changed the default port on which RWP listens for HTTP requests (see To change the default RWP HTTP port).

    ProxyPass / http://hostname[:port]/
    ProxyPass /cqweb/ http://hostname[:port]/cqweb/
    ProxyPass /wre/ http://hostname[:port]/wre/
    ProxyPass /common/ http://hostname[:port]/common/
    ProxyPass /px/ http://hostname[:port]/wre/px/
    ProxyPass /wpf/ http://hostname[:port]/wre/wpf/
    ProxyPass /dct/ http://hostname[:port]/dct/
    ProxyPass /scripts/ http://hostname[:port]/scripts/
    ProxyPass /view/ http://hostname[:port]/view/
    ProxyPass /siteconfig/ http://hostname[:port]/wre/siteconfig/
    ProxyPass /help/ http://hostname[:port]/view/browser/help/
    ProxyPass /doc/ http://hostname[:port]/doc/
    ProxyPass /html/ http://hostname[:port]/wre/common/html/
    
    ProxyPassReverse / http://hostname[:port]/
    ProxyPassReverse /cqweb/ http://hostname[:port]/cqweb/
    ProxyPassReverse /wre/ http://hostname[:port]/wre/
    ProxyPassReverse /common/ http://hostname[:port]/common/
    ProxyPassReverse /px/ http://hostname[:port]/wre/px/
    ProxyPassReverse /wpf/ http://hostname[:port]/wre/wpf/
    ProxyPassReverse /dct/ http://hostname[:port]/dct/
    ProxyPassReverse /scripts/ http://hostname[:port]/scripts/
    ProxyPassReverse /view/ http://hostname[:port]/view/
    ProxyPassReverse /siteconfig/ http://hostname[:port]/wre/siteconfig/
    ProxyPassReverse /help/ http://hostname[:port]/view/browser/help/
    ProxyPassReverse /doc/ http://hostname[:port]/doc/
    ProxyPassReverse /html/ http://hostname[:port]/wre/common/html/

    For example, the following directives would configure the proxy server to support access by the Rational ClearQuest Web interface to an RWP process listening on port 81 of a host named RWP_host.

    ProxyPass / http://RWP_host:81/
    ProxyPass /cqweb/ http://RWP_host:81/cqweb/
    ProxyPass /wre/ http://RWP_host:81/wre/
    ProxyPass /common/ http://RWP_host:81/common/
    ProxyPass /px/ http://RWP_host:81/wre/px/
    ProxyPass /wpf/ http://RWP_host:81/wre/wpf/
    ProxyPass /dct/ http://RWP_host:81/dct/
    ProxyPass /scripts/ http://RWP_host:81/scripts/
    ProxyPass /view/ http://RWP_host:81/view/
    ProxyPass /siteconfig/ http://RWP_host:81/wre/siteconfig/
    ProxyPass /help/ http://RWP_host:81/view/browser/help/
    ProxyPass /doc/ http://RWP_host:81/doc/
    ProxyPass /html/ http://RWP_host:81/wre/common/html/
    
    ProxyPassReverse / http://RWP_host:81/
    ProxyPassReverse /cqweb/ http://RWP_host:81/cqweb/
    ProxyPassReverse /wre/ http://RWP_host:81/wre/
    ProxyPassReverse /common/ http://RWP_host:81/common/
    ProxyPassReverse /px/ http://RWP_host:81/wre/px/
    ProxyPassReverse /wpf/ http://RWP_host:81/wre/wpf/
    ProxyPassReverse /dct/ http://RWP_host:81/dct/
    ProxyPassReverse /scripts/ http://RWP_host:81/scripts/
    ProxyPassReverse /view/ http://RWP_host:81/view/
    ProxyPassReverse /siteconfig/ http://RWP_host:81/wre/siteconfig/
    ProxyPassReverse /help/ http://RWP_host:81/view/browser/help/
    ProxyPassReverse /doc/ http://RWP_host:81/doc/
    ProxyPassReverse /html/ http://RWP_host:81/wre/common/html/
    Note: The Web addresses specified in this example must be written in the httpd.conf file exactly as specified, with the exception of the host name and optional port number.

    For the ClearCase Web interface, add these ProxyPass and ProxyPassReverse directives:

    ProxyPass /ccweb http://hostname[:port]/ccweb

    ProxyPassReverse /ccweb http://hostname[:port]/ccweb

    ProxyPass /Java_Plugins http://hostname[:port]/Java_Plugins

    ProxyPassReverse /Java_Plugins http://hostname[:port]/Java_Plugins

    The hostname is the name of the RWP server host and port is an optional port number, which you must specify if you have changed the default port on which RWP listens for HTTP requests (see To change the default RWP HTTP port). For example, the following directives would configure the proxy server to support access by the ClearCase Web interface to an RWP process listening on port 81 of a host named RWP_host.

    ProxyPass        /ccweb http://RWP_host:81/ccweb
    ProxyPassReverse /ccweb http://RWP_host:81/ccweb
    ProxyPass        /Java_Plugins http://RWP_host:81/Java_Plugins
    ProxyPassReverse /Java_Plugins http://RWP_host:81/Java_Plugins

    For the ClearQuest Web interface, add these ProxyPass and ProxyPassReverse directives:

    • For the ClearQuest Web interface, add the ProxyPass and ProxyPassReverse directives of the following form for the ccweb Web address.

      ProxyPass /wpf/ http://hostname[:port]/wpf/

      ProxyPass /px/ http://hostname[:port]/px/

      ProxyPass /images/ http://hostname[:port]/images/

      ProxyPass /dct/ http://hostname[:port]/dct/

      ProxyPass /common/ http://hostname[:port]/common/

      ProxyPass /../view/ http://hostname[:port]/view/

      ProxyPass /view/ http://hostname[:port]/view/

      ProxyPass /cqweb/ http://hostname[:port]/cqweb/

      ProxyPass /cqattachments/ http://hostname[:port]/cqattachments/

      ProxyPassReverse / http://hostname[:port]/

      The hostname is the name of the RWP server host and port is an optional port number, which you must specify if you have changes the default port on which RWP listens for HTTP requests. The following example supports proxy access by the ClearQuest Web interface to an RWP process listening on port 81 of a host named RWP_host.

    ProxyPass         /wpf/ http://RWP_host:81/wpf/
    ProxyPass        /px/ http://RWP_host:81/px/
    ProxyPass        /images/ http://RWP_host:81/images/
    ProxyPass        /dct/ http://RWP_host:81/dct/
    ProxyPass        /common/ http://RWP_host:81/common/
    ProxyPass        /../view/ http://RWP_host:81/view/
    ProxyPass        /view/  http://RWP_host:81/view/
    ProxyPass        /cqweb/ http://RWP_host:81/cqweb/
    ProxyPass        /cqattachments/ http://RWP_host:81/cqattachments/
       ProxyPassReverse / http://RWP_host:81/

    The Web addresses used by Web interfaces to IBM products may change when you install a new release of ClearCase, ClearQuest, or any other IBM products on the RWP host. To find the currently valid Web addresses for IBM products on the RWP host, examine the *.conf files in the RWP conf/include directory. The application Web addresses are embedded as arguments to Alias or JkMount directives. For example: JkMount /CQWeb/* ajp13 indicates that /CQWeb is a Web address that supports (omit the trailing /* ). Similarly: Alias /ccweb "_CC_HOME_/web" indicates that /ccweb is a Web address that RWP supports.



Feedback