You can set up a Central Authentication Server (CAS) cluster in the same WebLogic domain as Oracle WebCenter Sites, in a different WebLogic domain on the same machine, or for high availability, in a different WebLogic domain on a different machine.
The following topics describe how to set up a CAS cluster:
Parent topic: Configuring WebCenter Sites Components
This topic describes how to set up the CAS application to function on a WebCenter Sites cluster both as a single instance and as a clustered application. If you are not clustering the CAS application, you can skip the steps required specifically for clustering CAS.
An instance of WebCenter Sites with CAS, the primary cluster node, needs to be up and running.
Never change the context root of the CAS application from its default value of /cas
, even if the CAS application itself is relocated.
This topic describes how to set up one or more secondary CAS (Central Authentication Service) application cluster nodes.
After you have configured and tested all the secondary CAS cluster nodes, start the primary and all secondary CAS cluster nodes, and, optionally, restart the load balancer. Then log in to the WebCenter Sites Admin interface to confirm that the CAS cluster has been successfully configured.
Note:
If the cluster members are not all colocated in a Weblogic domain on the same machine, thetimeToLive
field must be changed from the default value of 0
. Set the timeToLive
field based on the distribution of your clustered machines. A list of possible settings follows:
|
Multicast packets restricted to the same subnet (suggested cluster value if distribution unknown) |
|
Multicast packets restricted to the same site |
|
Multicast packets restricted to the same region |
|
Multicast packets restricted to the same continent |
|
Multicast packets unrestricted |