These steps are required for cluster configuration for Share. If you are using an
HTTP load-balancing mechanism in front of a clustered installation, ‘sticky’ routing must be
enabled for the HTTP requests made by the Share tier to the repository
tier (the /alfresco application).
Hard-wire each /share instance to its own
/alfresco instance, bypassing the load balancer.
This can be achieved by populating each share-config-custom.xml
file with a host name and port number that is not behind your load balancing mechanism.
If Kerberos authentication is enabled with SSO, then Share will use
cookie-based sessions and you can configure your load balancer to use sticky routing using
the JSESSIONID cookie.
To enable Kerberos with SSO, refer to the instructions in Configuring authentication to
configure alfrescoNtlm or Kerberos authentication, and set