This topic describes how to install a separate cache server for use by application server
nodes in a cluster. To install the cache server, you use the same Linux package that you
use to install an application server. If your installation uses a single application
node, the installation will not enable the cache services; instead, the installation
will use the local cache installed with the application server. When you have a
multi-node configuration, use the following steps to set up cache services in the
cluster.
To install a cache server:
- Install the application as described in the (installation documentation).
- Because the cache server machine's only function will be operating as a cache
server, shut down the services you won't need on a cache
server:
On Linux
/etc/init.d/jive-httpd stop
/etc/init.d/jive-httpd deactivate
/etc/init.d/jive-application stop
/etc/init.d/jive-application deactivate
- Configure the cache server with its address.
You can either edit
/etc/jive/conf/cache.conf and add the CACHE_ADDRESSES line or export the
variable.
CAUTION:
If you're setting up more than one cache server machine, you must use three or
more. The CACHE_ADDRESSES value should list them in a comma-separated list.
Using only two cache servers is not supported and can cause data loss.
- Register and start the caching service with a command as shown
below:
On Linux
/etc/init.d/jive-cache activate
/etc/init.d/jive-cache start
As the cache service starts it will:
- Write the CACHE_ADDRESSES value to the cache configuration file located
in /etc/jive/conf/cache.conf.
- Run the cache configuration script located in
$JIVE_HOME/sbin/configure-cache.
- Generate cluster.xml.
- Generate server.properties.
- Generate stores.xml.
- Start the cache service.
The cache service writes several log files to $JIVE_HOME/var/logs/.
These are:
- cache.log -- Output from the cache processes, showing start flags,
restarts, and general errors.
- cache-gc.log -- Output from garbage collection of the cache
process.
- cache-service.log -- Output from the cache service watchdog daemon,
which restarts the cache service as needed and logs interruptions in
service.
- If you haven't already, set up your application cluster to use the cache server
address you specified here.