13 Setting Up a CAS Cluster
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:
Configuring the CAS Primary Cluster Node
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.
Configuring the CAS Secondary Cluster Node(s)
This topic describes how to set up one or more secondary CAS (Central Authentication Service) application cluster nodes.
- Create a Managed Server for each secondary CAS cluster node and assign it to the WebLogic cluster containing the primary CAS cluster node.
- Shut down all CAS Managed Servers.
- Create a CAS
config
directory (CAS_CONFIG_DIR
) on the new Managed Server; for example,DOMAIN_HOME/wcsites/cas/config
. - Copy the contents of the
CAS_CONFIG_DIR
directory from the primary CAS Managed Server to the new Managed Server, the secondary cluster node. - Set the
host.name
parameter value inCAS_CONFIG_DIR/cas.properties
to the host name or IP address of this secondary cluster node. - (Optional) Update the
CAS_CONFIG_DIR/ticket-cache.xml
file. If you are clustering the CAS application, setip_ttl
to a value appropriate for your environment. Oracle recommends1
as a starting point. See Setting Up a WebCenter Sites Cluster for a list of suggested values. - Start the load balancer, if it is not already running.
- Start the new Managed Server.
- Log in to the WebCenter Sites Admin interface to ensure that the new server is functional.
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, the timeToLive
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 |