Configuring application clusters
For a medium or large sized deployment, an administrator deploys multiple instances of the TrueSight Automation Console application server component and creates an application cluster. You must configure a cluster of application servers to replicate information, so if one fails, other members of the cluster have access to the same information.
You can use any proxy solution to configure application clusters. This topic provides instructions on how to share data in a TrueSight Automation Console (on-premises) application cluster using the High Availability Proxy (HA Proxy) solution.
Configuring an application cluster using HA Proxy
On a host where the Automation Console application is not installed, run the following command to install HA Proxy.
yum install haproxy
A configuration file, haproxy.cfg gets created in the /etc/haproxy directory.
Navigate to the /etc/haproxy directory and replace the content in the default haproxy.cfg file with the following content.
Open the file in a text editor, and locate the
frontend localnodes
section and replace<portNumber>
with the secure port used to access the Automation Console application.Examplefrontend localnodes bind *:10443 mode tcp default_backend http_1
At the end of the file, replace
<IPAddress_hostA>/<FQDN_hostA>
with the Fully Qualified Domain Name or IP Address of the application server host and port number with the secure port used to access Automation Console application.
Increase the number of entries based on the number of applications you have installed. For example, if you have four instances of application, add four server counter entries.Note
You must specify the same port number for all the application servers.
- Save changes and run the
service haproxy restart
command to restart the HA Proxy service.
Comments
Are these steps validated by Product Development team?
There is an defect around this #DRSMP-4658
Hi Satish,
Yes, they are, however, let me check and update the docs.
Thank you for your feedback on the documentation. We have entered the following internal tracking ID for this (DRSMP-6213) and will address your query as soon as possible.
Log in or register to comment.