Table of Contents

Search

  1. Preface
  2. Introduction to High Availability
  3. Set Up the High Availability Environment
  4. Configure JMS Discovery
  5. Configure RMI Connections
  6. Configure the Operation Console
  7. Configure an HTTP Load Balancer
  8. Configure the Dashboard and Reports
  9. Appendix A: Troubleshooting High Availability
  10. Appendix B: High Availability Log Messages
  11. Appendix C: Port Number Reference
  12. Appendix D: Glossary

High Availability Guide

High Availability Guide

Configuring Apache HTTP Server for Sticky Sessions

Configuring Apache HTTP Server for Sticky Sessions

To configure the Apache HTTP Server for sticky sessions, you need to make changes in the cluster configuration.
  1. Include cluster configuration. Edit the file
    <apache installation>/conf/httpd.conf
    and add
    Include conf/dx-gui-cluster.conf
    at the end.
    This Apache directive indicates that an additional configuration file must to be loaded.
  2. Add the cluster configuration. Create a file called
    dx-gui-cluster.conf
    under
    <apache installation>/conf
    / and copy the following code section into it:
    ## Load the proxy module, if is not loaded already <IfModule !proxy_module> LoadModule proxy_module modules/mod_proxy.so </IfModule> ## Load the http proxy protocol module, if it is not loaded already ## This module enables load balancing between nodes <IfModule !proxy_http_module> LoadModule proxy_http_module modules/mod_proxy_http.so </IfModule> ## Load the proxy balancer module, if it is not loaded already ## This module enables load balancing between nodes <IfModule !proxy_balancer_module> LoadModule proxy_balancer_module modules/mod_proxy_balancer.so </IfModule> ## Load the ajp proxy protocol module, if it is not loaded already ## This module enables the communication between Apache and Tomcat via AJP <IfModule !proxy_ajp_module> LoadModule proxy_ajp_module modules/mod_proxy_ajp.so </IfModule> ## Add an additional location to access the current load balancing configuration ## and statistics. Access is only allowed from localhost ## Only set the location if status module (mod_status) is loaded <IfModule status_module> <Location /balancer-manager> SetHandler balancer-manager Order Deny,Allow Deny from all Allow from 127.0.0.1 </Location> </IfModule> ## Configure the ‘proxy’ for the
    Data Integration Hub
    Operation Console instances ## Note that this is a static list, all the machines should be explicitly listed here ## The value for the attribute ‘route’ must exactly match that which is ## used when configuring Tomcat <Proxy balancer://dx-gui-cluster> BalancerMember ajp://tomcat-a:18009 route=dxTomcat-A BalancerMember ajp://tomcat-b:18009 route=dxTomcat-B </Proxy> # Disable ProxyRequest as only the ProxyPass and ProxyPassReverse are used. # This prevents the server from processing requests from spammers (sending e-mails) ProxyRequests Off ## Configure the forwarding of the request. ## Client browser must connect to <apache http server>:<port>/
    dih
    -console/ ## Note that it must be a single line ProxyPass /
    dih
    -console/ balancer://dx-gui-cluster/
    dih
    -console/ stickysession=JSESSIONID|jsessionid ## Configure the return route from back-end to front ProxyPassReverse /
    dih
    -console/ balancer://dx-gui-cluster/
    dih
    -console/
    The URLs in the
    ProxyPass
    and
    ProxyPassReverse
    directives must end with a slash. If the slash is missing, routing a message to and from the back-end nodes might fail.
  3. Edit the cluster configuration. In the file that you created, edit the copied code segment as follows:
    • Delete the two lines beginning with
      BalancerMember
      . You can find them between the lines
      <Proxy balancer://dx-gui-cluster>
      and
      </Proxy>
      .
    • Insert lines, one for each Operation Console (Tomcat) server that is part of your cluster. Each line must have fields for a specific node (Tomcat instance), the machine name, and the
      jvmRoute
      value set for that specific Tomcat instance, for example,
      Balancer-Member ajp://<operation console machine name>:18009 route=<jvmRoute value as defined in web.xml>
  4. Enable load balancer status monitoring. In the file
    <apache installation>/conf/httpd.conf
    , remove the comment indicator before the following line:
    LoadModule status_module modules/mod_status.so
    and restart the Apache HTTP Server.

0 COMMENTS

We’d like to hear from you!