5.13.2 Using a Load Balancer

Once the servers are clustered, you can configure a load balancer in front of your MSS instances for high availability. Use these values:

  • Load balancing algorithm: Least Connections (or something similar)

  • Session persistence: Enabled - use the existing JSESSIONID cookie. See the NOTE for additional configuration, as needed.

    NOTE:Be sure to use the required persistence settings for your environment.

    • Basic load balancing setup: Use the existing JSESSIONID cookie.

    • When using Single Sign-on through IIS: The MSS load balancer must also use the sessid URL parameter for persistence — in addition to the JSESSIONID cookie.

    • When using the Assigned Sessions list to launch new sessions: The MSS load balancer needs to stick first on the SESSIONID and then the JSESSIONID — in that specific order.

      Access to the Assigned Sessions list must be through the same MSS load balancer that the client, such as an HACloud session server, uses to connect to MSS.

    • When using both Single Sign-on through IIS — AND — the Assigned Sessions list, use the sessid URL parameter, set the MSS load balancer to stick first on the SESSIONID and then the JSESSIONID, as noted above.

  • Health check endpoint: https://<mss-server>/mss/

  • TLS: Configure TLS and install certificates as needed.

If you are using Host Access for the Cloud, see the product documentation for additional information about deploying MSS for high availability.

Related topics