Reconfigure an RPA server to use an external load balancer

Topic

• Product version: 21.4 and higher
• Components: Other

Instructions

If the customer is asking to reconfigure our HA solution to use an external load balancer instead of our internal balancing solution, here is what is required (on version 21.4 and newer):

On the load balancer side:

1. Sticky sessions by source IP are required to make everything work properly

2. In the case of SSL configuration, we are demanding to terminate SSL on our side and not on the LB

3. Balancing should be performed on the HTTP level, not TCP

On the RPA server side:

1. Stop all services on both nodes

2. Open \Kryon\installer-assets\config\prod\scripts\config.prod.properties.json

   • ​​​​​​​For 21.4 and 22.3:
     Change "KEYCLOAK_HOST" and "SERVERS_FQDNS" to FQDN of the load balancer

   • For 22.9:
     Change "LB_FQDN" to FQDN of the load balancer, "SERVER_FQDNS" to FQDN of the current server
     Run configureall to apply changes

3. Open \Kryon\IDP\Aerobase\Configuration\overrides.rb

   • Change value of external_url to FQDN of the load balancer

   • Run aerobase-ctl reconfigure to apply changes

4. Connect to the database and edit Leoservers table so it contains only FQDN of the load balancer

5. Change configuration of Admin

   • Open \Kryon\Services\Kryon Admin Client 64bit\Config\appSettings.config

   • Set values of IdpHost, IdpDomainAdres, Host, appServer to FQDN of the load balancer

6. Edit \Kryon\Console\Web\ConsoleX\assets\data\appConfig.prod.json

   • ​​​​​​​Set values of “apiUrl”, "url" under “keycloak” section (~line 182) to FQDN of the load balancer

   • Check that “seqUrl” is pointing to proper FQDN

7. Restart all services.
    

If you have a deployment with SSO, then a new keytab with Load Balancer FQDN should be issued, and the respective SPN is set.

If you have a deployment with SSL, then the certificate must include LB URL in SAN.