Enabling Stateless Load Balancing

It is recommended that Stateless Load Balancing be configured only for scenarios in which a single session will serve a very high volume of requests, possibly over an extended period of time. For example, in an integration scenario a third-party system or Cloud service might use a single session to continuously invoke orchestrations. Without Stateless Load Balancing, the single session is authenticated to only one AIS server, and fail-over or high-volume transactions are not easily supported. However, with Stateless Load Balancing, the single session is authenticated to a group of AIS (and HTML) servers, allowing them to scale out for high volume and fault tolerance.