Follow the steps in Section 4.1, Changing Configuration Options for the Filr Appliance.
You can modify the following configuration options:
Enable Clustered Environment: Select this option to enable clustering.
JVM Route: If you plan to use Apache as the reverse proxy, add a JVM route for each filr Appliance in the Cluster. Otherwise, you can leave the JVM Route field empty. The purpose of this field is to uniquely identify each Filr Appliance to Apache.
In the field, specify worker1. On the second Filr node, in the field, specify worker2, and so forth for each Filr node, incrementing the JVM Route setting. Each Tomcat instance should have a unique JVM Route setting.
worker1, worker2, and so forth are the default names for the matching values used for the reverse proxy configuration. For example, if you have set up Apache or IIS as a reverse proxy, these are the default values. The setting in the Filr installer must match these values.
For information about how to configure Apache as a load balancer, see Section A.0, Configuring Apache as a Load Balancer.
Hibernate Caching Provider: is the only option available when configuring Filr in a clustered environment.
For more information about Memcache caching, see Memcached.
Server Addresses: Each Filr server in the cluster must list all of the Filr servers in the cluster, with each server separated by a space. The default port for memcached is 11211. For example, ipaddress1:11211 ipaddress2:11211 ipaddress3:11211
The server addresses listed here are all nodes within the Filr cluster. Changes made to one Filr node are immediately visible in other Filr nodes. Ensure that all Filr appliances in the cluster are pointing to the same NTP time source. Failure to do so can significantly degrade overall system performance.
Click for your changes to take effect.
NOTE:This stops and restarts your Filr server. As this results in server downtime, you should restart the server at off-peak hours.