Specify the distributed session cache cluster and location
To configure WebSEAL to use the distributed session cache, we must specify the distributed session cache server cluster and location in the [dsess] and [dsess-cluster] stanzas.
Gather the following information about the cluster containing the distributed session cache server:
- The IP address of the primary master.
- The IP addresses of the supplementary masters, including the secondary, tertiary, and quaternary masters (if applicable).
- The port for the distributed session cache.
Use the LMI of the primary master to view the General and Session Cache tabs of Cluster Configuration page to obtain these details. For information about the cluster configuration fields, search for "Managing cluster configuration" in the Administering web reverse proxy topics in the Knowledge Center.
Configuration entries for using the distributed session cache are located in the [dsess] and [dsess-cluster] stanzas of the WebSEAL configuration file.
- To specify the location of the distributed session cache, define a cluster name in the dsess-cluster-name entry of the [dsess] stanza. For example:
[dsess] dsess-cluster-name = dsessWe can assign any name to this cluster. This value is not set as part of the cluster configuration process.- Next, define the details for the cluster in a corresponding [dsess-cluster:<cluster-name>] stanza. Use the server entry to specify the location of the distributed session cache server in the following format: https://<IP_Address>:<Port>/DSess/services/DSess.
Where:
- <IP_Address>
- The IP address of the distributed session cache server. For example, 10.150.21.80.
- <Port>
- The port for the distributed session cache. For example, 2126.
The default parameters and values to define a cluster of distributed session cache servers are provided in the [dsess-cluster] stanza.
For architectures where more than one distributed session cache is installed in a failover configuration, create multiple instances of this configuration entry. We can specify multiple server entries for failover purposes. The complete set of these server entries defines the membership of a distributed session cache cluster.
- Specify a priority level for each distributed session cache server by including a number, 1-9, before the URL. This digit represents the priority of the server in the cluster (9 being the highest, 0 being lowest). We must assign the highest priority to the primary master, the next highest priority to the secondary master, and the following priorities to the tertiary and quaternary masters if present.
For example:
[dsess-cluster:dsess] server = 9,https://<primary_master_IP_address>:<port>/DSess/services/DSess server = 8,https://<secondary_master_IP_address>:<port>/DSess/services/DSess server = 7,https://<tertiary_master_IP_address>:<port>/DSess/services/DSess server = 6,https://<quaternary_master_IP_address>:<port>/DSess/services/DSess
When the server entry specifies the HTTPS protocol in the URL, configure WebSEAL for SSL communication with the distributed session cache. See SSL configuration for WebSEAL and the distributed session cache.
Parent topic: Distributed session cache configuration for WebSEAL