For high availability, you can set up a WebCenter Sites cluster in a WebLogic domain with a primary cluster node on one machine and one or more secondary cluster nodes on the same or different machines. The first WebCenter Sites Managed Server you create is the primary node, and any additional WebCenter Sites Managed Servers in the same domain are secondary nodes.
The following topics describe how to set up a WebCenter Sites cluster.
Now that you have installed and configured a WebCenter Sites domain with Managed Servers, set up a load balancer, run the Configurator, set up an LDAP authentication provider, and configured CAS, you can set up a cluster of WebCenter Sites Managed Servers for the domain.
Install WebCenter Sites, as Installing the Oracle WebCenter Sites Software describes, and set up a WebLogic domain with at least one WebCenter Sites Managed Server, the primary node in a cluster, as Configuring the WebCenter Sites Domain describes.
If you followed the instructions in Configuring the WebCenter Sites Domain, you would have a WebCenter Sites domain with one cluster and two Manager Servers to start setting up the cluster.
To add secondary nodes, you can clone the primary node configuration through the WebLogic Server Administration Console, as Setting Up a WebCenter Sites Cluster describes. Or you can use the Fusion Middleware Configuration Wizard to extend the WebCenter Sites domain,
Set up a web tier and load balancer, and configure the primary cluster node to use the load balancer’s IP address, as Creating a WebCenter Sites Web Tier describes.
For more information about setting up a load balancer, see "Server Load Balancing in a High Availability Environment" and "Configure Load Balancer" in the Oracle Fusion Middleware High Availability Guide
Run the WebCenter Sites Configurator, as Configuring WebCenter Sites describes.
For authentication based on an external LDAP authentication provider or Oracle Access Manager, complete this integration before scaling out for a clustered environment. You can change the default identity store to an LDAP authentication provider with Oracle Access Manager, as Switching to Authentication Against an LDAP Directory describes. You also have the option of integrating WebCenter Sites with an external LDAP directory, as Switching to Authentication Against an LDAP Directory describes.
If you want to deploy the Centeral Authentication Service (CAS) on a separate server for High Availability, set up a CAS cluster prior to WebCenter Sites cluster configuration.
If the CAS application is to reside on a cluster node other than the primary, complete the steps in Configuring the CAS Primary Cluster Node.
For a traditional, file-based cluster, set up a new shared location, containing the
wcs_properties.json file that all the different cluster nodes can point to.
Note:This step is not required for a cluster that uses the NIO database-based file system. For more information, see Moving the Shared File System to a Database.
In the WebCenter Sites shared storage directory (
sites-shared), create a directory named
Move the file
DOMAIN_HOME/wcsites/wcsites/config/wcs_properties.json to the
sites-shared/config directory. Do not copy the file.
sites.config system property on each cluster node to reference the shared directory where
wcs_properties.json now resides.
sites.configcannot used for sharedFS. For the directory sharedFS you need to create a new directory, often the directory
wcssites/wcsites/sharedis used. The configuration utility will fail when pointing the sharedFS to
Shut down all WebCenter Sites Managed Servers in the cluster.
After you create one or more WebCenter Sites cluster nodes as Managed Servers (
wcs_server2), you need to configure the nodes to set up the cluster.
80, you must also specify the port number.
yesfor HTTPS and
Note:The primary node must be registered first.
/wcsites/wcsites/configdirectory, modify the following two files:
host.properties: Update the
host.nameproperty with a valid host name for this cluster node. The
host.namevalue should be unique within the cluster.
jbossTicketCacheReplicationConfig.xml: Update the
bind_addrproperty with a valid host or IP address for this cluster node.
jbossTicketCacheReplicationConfig.xmlfiles in the
DOMAIN_HOME/wcsites/wcsites/configdirectory as follows.
ss-cache.xmlfiles to a value appropriate for your environment (typically
1). Set the
jbossTicketCacheReplicationConfig.xmlfile to a value appropriate for your environment (typically
timeToLivefield must be changed from the default value of
0if the cluster members are not all collocated on the same machine. This field must be set based on the distribution of your clustered machines, as the following table shows.
Multicast packets restricted to the same subnet.
Multicast packets restricted to the same site.
Multicast packets restricted to the same geographical region.
Multicast packets restricted to the same continent.
Note:Sometimes WebCenter Sites installation may be slow and take up to several hours because other installations may be using the same multicast port. Ensure that the ports used for this installation are different from other WebCenter Sites installations on the network. If your installation seems slow, change your multicast ports as a troubleshooting step.
multicastGroupPortvalue to a unique value greater than
2048. Ensure that the multicast port used in
jbossTicketCacheReplicationConfig.xmlis the same on each node in the cluster but is different on other clusters running on the same network
sites_server2and any additional secondary nodes, ensure that the Managed Server is shut down, do the following steps, and then go back and repeat steps 2 through 6.
sites_server2or any additional secondary node added using the Configuration Wizard (
DOMAIN_HOMEwcsites/wcsites/config.sh), copy the
configfolder from the primary node (
DOMAIN_HOMEwcsites/wcsites/configto replace the
configfolder created by the Configuration Wizard on the newly added node (
|Node name||This must be the same as the value of
|Host name||The host name or IP address of this cluster node (not the load balancer).|
|Port number||The port number of this cluster node (not the load balancer).|
|Batch Host name||The host name or IP address of the node member, which is the actual listen address of the node, and not the load balancer. In a clustered environment, only one batch host is supported. Set this property on each cluster member to point to the dedicated host.|
|Batch Port number||The batch port number, which you must specify if it is something other than
|Are you installing over a secure connection?||Set to Yes if using SSL (HTTPS); otherwise set to No.|