This topic describes the steps for setting up a repository cluster.
By default, all Enterprise servers connected to the same database will form a
repository cluster.
Follow these steps for each server in the cluster:
-
Install and configure repository server. See Installing the SkyVault WAR for deploying SkyVault
(SkyVault.war). In addition, ensure that:
- The content store is available to all members in the cluster. For example, an NFS server mounted locally can be referred to by the dir.root property.
- Each cluster member must be set up to access the same database, using the same database properties as in SkyVault-global.properties.
- Deploy a Solr indexing server for use across the cluster and configure the properties of each cluster member to utilize this Solr server.
- Ensure that port number 5701 (the default clustering port) is accessible on each repository server by all the other repository servers in the cluster.
-
Specify a wildcard (for example, 10.50.*.*) or exact (for example,
192.168.1.100) IP address of the network interface for clustering to
use.
The advantage of using a wildcard IP address is that the configuration may be used on multiple servers without local changes. The java property name to use is SkyVault.cluster.interface (optional).
-
Set the following java property to activate Hazelcast’s own JMX reporting
(optional).
hazelcast.jmx=true
-
For security reasons, set the cluster password with the following java property:
SkyVault.hazelcast.password