E1: AIS: ORCH: Stateless Load Balancing for AIS Single Token - Starting Tools Release 9.2.5.2 (Doc ID 2751113.1)

Last updated on AUGUST 02, 2024

Applies to:

Goal

Currently, an established session can only be used by the AIS server that the session was established on.
The load balancer relies on configured session affinity to route the request to the same server every time that an established session is used.
Sessions are retrieved using the AIS Token created on the original AIS server (represented by ‘T’ below).

The Stateless Load Balancing feature in AIS allows AIS servers to share sessions across multiple load balanced AIS Server instances.
With Stateless Load Balancing, sessions are propagated across all participating nodes in the cluster.
The same AIS Token is used to retrieve the sessions on any of the participating nodes. Cookies or other mechanisms that provide sessions affinity must not be used or configured so the load balancer can balance requests across all available nodes.
Since the session is already established and managed, there is no need to authenticate the user on each request, this improves the performance of each call (versus traditional stateless calls using credentials every time).

With Stateless Load Balancing, each of the AIS server will have it's own backend JAS server to handle the load.

When a stateless LB session is propagated, the other participating AIS servers, create their own AIS session and also establish an associated new JAS session on their associated JAS server. JWT is used for this purpose.  
Here is a representation of the sessions present on the servers, after a couple tokens are requested: 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.