Revision as of 20:31, November 9, 2016 by Sschlich (talk | contribs) (loadbalancer_tenantN.conf)
Jump to: navigation, search

Load Balancing Multi-tenant

ENTIRE PAGE IS NEW

See Also: Load Balancing Single Tenant

Setting up the Load Balancer in a Multi-tenant Environment

Please note that any URL setup for the various GIR components described in the Multi-Tenant Deployment should now point to the respective loadbalancer URLs, e.g.

RP url : <loadbalancer URL> t1/rp/api 
      / 
htcc.baseurl should point to the RWS loadbalancer url: <loadbalancer URL>/t1 
rcs.base_uri should point to <loadbalancer URL>/t1/rcs 
Important
Only GIR releases post-8.5.210.02 with WDE support multi-tenancy.

Follow the instructions on this page and for each tenant create a separate/etc/httpd/conf.d/loadbalancer_tenantN.conf file.

In addition, provide each tenant with a separate balancer rule, ProxyPass and the following URI conventions:

  • Interaction Recording Web Services
  • http://loadbalancer/t1/api
  • http://loadbalancer/t1/internal-api
  • Recording Processor
  • http://loadbalancer/t1/rp
  • Recording Crypto Server
  • http://loadbalancer/t1/rcs
  • Interaction Receiver
  • http://loadbalancer/t1/interactionreceiver
  • WebDAV Server
  • http://loadbalancer/t1/webdav

On both servers, create the following files:

  • Create /etc/httpd/conf.d/serverstatus.conf and add the following text:

<Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from 127.0.0.1 </Location>

  • For each tenant, create /etc/httpd/conf.d/loadbalancer_tenantN.conf, and add the following text:

Important If your existing configuration already includes the loadbalancer rules in the /etc/httpd/conf/httpd.conf, skip this step.

The following lines starting with BalancerMember refer to the URL to the servers for Interaction Recording Web Services, Recording Processor, Recording Crypto Server, Interaction Receiver, and WebDAV server.

Provide each tenant with a separate balancer rule, ProxyPass and the following URI conventions:

loadbalancer_tenantN.conf
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED <br>
 # Interaction Recording Web Services for tenant 1 <Proxy balancer://t1rws> BalancerMember http://t1rws1:8080  route=T1RWS1 BalancerMember http://t1rws2:8080 route=T1RWS2 BalancerMember http://t1rws3:8080  route=T1RWS3 ProxySet stickysession=ROUTEID </Proxy> ProxyPass /t1/api balancer://t1rws/api ProxyPass /t1/internal-api balancer://t1rws/internal-api <br>
 # RP for tenant 1 <Proxy balancer://t1rp> BalancerMember http://t1rp1:8889 BalancerMember http://t1rp2:8889 </Proxy> ProxyPass /t1/rp/api balancer://t1rp/api <br>
 # RCS for tenant 1 <Proxy balancer://t1rcs> BalancerMember http://t1rcs1:8008 connectiontimeout=10000ms route=T1RCS1 BalancerMember http://t1rcs2:8008 connectiontimeout=10000ms route=T1RCS2 </Proxy> ProxyPass /t1/rcs balancer://t1rcs/rcs stickysession=JSESSIONID ProxyPassReverseCookiePath "/rcs" "/t1/rcs" <br>
 # Interaction Receiver for tenant 1 <Proxy balancer://t1sm> BalancerMember http://t1ir1 BalancerMember http://t1ir2 </Proxy> ProxyPass /t1/interactionreceiver balancer://t1sm/interactionreceiver <br>
 # WebDAV for tenant 1 <Proxy balancer://t1webdav> BalancerMember http://t1webdav1 BalancerMember http://t1webdav2 status=H </Proxy> ProxyPass /t1/webdav/recordings balancer://t1webdav/recordings ProxyPass /t1/webdav/dest2 balancer://t1webdav/dest2<br>
Comments or questions about this documentation? Contact us for support!