SESSION AFFINITY QUESTIONS (Doc ID 1076512.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Utilities Customer Care and Billing - Version: 1.5.20.2 and later   [Release: 1.5 and later ]
Oracle Enterprise Taxation Management - Version: 2.1.5.1 and later    [Release: 2.1 and later]
Information in this document applies to any platform.

Goal

It appears that the ETM Web application generates a session object for a session. The result of generating a session object (as it is called in WebSphere at least) is Session Affinity. The result of Session Affinity is that all requests for the duration of a session will be handled by one and the same applicationserver instance in the applicationserver cluster. This behaviour is somehow contradictory to ETM being a stateless application.

The questions are:
- why the session object is generated,
- for what is it used, and is its use mandatory for the validity/consistency of the session,
- what would be the impact if we break the session affinity, so requests for one session would be handled by any applicationserver instance in the cluster (thus optimizing balancing)?


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms