Does the Policy Server supports loadbalancing between 2 instances ofODBC Session Stores, which means that it can write to both ODBCSession Stores ? Or should it be configured to write only to 1 ODBCSession Store instance in failover scenario ?
On one hand, our Documentation precises that Policy Server shouldwrite to the same database, and several ODBC instances of SessionStores can be replicated.
Policy Server to Session Store Communication
If you deploy a session store, all Policy Servers in the environment must use the same session store database.
Deploying a master session store is a way to achieve session store redundancy. A master session store lets each Policy Server communicate with the closest replicated version.
>>> the diagram shows a direct link from Chicago Policy Server to>>> Chicago Session Store replica, not to the Master. The Boston>>> Policy Server goes to the Boston Replica.
On the other hand, our Documentation about configuring the OracleDatabase driver for failover allows writes to more than 1 SessionStore.
Configure the Oracle Wire Protocol Driver for Oracle RAC without SCAN
If the primary server is not accepting connections, specifies the connection failover to the other Oracle nodes.
Turns on client load balancing, which helps to distribute new connections to keep RAC nodes from being overwhelmed with connection requests. When enabled, the order in which primary and alternate database servers are accessed is random.
So said, Policy Server does support the fail over configurationbetween multiple instances of ODBC Session Stores, which can beconfigured from SiteMinder Management console.
Please note that replication should be configured between themultiple instances of ODBC Session Stores to achieve Single Sign-Onin case of fail over.
Load Balancing with multiple instances of ODBC Session Stores arenot tested internally with in the Database Source Name (DSN).
If you deploy a session store, we recommend to have all PolicyServers in the environment to use the same session store database.
To configure Session Store high availability, follow one of the wayslisted that suits the organization requirement.
A centralized replicated session store to enable single sign–on between all applications as documented athttps://docops.ca.com/ca-single-sign-on/12-8/en/implementing/implementing-ca-single-sign-on/multiple-data-centers/
A master session store lets each Policy Server communicate with the closest replicated version as documented athttps://docops.ca.com/ca-single-sign-on/12-8/en/implementing/implementing-ca-single-sign-on/architectural-use-cases/
KB : KB000130537