The caching system is optimized for use in a clustered installation, where you set up and configure a separate external cache server.
Use the same Linux package that you used to install the application servers to install a separate cache server that application servers can use in a cluster.
If your installation uses a single application node, the installation does not enable the cache services; instead, the installation uses the local cache installed within the application server. When you have a multi-node configuration, follow through this article which provides the steps in configuring the cache server in the cluster.
- Install the Jive RPM file (the same RPM file used during the Jive package installation and starting up)
- Because the cache server machine's only function is operating as a cache server, only enable the cache service. To do this, type the following as jive user:
jive enable cache
Note: If you're logged in as root, you can use
su - jiveto become the jive user.
- Configure the cache server with its address.
- Register and start the caching service by using the following commands:
jive set cache.hostnames hostname
The cache service writes several log files to
$JIVE_HOME/var/logs/. These are:
cache-service.out: Cache startup messages, output from the cache processes, showing start flags, restarts, and general errors.
cache-gc.log: The output from the garbage collection of the cache process.
- If you haven't already, set up your application cluster to use the cache server address. You can find this in the Admin Console, at System > Settings > Caches.