This functionality can replace a load balancer appliance between the PingAccess engine nodes and the target servers, allowing for a simpler network architecture.

Available load balancing strategies:

The header-based strategy requires incoming requests to include a header that defines the target to select from the Site configuration. This load balancing strategy allows fall back if the requested target is unavailable or if the header is missing from the request.
The round-robin strategy has a sticky session option that permits a browser session to be pinned to a persistent backend target. This strategy works in conjunction with the availability profile to select a target based on its availability. The load balancer will not select a target that is in a failed state.

If you specify multiple target servers for a site but don't apply a load balancing strategy, PingAccess uses the first target server in the list until it fails. Secondary target servers are only used if the first target server is not available. PingAccess uses the Failed Retry Timeout value from the site's availability profile settings to determine when to mark the first target server as available again.