Specifications

GUI Configuration
See Running the GUI on a Remote System for information on configuring and running the GUI on a
remote system outside your LifeKeeper cluster.
GUI Configuration
Item Description
GUI client and
server com-
munication
The LifeKeeper GUI client and server use Java Remote Method Invocation
(RMI) to communicate. For RMI to work correctly, the client and server must
use resolvable hostnames or IP addresses. If DNS is not implemented (or
names are not resolvable using other name lookup mechanisms), edit
the/etc/hostsfile on each client and server to include the names and addresses
of all other LifeKeeper servers.
GUI Server
Java platform
The LifeKeeper GUI server requires that the Java Runtime Environment (JRE) -
Java virtual machine, the Java platform core classes and supporting files - be
installed. The JRE for Linux is available on the SPS for Linux Installation Image
File (See theSPSfor Linux Installation Guide) or it can be downloaded directly
from http://www.oracle.com/technetwork/java/javase/downloads/index.html.
(Note: If downloading directly from this site, make sure you download Version
1.6.)
Note:By default, the LifeKeeper GUI server expects the JRE on each server to
be installed in the directory/usr/java/jre1.6.0_33. If this is not found, it will look
in the directory/usr/java/jdk1.6.0_33for a Java Software Development Kit
(JDK).If you want to use a JRE or JDK in another directory location, you must
edit the PATH in the LifeKeeper default file/etc/default/LifeKeeperto include
the directory containing the java interpreter, java.exe. If LifeKeeper is running
when you edit this file, you should stop and restart the LifeKeeper GUI server to
recognize the change. Otherwise, the LifeKeeper GUI will not be able to find the
Java command.
Java remote
object registry
server port
The LifeKeeper GUI server uses port 82 for the Java remote object registry on
each LifeKeeper server. This should allow servers to support RMI calls from cli-
ents behind typical firewalls.
LifeKeeper
administration
web server
The LifeKeeper GUI server requires an administration web server for client
browser communication. Currently, the LifeKeeper GUI server is using a private
copy of the lighttpd web server for its administration web server. This web
server is installed and configured by the steeleye-lighttpd package and uses
port 81 to avoid a conflict with other web servers.
GUI client net-
work access
LifeKeeper GUI clients require network access to all hosts in the LifeKeeper
cluster. When running the LifeKeeper GUI client in a browser, you will have to
lower the security level to allow network access for applets. Be careful not to
visit other sites with security set to low values (e.g., change the security set-
tings only for intranet or trusted sites).
SteelEye Protection Suite for Linux159