Configure Apache HTTP Server version 2.2 or 2.4 using mod_proxy

This topic provides instructions on how to configure an external Web server on both Windows and Linux systems.

Configure Apache HTTP Server version 2.2 or 2.4 on a Windows system

To configure Apache HTTP Server version 2.2 or 2.4 using mod_proxy on a Windows system:

  1. Download and install the Apache HTTP Server version 2.2 or 2.4 from the Apache HTTP Server Project web site.

    Note: Make sure that you use the MSI installer that includes OpenSSL.

  2. Navigate to C:\Program Files\Apache Group\Apache\conf and open the Apache server configuration file httpd.conf in a text editor.

  3. In the httpd.conf file, uncomment the following lines:

    LoadModule proxy_module modules/mod_proxy.so 
    LoadModule proxy_balancer_module modules/mod_proxy_ balancer.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_http_module modules/mod_ssl.so
  4. Add the following line to the httpd.conf file:

    Include conf/extra/reverse_proxy.conf
  5. Save and close the httpd.conf file.

  6. Configure SSL for your Apache web server. (For information, see Configure Apache HTTP Server Version 2.2 Using mod_jk (IPv4 Only).)

  7. Use the following template to create a file named reverse_proxy.conf.

    Note:  

    • Make sure that your reverse_proxy.conf correctly conforms to this format. In each directive section, list each node with IP, PORT, and the respective KINTANA_SERVER_NAME.

    • Make sure that you use EXTERNAL_WEB_PORT to connect to a load balancer or web server and use EXTERNAL_WEB_PROTOCOL to specify the protocol. For details, see Server parameters.

    For example, for a two-node cluster:

    ProxyPass /itg balancer://itg stickysession=JSESSIONID|jsessionid nofailover=Off
    ProxyPassReverse /itg balancer://itg
    ProxyPass /dashboard balancer://dashboard stickysession=JSESSIONID|jsessionid nofailover=Off
    ProxyPassReverse /dashboard balancer://dashboard
    ProxyPassReverse/itg http://<Proxy_Server_IP_Address>/itg
    ProxyPassReverse/dashboard http://<Proxy_Server_IP_Address>/dashboard
    <Proxy balancer://itg>
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    </Proxy>
    <Proxy balancer://dashboard>
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    </Proxy>
    ProxyPreserveHost on
  8. Restart the Apache web server.

  9. Check your PPM Center server.conf file to make sure that all of your base URLs are of the following type:

    http(s)://<Reverse_Proxy_Server_IP_Address>/

Back to top

Configure Apache HTTP Server version 2.2 or 2.4 on a Linux system

To configure Apache HTTP Server version 2.2 or 2.4 using mod_proxy on a Linux system:

  1. Download and install the Apache HTTP Server Version 2.2 or 2.4 from the Apache HTTP Server Project web site.

  2. Download the httpd-2.2.xx.tar.gz or httpd-2.4.xx.tar.gz UNIX source file.

  3. Run the following commands:

    $ gzip -d httpd-NN.tar.gz
    $ tar xvf httpd-NN.tar
    ./configure --prefix=/etc/httpd-NN --enable-proxy --enable-proxy-http --enable-proxy-balancer --enable-ssl -enable-so
    make
    make install
  4. Configure SSL for your Apache web server. (For information, see Configure Apache HTTP Server Version 2.2 Using mod_jk (IPv4 Only).)

  5. Open the httpd.conf file in a text editor.

    To find the Apache installation directory and print the httpd.conf file location, run # httpd -v.

  6. Add the following line to the httpd.conf file:

    Include conf/extra/reverse_proxy.conf
  7. Use the following template to create a file named reverse_proxy.conf.

    Note:  

    • Make sure that your reverse_proxy.conf correctly conforms to this format. In each directive section, list each node with IP, PORT, and the respective KINTANA_SERVER_NAME.

    • Make sure that you use EXTERNAL_WEB_PORT to connect to a load balancer or web server and use EXTERNAL_WEB_PROTOCOL to specify the protocol. For details, see Server parameters.

    For example, for a two-node cluster:

    ProxyPass /itg balancer://itg stickysession=JSESSIONID|jsessionid nofailover=Off
    ProxyPassReverse /itg balancer://itg
    ProxyPass /dashboard balancer://dashboard stickysession=JSESSIONID|jsessionid nofailover=Off
    ProxyPassReverse /dashboard balancer://dashboard
    ProxyPassReverse/itg http://<Proxy_Server_IP_Address>/itg
    ProxyPassReverse/dashboard http://<Proxy_Server_IP_Address>/dashboard
    <Proxy balancer://itg>
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    </Proxy>
    <Proxy balancer://dashboard>
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    BalancerMember http://<PPM_SERVER_IP_ADDRESS:EXTERNAL_WEB_PORT>/itg route=KINTANA_SERVER_NAME
    </Proxy>
    ProxyPreserveHost on
  8. Restart the Apache web server.

  9. Check your PPM Center server.conf file to make sure that all of your base URLs are of the following type:

    http(s)://<Reverse_Proxy_Server_IP_Address>/

Back to top