Is Load Balancer Health Check Required for a Highly Available Single Site, Multi-Machine ArcGIS Server?

2615
12
Jump to solution
07-21-2021 03:39 PM
BenjaminBlackshear
New Contributor III

I have deployed ArcGIS enterprise 10.8.1 and configured it for high availability. Everything is working well so far.

Machine 1 is running portal (primary), server, data store (primary), and 2 web adapters (portal and server)
Machine 2 is running portal (secondary), server, data store (secondary), and 2 web adapters (portal and server)
The two ArcGIS Server installations have been joined and are operating as one site which is federated with the portal using the load balancer url.

In the load balancer (KEMP), currently we only have heath checks configured for the portal machines, is it necessary to configure them for the server machines as well? It is clear from the documentation that this is required for the portals but I cant tell if we need it for the servers or not. I can understand why this would be necessary if the machines were separate sites but does the health check provide any advantage or additional functionality in this case with a single site?

0 Kudos
12 Replies
SaurabhUpadhyaya
Occasional Contributor

Thanks @DavidHoy. for explanation. 

I am using web adapter(ArcGIS) for both servers, and it is linked to load balancer(https://sla.com/arcgis). Now the requirement is to add Portal in same environment to take the portal benefits. As per my understanding load balancer of ArcGIS Server can be federate with Portal. Services URL(https://sla.com/arcgis) will be load balancer url and Administration URL (https://sla.com/arcgis) and user name password will be primary site administrator url @DavidHoy can you please verify my approach if required any changed please suggest proposed_arch.png

 

....reference esri url (https://enterprise.arcgis.com/en/portal/latest/administer/linux/federate-an-arcgis-server-site-with-...)

0 Kudos
DavidHoy
Esri Contributor

@SaurabhUpadhyaya wrote:

Thanks @DavidHoy. for explanation. 

I am using web adapter(ArcGIS) for both servers, and it is linked to load balancer(https://sla.com/arcgis). Now the requirement is to add Portal in same environment to take the portal benefits. As per my understanding load balancer of ArcGIS Server can be federate with Portal. Services URL(https://sla.com/arcgis) will be load balancer url and Administration URL (https://sla.com/arcgis) and user name password will be primary site administrator url @DavidHoy can you please verify my approach if required any changed please suggest proposed_arch.png

 

....reference esri url (https://enterprise.arcgis.com/en/portal/latest/administer/linux/federate-an-arcgis-server-site-with-...)



@SaurabhUpadhyaya wrote:

Thanks @DavidHoy. for explanation. 

I am using web adapter(ArcGIS) for both servers, and it is linked to load balancer(https://sla.com/arcgis). Now the requirement is to add Portal in same environment to take the portal benefits. As per my understanding load balancer of ArcGIS Server can be federate with Portal. Services URL(https://sla.com/arcgis) will be load balancer url and Administration URL (https://sla.com/arcgis) and user name password will be primary site administrator url @DavidHoy can you please verify my approach if required any changed please suggest proposed_arch.png

 

....reference esri url (https://enterprise.arcgis.com/en/portal/latest/administer/linux/federate-an-arcgis-server-site-with-...)


Sorry I have been away from my desk for a few days.
You diagram is not quite correct:  It is a common misunderstanding that the Server is "behind" the Portal, this is not the case.
The endpoint for your Portal and your ArcGIS Server site is the Load Balancer. All calls from the clients go to the Load Balancer and are then distributed as required either to the Portal or the AGS machines.
The federation between Portal and Server site also uses the Load Balancer path. You have described this correctly in your text.
The Portal communicates with the Server site via the <LB>/arcgis and the Servers communicate with the Portal via the <LB>/portal. (This should happen automatically when you make the federation - this is why the Portal needs to have its webContextURL property set correctly to the LB/portal address before you federate) - you can check in the AGS site's server/admin/security/config page after federation - it should show both a "portalURL" and "privatePortalUrl" with the LB/portal address.

Here is an altered diagram.
I have added a fileshare because I presume you must have always had this for shared Server Config and System Directories to make your 2 machine ArcGIS Server site work in the past.
I also drew in an ArcGIS Data Store - you haven't mentioned this, and it is not 100% required, but to take full advantage of ArcGIS Enterprise, you will need to establish at least a Relational Data Store and register it with your Server Site to allow it to act as a "Hosting Server" to hold system managed data created by Portal Users.

Simple_Architecture.jpg

SaurabhUpadhyaya
Occasional Contributor

Thanks @DavidHoy 

0 Kudos