We are using an Open Source solution for Loadbalancing: HA Proxy and don't know how to configure this and make it work. For SmartIT, check 000173915 |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. PREREQUIRED RSSO NEEDS TO BE INSTALLED AND CONFIGURED FOR DWP, THIS WILL MAKE SESSION FAIL OVER WORK. Load balancing with the sticky option applies on both F5 and HA Proxy, insert cookie option needs to be in place. Need to have a rule to rewrite http to https. The "sticky" or "persistence" option ensures that a single client gets the same real AR System server for each interaction with the load balancer. This is a requirement for AR System because:
SEE KA 000026873
NOTES:
https://www.haproxy.com/blog/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know
Whether your have HA Proxy or not (F5 in place), make sure you perform below steps for Jetty and Tomcat: We are assuming you already know how to configure Tomcat clustering and session persistence on Tomcat.
https://tomcat.apache.org/tomcat-8.5-doc/cluster-howto.html
https://wiki.eclipse.org/Jetty/Tutorial/Session_Clustering
distributable="true"
HA Proxy config files are attached to this KA. You could use as a Protocol, but our recommendation is to use HTTP protocol for this purpose.
vi /etc/haproxy/haproxy.cfg -- to update the configuration
sudo service haproxy restart -- to restart the service sudo service haproxy status -l -- to make sure service is running properly
|