Configure Session Persistence
If you created a domain with Oracle WebLogic Server for OCI, and your web applications require session persistence, you can update the load balancer for the domain.
Session persistence is a method to direct all requests originating from a single
logical client to a single backend server. By default, session persistence is
enabled on the load balancer with the Enable load balancer cookie
persistence
option, but you can update the load balancer after creating
a domain.
Oracle Cloud Infrastructure Load Balancing supports two types of session persistence (stickiness):
- Application cookie persistence - The load balancer activates session persistence when a backend server sends a
Set-Cookie
response header containing a recognized cookie name. - Load balancer cookie persistence - The load balancer inserts a cookie into the response, which enables session persistence. This method is useful when you have applications that cannot generate their own cookies.
To configure session persistence:
See these topics in the Oracle Cloud Infrastructure documentation:
Enable Session Affinity or Sticky Sessions
If you have clustered JMS resources and you access it by using an external client through a load balancer by rmi-tunneling, then you need to enable session affinity or sticky sessions.
- Access the WebLogic console of the clone instance. See Access the WebLogic Console.
- Under Domain Structure, expand Environment > Clusters, and then click Cluster-1.
- In the right pane, change the Default Load Algorithm property to
RoundRobinAffinity
. - Click Save.
- Restart the WebLogic Server instances.